8 messages in net.sourceforge.lists.courier-usersRe: [courier-users] <@> as a return a...
FromSent OnAttachments
William Dell WisnerFeb 3, 2003 5:52 am 
Roland SchneiderFeb 3, 2003 7:33 am 
William Dell WisnerFeb 3, 2003 9:03 am 
Roland SchneiderFeb 3, 2003 11:18 am 
Sam VarshavchikFeb 3, 2003 4:10 pm 
William Dell WisnerFeb 4, 2003 1:44 am 
Roman NeuhauserFeb 4, 2003 2:30 am 
Brian CandlerFeb 4, 2003 11:51 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] <@> as a return addressActions...
From:Brian Candler (B.Ca@pobox.com)
Date:Feb 4, 2003 11:51:42 am
List:net.sourceforge.lists.courier-users

On Tue, Feb 04, 2003 at 09:03:18AM +0100, Roman Neuhauser wrote:

# will@dell.wisner.name / 2003-02-03 13:42:24 +0000:

As far as I can determine <@> is not a valid RFC2822 address, yet Courier uses it on outgoing error messages. Am I missing something in one of the myriad mail RFCs that defines this usage? Sam? Anybody?

see RFC 2821 sections 3.7 and 4.5.5

Neither of those sections answers the question.

Double-bounces aren't normally delivered, but they might get delivered to the local postmaster, in which case you really ought to put a valid RFC2822 address on them. What does Courier MTA do with single-bounce messages? If they have a valid header, such as "From: Mailer-Daemon@your.domain", I see no reason why you can't use that for double-bounces too.