On Mar 17, 2008, at 7:28 PM, Mark Sapiro wrote:
> A text change breaks 35 existing Mailman translations, and breaks them

Sorry, yes you are right I forgot about translations.

> I'm not talking about DSNs to non-accepted mail. I'm talking about a
> message that is accepted by an MX, queued and later rejected by the
> ultimate destination. When the MX gets the reject from the  
> destination,
> does it say "oops, I screwed up, I never should have accepted and  
> queued
> this message" and just drop it, or does it return a DSN.
>
> Does this make sense, or am I stuck in the 20th century?

If you have an MX that queues mail for someone else and isn't  
configured to properly deal with DSNs, then yes, you are stuck in the  
20th century.

And yes, if your MX host was on our network (and sending DSNs to  
forged senders) we'd ask you to shut it down.  ("ask" in non-optional  
sense)

-- 
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source  
and other randomness


_______________________________________________
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Reply via email to