atom feed12 messages in net.sourceforge.lists.courier-usersRe: [courier-users] validating addres...
FromSent OnAttachments
Matus UHLAR - fantomasMay 20, 2010 2:26 am 
Sam VarshavchikMay 20, 2010 4:04 am 
Matus UHLAR - fantomasMay 20, 2010 4:52 am 
Sam VarshavchikMay 20, 2010 3:03 pm 
Matus UHLAR - fantomasMay 26, 2010 2:38 am 
Sam VarshavchikMay 26, 2010 4:01 am 
Gordon MessmerMay 26, 2010 8:32 pm 
Matus UHLAR - fantomasMay 28, 2010 6:31 am 
Matus UHLAR - fantomasMay 28, 2010 7:18 am 
Sam VarshavchikMay 28, 2010 3:08 pm 
Gordon MessmerMay 28, 2010 4:11 pm 
Matus UHLAR - fantomasMay 31, 2010 8:24 am 
Subject:Re: [courier-users] validating addresses at SMTP time.
From:Sam Varshavchik (mrs@courier-mta.com)
Date:May 20, 2010 3:03:44 pm
List:net.sourceforge.lists.courier-users

Matus UHLAR - fantomas writes:

On 20.05.10 07:05, Sam Varshavchik wrote:

This is typically done by exporting the user list as aliases: us@domain.com: us@server1.domain.com

All nonexistent addresses would therefore be rejected as unauthorized relaying.

What if the users have authenticated do they have relaying privileges?

The mail will be accepted, but subsequently bounced.

Another question is - can courieresmtpd validate existence of addresses provided in mail from: in the same way as it validated rcpt to: ?

Nope.

Can you please answer my last question - can (are) domain in rcpt to: validated the same way as those in mail from:, when BOFHCHECKDNS is set? So the users wouldn't send mail to nonexistent domains...

No. Historically this originated as an easy way to reject junk mail with a randomly-generated return address. There was never a need to do a DNS lookup on the recipient's domain. That's where that came from.