On 17-Mar-2009, at 06:09, Erwan David wrote:
I would fear it breaks recipient validation, accepting mail for eavery
address with a _ as valid.
That is a drawback. The other choice is to change the delimiter in
postfix to _ and rewrite it to accept all '+' addresses to '_'. The
trouble is the huge mass of ignorant websites that refuse to accept a
'+' and don't even care that they are wrong.
And since we've been using plus addressing for over 10 years, simply
switching to '_' (or '.' which at least one IMAP server uses) is just
not realistic.
The good thing is, it hasn't been much of a problem. In the last 30
days I've gotten exactly one address that was invalid and had a '_' in
it, and I'm pretty sure that was a spoof address that the domain owner
handed out.
It appears that, at least now, '_' is not in the spammer's lexicon of
addresses to try.
but yeah, this needs to be monitored as it can be a backscatter source:
Mar 17 07:21:22 mail postfix/smtpd[40467]: C3B7D118B9B7:
client=c-67-164-162-51.hsd1.co.comcast.net[67.164.162.51]
Mar 17 07:21:22 mail postfix/cleanup[40775]: C3B7D118B9B7: message-id=<040e794f-40e7-4c23-ac4b-001d5cf24...@kreme.com
>
Mar 17 07:21:22 mail postfix/qmgr[31772]: C3B7D118B9B7: from=<krem...@kreme.com
>, size=815, nrcpt=1 (queue active)
Mar 17 07:21:23 mail postfix/error[41241]: C3B7D118B9B7: to=<ziggy+t...@kreme.com
>, orig_to=<ziggy_t...@kreme.com>, relay=none, delay=0.3,
delays=0.09/0.14/0/0.07, dsn=5.0.0, status=bounced (User unknown)
Mar 17 07:21:23 mail postfix/bounce[41242]: C3B7D118B9B7: sender non-
delivery notification: 14A1A118BA5C
Mar 17 07:21:23 mail postfix/qmgr[31772]: C3B7D118B9B7: removed
Maybe we'll get support for multiple delimiters in postfix someday?
recipient_mutli_delimiters = {+,_.}
where everything between {} is a valid delimiter?
Not holding my breath though.
--
You and me
Sunday driving
Not arriving
