| 2012-05-07 16:16:17 |
Paul Everitt |
description |
gocept provided a devnull email address for bounces:
bounces@osf.karlstaging.gocept.com
Code change, put into production. |
gocept provided a devnull email address for bounces:
bounces@osf.karlstaging.gocept.com
Code change, put into production.
Background by Chris in a comment on another ticket:
The idea here is that if we set the envelope from of bounce messages
to something that winds up either in the bitbucket or cordoned off
somewhere, then we break the cycle and no longer generate massive
infinite loops of MTAs emailing each other about the fact that they
can't email each other. Something from yesterday felt funny to me so
I investigated further this morning and discovered that my
implementation of this is actually wrong. I am setting the 'From'
header of the email to whatever is set as the 'bounce_from_email'. I
am not actually setting the envelope 'From' which is why bounces of
bounces keep coming back to 'karl@karl.soros.org', because that's
still the envelope from. So that's one problem.
I did go ahead and send a test mail to
'bounces@osf.karlstaging.gocept.com', the email provided by Zagy in
that ticket, just to see what would happen. That email bounced. ;)
So fixing my snafu with the envelope from won't get us out of the
woods yet. We need to also have an email address to set that to that
will quietly absorb, without bouncing, anything that is thrown at it.
The ticket above suggests hanging on to that email in case there's
something we want in it. I suspect there won't be and we may as well
send it to /dev/null, but as long as nothing bounces back from it,
we've fixed the infinite loop.
I don't really understand what you're suggesting with the local 'null'
alias. What we need is an address that will silently absorb email
sent to it from the great wide internet. And then I need to fix my
implementation of 'bounce_from_email'. |
|
