Stephen, Seems that using a dated address at all isn't recommended as you don't know whether the remote SMTP server will be using SAV or not. That would mean that the proper handling of bounces as shown below would no longer work.
# Catch-all rule for addresses that are not yet on the whitelist. # Use a dated envelope (to catch bounces), a dated Reply-To for safe # measure, and also append the recipient's address to the whitelist. #to-file ~/.tmda/whitelist bare to * tag envelope dated=10d reply-to dated from bare=append Brent Spencer XsiteDesigns > On Tue, February 26, 2008 3:59 pm, Brent Spencer wrote: >> I am encountering a problem when using TMDA's dated addresses to send to >> recipients that use Sender Address Verification to confirm the validity >> of >> a sender's email address. When the remote SMTP server connects to my >> SMTP >> server and tries to verify one of the dated addresses (e.g. >> <[EMAIL PROTECTED]>). Does anyone know >> how to configure their SMTP server to allow for a successfuly >> verification >> of a TMDA dated address? Any help is greatly appreciated. > > Yeah, that's part of the reason I turned SAV off on my receiving SMTP > server. That, and a lot of people refuse to validate even legitimate > addresses (e.g. outbound only email addresses at companies.) I kinda > recommend against anyone using it these days. > > Anyway, the exact mechanism to solve your problem depends on which SMTP > server you're using. You could probably do it using a wildcard in your > /etc/aliases file (if such things are supported), or in whatever recipient > table your server supports, or some kind of plugin, or an inbound SMTP > proxy that just does this then forwards connections to your real server, > or ... > > (This email has been scanned for viruses by ClamAV) > > (This email has been scanned for viruses by ClamAV) _____________________________________________ tmda-users mailing list (tmda-users@tmda.net) http://tmda.net/lists/listinfo/tmda-users
