Menu

#26 SES interacts badly with greylisting

v0.8
open-postponed
pysrs (1)
1
2006-07-31
2005-08-24
No

A Greylisting mail recipient will reject a message with
a TEMPFAIL the first time you connect. You then have
to try back later. When using SES, the MAIL FROM is
different the next time we try, so the greylister never
accepts our mail. With SRS, the timestamp changes less
often (once per day), and so it can usually get accepted.

One solution is to make MAIL FROM persistent within
sendmail. Here is an idea from Dick St. Peters on the
srs-discuss mailing list:

Rename EnvFromSMTP to something like OrigEnvFromSMTP
and define a new EnvFromSMTP that returns the value of
a new macro, say MailFrom. Then assign
OrigEnvFromSMTP's output to MailFrom and declare
MailFrom to be a persistent macro. Something like this
- *completely untested*:

C{persistentMacros} {MailFrom}
...
R$* $: $(macro {MailFrom} $@ $>OrigEnvFromSMTP $&f
$) $1
...
SEnvFromSMTP
R$* $@ $&{MailFrom}

I'd be really surprised if I got the details right, but
I think the
basic idea should work.

Discussion

  • Stuart D. Gathman

    • milestone: --> v0.8
    • priority: 7 --> 1
    • assigned_to: nobody --> customdesigned
    • status: open --> open-postponed
     
  • Stuart D. Gathman

    Logged In: YES
    user_id=142072

    I have added a 'signing' mode to SRS. This works fine with
    greylisting, and the SES code should probably be deprecated.

     

Log in to post a comment.