Well, when that happens, the service has to contact the registrant (or if impossible another involved party) and request an update of the underlying data. Anything beyond that is not required at this time. Why should the original sender have a right to be informed about a bounce if the data is later fixed? Volker Am 31.07.2014 17:55, schrieb Alex_Deacon@mpaa.org:
Thats right.
We are getting into the weeds here but when the “sender” (SMTP server in the context Michele provided below) finally gives up it will send a hard bounce back to the address in From: or Reply-To: header.
When this happens the service has X days (2 days based on the recent thread) to process the message and notify the original sender of the bounce.
Alex
On Jul 30, 2014, at 1:46 AM, Michele Neylon - Blacknight <michele@blacknight.com> wrote:
David
It's defined in the RFC as:
"Retries continue until the message is transmitted or the sender gives up; the give-up time generally needs to be at least 4-5 days"
See: https://www.ietf.org/rfc/rfc2821.txt
Of course that's an RFC, so while *most* mail servers might work that way there's no guarantee that they all will
Regards
Michele
-- Mr Michele Neylon Blacknight Solutions Hosting & Colocation, Domains http://www.blacknight.co/ http://blog.blacknight.com/ http://www.technology.ie/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Twitter: http://twitter.com/mneylon ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,Ireland Company No.: 370845
-----Original Message----- From: gnso-ppsai-pdp-wg-bounces@icann.org [mailto:gnso-ppsai-pdp-wg-bounces@icann.org] On Behalf Of David Cake Sent: Tuesday, July 29, 2014 6:20 PM To: James M. Bladel Cc: gnso-ppsai-pdp-wg@icann.org Subject: Re: [Gnso-ppsai-pdp-wg] Question
It used to be the standard practice was that mail servers would continue trying to deliver for four days.
Regards David
On 29 Jul 2014, at 6:15 pm, James M. Bladel <jbladel@godaddy.com> wrote:
I¹ll also see if we are tracking/counting this stat. Another helpful data point might be how many ³bounces² are later resolved, meaning the delivery failure was a temporary situation that was later corrected. This could be important if a relay obligation were framed in terms of ³unsuccessful delivery after X attempts or within Y business days² or something similar.
Thanks<
J.
On 7/29/14, 10:42 , "Graeme Bunton" <gbunton@tucows.com> wrote:
That's a good question Kathy, I'll see if I can dig some stats up from our systems.
Graeme _________________________ Graeme Bunton Manager, Management Information Systems Manager, Public Policy Tucows Inc. PH: 416 535 0123 ext 1634
-----Original Message----- From: gnso-ppsai-pdp-wg-bounces@icann.org [mailto:gnso-ppsai-pdp-wg-bounces@icann.org] On Behalf Of Kathy Kleiman Sent: Tuesday, July 29, 2014 11:32 AM To: Metalitz, Steven; gnso-ppsai-pdp-wg@icann.org Subject: [Gnso-ppsai-pdp-wg] Question
Hi Steve and Alex, Good discussion today - much appreciated. Quick note: I can certainly understand the desire to know if an email went through. Quick question: do you have any idea how many "bouncebacks" we are talking about? In today's environment, with the current forwarding work by proxy/privacy providers, do you have any idea how many messages are undeliverable vs. how many may be received but not responded to? I know each messages is important, but are we talking about a high percentage or a very low percentage?
Tx, Kathy _______________________________________________ Gnso-ppsai-pdp-wg mailing list Gnso-ppsai-pdp-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg
_______________________________________________ Gnso-ppsai-pdp-wg mailing list Gnso-ppsai-pdp-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg
_______________________________________________ Gnso-ppsai-pdp-wg mailing list Gnso-ppsai-pdp-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg
_______________________________________________ Gnso-ppsai-pdp-wg mailing list Gnso-ppsai-pdp-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg
Gnso-ppsai-pdp-wg mailing list Gnso-ppsai-pdp-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg
-- Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung. Mit freundlichen Grüßen, Volker A. Greimann - Rechtsabteilung - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann@key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook: www.facebook.com/KeySystems www.twitter.com/key_systems Geschäftsführer: Alexander Siffrin Handelsregister Nr.: HR B 18835 - Saarbruecken Umsatzsteuer ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen. -------------------------------------------- Should you have any further questions, please do not hesitate to contact us. Best regards, Volker A. Greimann - legal department - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann@key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Follow us on Twitter or join our fan community on Facebook and stay updated: www.facebook.com/KeySystems www.twitter.com/key_systems CEO: Alexander Siffrin Registration No.: HR B 18835 - Saarbruecken V.A.T. ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.