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:Roland Schneider (list@serv.ch)
Date:Feb 3, 2003 7:33:10 am
List:net.sourceforge.lists.courier-users

--William Dell Wisner wrote on 03.02.03 13:42 +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?

Courier uses an empty sender for DSN. If such a bounce is undeliverable you get a doublebounce whith the sender set to @# (or #@, dont remeber...) which prevents the message from bouncing around anymore.

Dont accept messages with forged domains (set BOFHCHECKDNS), and dont bounce from within Maildrop (or dot-courier).

Roland