Re: [Systems Req #51537] FW: [mpich2-maint] Spam mail
I believe I have stopped the bouncing, for now. We are going to have to architect a better system by which to filter out spam before it hits the trac server though, as this will continue to happen. Rick Rajeev Thakur wrote:
We are getting too many of these mails in response to a spam mail sent to mpich2-maint, which is now run by Trac. Is there a way to stop them? Looks like they are just bouncing back and forth.
Rajeev
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of mpich2 Sent: Thursday, July 31, 2008 10:03 AM To: undisclosed-recipients: Subject: [mpich2-maint] #12: DELIVERY FAILURE: No route found to server BNSTORNOTES-M03/Servers/ScotiabankGroup from server BNSHUB01/H/SCOTIABANKGROUP. Check Server and Connection documents in the Domino Directory.
---------------------------------------+-------------------------------- ---------------------------------------+---- Reporter: [email protected] | Type: bug Status: new | Priority: major Component: mpich2 | ---------------------------------------+-------------------------------- ---------------------------------------+----
Your message
Subject: [mpich2-maint] #11: DELIVERY FAILURE: No route found to server BNSTORNOTES-M03/Servers/ScotiabankGroup from server BNSHUBM02/H/SCOTIABANKGROUP. Check Server and Connection documents in the Domino Directory.
was not delivered to:
because:
No route found to server BNSTORNOTES-M03/Servers/ScotiabankGroup from server BNSHUB01/H/SCOTIABANKGROUP. Check Server and Connection documents in the Domino Directory.
Notice of Confidentiality: The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review re-transmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error please contact the sender immediately by return electronic transmission and then immediately delete this transmission including all attachments without copying distributing or disclosing same.
Avis de confidentialit�: L�information transmise est strictement r�serv�e � la personne ou � l�organisme auquel elle est adress�e et peut �tre de nature confidentielle. Toute lecture retransmission divulgation ou autre utilisation de cette information ou toute action prise sur la foi de cette information par des personnes ou organismes autres que son destinataire est interdite. Si vous avez re�u cette information par erreur veuillez contacter son exp�diteur imm�diatement par retour du courrier �lectronique puis supprimer cette information y compris toutes pi�ces jointes sans en avoir copi� divulgu� ou diffus� le contenu.
Aviso de Confidencialidad. Este correo electr�nico y/o el material adjunto es para uso exclusivo de la persona o entidad a la que expresamente se le ha enviado y puede contener informaci�n confidencial o material privilegiado. Si usted no es el destinatario leg�timo del mismo por favor rep�rtelo inmediatamente al remitente del correo y b�rrelo. Cualquier revisi�n retransmisi�n difusi�n o cualquier otro uso de este correo por personas o entidades distintas a las del destinatario leg�timo queda expresamente prohibido. Este correo electr�nico no pretende ni debe ser considerado como constitutivo de ninguna relaci�n legal contractual o de otra �ndole similar.
-- Ticket URL: <https://trac.mcs.anl.gov/projects/mpich2/ticket/12>
Thanks. How do you do it for the systems mailing list, which also sends an automatic reply, which can result in another spam, and so on? Rajeev
-----Original Message----- From: Rick Bradshaw [mailto:[email protected]] Sent: Thursday, July 31, 2008 10:27 AM To: Rajeev Thakur Cc: 'The Systems Group'; [email protected] Subject: Re: [Systems Req #51537] FW: [mpich2-maint] Spam mail
I believe I have stopped the bouncing, for now. We are going to have to architect a better system by which to filter out spam before it hits the trac server though, as this will continue to happen.
Rick
Rajeev Thakur wrote:
We are getting too many of these mails in response to a spam mail sent to mpich2-maint, which is now run by Trac. Is there a way to stop them? Looks like they are just bouncing back and forth.
Rajeev
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of mpich2 Sent: Thursday, July 31, 2008 10:03 AM To: undisclosed-recipients: Subject: [mpich2-maint] #12: DELIVERY FAILURE: No route found to server BNSTORNOTES-M03/Servers/ScotiabankGroup from server BNSHUB01/H/SCOTIABANKGROUP. Check Server and Connection documents in the Domino Directory.
---------------------------------------+------------------------------
---------------------------------------+-- ---------------------------------------+---- Reporter: [email protected] | Type: bug Status: new | Priority: major Component: mpich2 |
---------------------------------------+------------------------------
---------------------------------------+-- ---------------------------------------+----
Your message
Subject: [mpich2-maint] #11: DELIVERY FAILURE: No route found to server BNSTORNOTES-M03/Servers/ScotiabankGroup from server BNSHUBM02/H/SCOTIABANKGROUP. Check Server and Connection documents in the Domino Directory.
was not delivered to:
because:
No route found to server BNSTORNOTES-M03/Servers/ScotiabankGroup from server BNSHUB01/H/SCOTIABANKGROUP. Check Server and Connection documents in the Domino Directory.
Notice of Confidentiality: The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review re-transmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error please contact the sender immediately by return electronic transmission and then immediately delete this transmission including all attachments without copying distributing or disclosing same.
Avis de confidentialit�: L�information transmise est strictement r�serv�e � la personne ou � l�organisme auquel elle est adress�e et peut �tre de nature confidentielle. Toute lecture retransmission divulgation ou autre utilisation de cette information ou toute action prise sur la foi de cette information par des personnes ou organismes autres que son destinataire est interdite. Si vous avez re�u cette information par erreur veuillez contacter son exp�diteur imm�diatement par retour du courrier �lectronique puis supprimer cette information y compris toutes pi�ces jointes sans en avoir copi� divulgu� ou diffus� le contenu.
Aviso de Confidencialidad. Este correo electr�nico y/o el material adjunto es para uso exclusivo de la persona o entidad a la que expresamente se le ha enviado y puede contener informaci�n confidencial o material privilegiado. Si usted no es el destinatario leg�timo del mismo por favor rep�rtelo inmediatamente al remitente del correo y b�rrelo. Cualquier revisi�n retransmisi�n difusi�n o cualquier otro uso de este correo por personas o entidades distintas a las del destinatario leg�timo queda expresamente prohibido. Este correo electr�nico no pretende ni debe ser considerado como constitutivo de ninguna relaci�n legal contractual o de otra �ndole similar.
-- Ticket URL: <https://trac.mcs.anl.gov/projects/mpich2/ticket/12>
I don't think this has stopped yet. Does trac have an option to get rid of the initial notification to the reporter? We will still need the subsequent notifications when someone replies to the ticket. (Sent from my iPhone) -- Pavan Balaji http://www.mcs.anl.gov On Jul 31, 2008, at 11:27 AM, Rick Bradshaw <[email protected]> wrote:
I believe I have stopped the bouncing, for now. We are going to have to architect a better system by which to filter out spam before it hits the trac server though, as this will continue to happen.
Rick
Rajeev Thakur wrote:
We are getting too many of these mails in response to a spam mail sent to mpich2-maint, which is now run by Trac. Is there a way to stop them? Looks like they are just bouncing back and forth.
Rajeev
-----Original Message----- From: [email protected] [mailto:[email protected] ] On Behalf Of mpich2 Sent: Thursday, July 31, 2008 10:03 AM To: undisclosed-recipients: Subject: [mpich2-maint] #12: DELIVERY FAILURE: No route found to server BNSTORNOTES-M03/Servers/ScotiabankGroup from server BNSHUB01/H/SCOTIABANKGROUP. Check Server and Connection documents in the Domino Directory.
--------------------------------------- +-------------------------------- ---------------------------------------+---- Reporter: [email protected] | Type: bug Status: new | Priority: major Component: mpich2 | --------------------------------------- +-------------------------------- ---------------------------------------+----
Your message
Subject: [mpich2-maint] #11: DELIVERY FAILURE: No route found to server BNSTORNOTES-M03/Servers/ScotiabankGroup from server BNSHUBM02/H/SCOTIABANKGROUP. Check Server and Connection documents in the Domino Directory.
was not delivered to:
because:
No route found to server BNSTORNOTES-M03/Servers/ScotiabankGroup from server BNSHUB01/H/SCOTIABANKGROUP. Check Server and Connection documents in the Domino Directory.
Notice of Confidentiality: The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review re-transmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error please contact the sender immediately by return electronic transmission and then immediately delete this transmission including all attachments without copying distributing or disclosing same.
Avis de confidentialité: L’information transmise est strictement réservée à la personne o u à l’organisme auquel elle est adressée et peut être de nature confidentielle. Toute lecture retransmission divulgation ou autre utilisation de cette information ou toute action prise sur la foi de cette information par des personnes ou organismes autres que son destinataire est interdite. Si vous avez reçu cette information par erreur veuillez contacter son exp éditeur immédiatement par retour du courrier électronique puis supprimer cette information y compris toutes pièces jointes sans en avoir copié d ivulgué ou diffusé le contenu.
Aviso de Confidencialidad. Este correo electrónico y/o el material adjunto es para uso exclus ivo de la persona o entidad a la que expresamente se le ha enviado y puede contener información confidencial o material privilegiado. Si uste d no es el destinatario legítimo del mismo por favor repórtelo inmediatame nte al remitente del correo y bórrelo. Cualquier revisión retransmisión difusión o cualquier otro uso de este correo por personas o entidades distintas a las del destinatario legítimo queda expresamente prohibido. Este c orreo electrónico no pretende ni debe ser considerado como constitutivo de ninguna relación legal contractual o de otra índole similar.
-- Ticket URL: <https://trac.mcs.anl.gov/projects/mpich2/ticket/12>
Is there a way to get rid of these tickets from Trac so that they don't even appear in the closed list? There are about 65 of them now. Rajeev
-----Original Message----- From: Pavan Balaji [mailto:[email protected]] Sent: Thursday, July 31, 2008 1:12 PM To: [email protected] Cc: Rajeev Thakur; The Systems Group Subject: Re: [mpich2-core] Re: [Systems Req #51537] FW: [mpich2-maint] Spam mail
I don't think this has stopped yet. Does trac have an option to get rid of the initial notification to the reporter? We will still need the subsequent notifications when someone replies to the ticket.
(Sent from my iPhone)
-- Pavan Balaji http://www.mcs.anl.gov
On Jul 31, 2008, at 11:27 AM, Rick Bradshaw <[email protected]> wrote:
I believe I have stopped the bouncing, for now. We are going to have to architect a better system by which to filter out spam before it hits the trac server though, as this will continue to happen.
Rick
Rajeev Thakur wrote:
We are getting too many of these mails in response to a spam mail sent to mpich2-maint, which is now run by Trac. Is there a way to stop them? Looks like they are just bouncing back and forth.
Rajeev
-----Original Message----- From: [email protected] [mailto:[email protected] ] On Behalf Of mpich2 Sent: Thursday, July 31, 2008 10:03 AM To: undisclosed-recipients: Subject: [mpich2-maint] #12: DELIVERY FAILURE: No route found to server BNSTORNOTES-M03/Servers/ScotiabankGroup from server BNSHUB01/H/SCOTIABANKGROUP. Check Server and Connection documents in the Domino Directory.
--------------------------------------- +-------------------------------- ---------------------------------------+---- Reporter: [email protected] | Type: bug Status: new | Priority: major Component: mpich2 | --------------------------------------- +-------------------------------- ---------------------------------------+----
Your message
Subject: [mpich2-maint] #11: DELIVERY FAILURE: No route found to server BNSTORNOTES-M03/Servers/ScotiabankGroup from server BNSHUBM02/H/SCOTIABANKGROUP. Check Server and Connection documents in the Domino Directory.
was not delivered to:
because:
No route found to server BNSTORNOTES-M03/Servers/ScotiabankGroup from server BNSHUB01/H/SCOTIABANKGROUP. Check Server and Connection documents in the Domino Directory.
Notice of Confidentiality: The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review re-transmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error please contact the sender immediately by return electronic transmission and then immediately delete this transmission including all attachments without copying distributing or disclosing same.
Avis de confidentialit�: L�information transmise est strictement r�serv�e � la personne o u � l�organisme auquel elle est adress�e et peut �tre de nature confidentielle. Toute lecture retransmission divulgation ou autre utilisation de cette information ou toute action prise sur la foi de cette information par des personnes ou organismes autres que son destinataire est interdite. Si vous avez re�u cette information par erreur veuillez contacter son exp �diteur imm�diatement par retour du courrier �lectronique puis supprimer cette information y compris toutes pi�ces jointes sans en avoir copi� d ivulgu� ou diffus� le contenu.
Aviso de Confidencialidad. Este correo electr�nico y/o el material adjunto es para uso exclus ivo de la persona o entidad a la que expresamente se le ha enviado y puede contener informaci�n confidencial o material privilegiado. Si uste d no es el destinatario leg�timo del mismo por favor rep�rtelo inmediatame nte al remitente del correo y b�rrelo. Cualquier revisi�n retransmisi�n difusi�n o cualquier otro uso de este correo por personas o entidades distintas a las del destinatario leg�timo queda expresamente prohibido. Este c orreo electr�nico no pretende ni debe ser considerado como constitutivo de ninguna relaci�n legal contractual o de otra �ndole similar.
-- Ticket URL: <https://trac.mcs.anl.gov/projects/mpich2/ticket/12>
Yeah, I'll take care of that once this mess is resolved. (Sent from my iPhone) -- Pavan Balaji http://www.mcs.anl.gov On Jul 31, 2008, at 2:28 PM, "Rajeev Thakur" <[email protected]> wrote:
Is there a way to get rid of these tickets from Trac so that they don't even appear in the closed list? There are about 65 of them now.
Rajeev
-----Original Message----- From: Pavan Balaji [mailto:[email protected]] Sent: Thursday, July 31, 2008 1:12 PM To: [email protected] Cc: Rajeev Thakur; The Systems Group Subject: Re: [mpich2-core] Re: [Systems Req #51537] FW: [mpich2-maint] Spam mail
I don't think this has stopped yet. Does trac have an option to get rid of the initial notification to the reporter? We will still need the subsequent notifications when someone replies to the ticket.
(Sent from my iPhone)
-- Pavan Balaji http://www.mcs.anl.gov
On Jul 31, 2008, at 11:27 AM, Rick Bradshaw <[email protected]> wrote:
I believe I have stopped the bouncing, for now. We are going to have to architect a better system by which to filter out spam before it hits the trac server though, as this will continue to happen.
Rick
Rajeev Thakur wrote:
We are getting too many of these mails in response to a spam mail sent to mpich2-maint, which is now run by Trac. Is there a way to stop them? Looks like they are just bouncing back and forth.
Rajeev
-----Original Message----- From: [email protected] [mailto:[email protected] ] On Behalf Of mpich2 Sent: Thursday, July 31, 2008 10:03 AM To: undisclosed-recipients: Subject: [mpich2-maint] #12: DELIVERY FAILURE: No route found to server BNSTORNOTES-M03/Servers/ScotiabankGroup from server BNSHUB01/H/SCOTIABANKGROUP. Check Server and Connection documents in the Domino Directory.
--------------------------------------- +-------------------------------- ---------------------------------------+---- Reporter: [email protected] | Type: bug Status: new | Priority: major Component: mpich2 | --------------------------------------- +-------------------------------- ---------------------------------------+----
Your message
Subject: [mpich2-maint] #11: DELIVERY FAILURE: No route found to server BNSTORNOTES-M03/Servers/ScotiabankGroup from server BNSHUBM02/H/SCOTIABANKGROUP. Check Server and Connection documents in the Domino Directory.
was not delivered to:
because:
No route found to server BNSTORNOTES-M03/Servers/ScotiabankGroup from server BNSHUB01/H/SCOTIABANKGROUP. Check Server and Connection documents in the Domino Directory.
Notice of Confidentiality: The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review re-transmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error please contact the sender immediately by return electronic transmission and then immediately delete this transmission including all attachments without copying distributing or disclosing same.
Avis de confidentialité: L’information transmise est strictement réservée à la perso nne o u à l’organisme auquel elle est adressée et peut être de nature confidentielle. Toute lecture retransmission divulgation ou autre utilisation de cette information ou toute action prise sur la foi de cette information par des personnes ou organismes autres que son destinataire est interdite. Si vous avez reçu cette information par erreur veuillez contacter son exp éditeur immédiatement par retour du courrier électronique puis supprimer cette information y compris toutes pièces jointes sans en avoir co pié d ivulgué ou diffusé le contenu.
Aviso de Confidencialidad. Este correo electrónico y/o el material adjunto es para uso exclus ivo de la persona o entidad a la que expresamente se le ha enviado y puede contener información confidencial o material privilegiado. Si uste d no es el destinatario legítimo del mismo por favor repórtelo inmedi atame nte al remitente del correo y bórrelo. Cualquier revisión retransm isión difusión o cualquier otro uso de este correo por personas o entidades distintas a las del destinatario legítimo queda expresamente prohibido. Este c orreo electrónico no pretende ni debe ser considerado como constitutivo de ninguna relación legal contractual o de otra índole similar.
-- Ticket URL: <https://trac.mcs.anl.gov/projects/mpich2/ticket/12>
participants (4)
-
Max trefonides -
Pavan Balaji -
Rajeev Thakur -
Rick Bradshaw