On 12/04/2013 08:07 AM, Tim Whitaker wrote:
Some of my users are getting "Subject: failure notice" emails because
someone is trying to send email as them, but is failing the
SMTP authentication... so they get the error notice.
Is there any way I can just trash these emails that are failing SMTP auth?
--tim
I'm not sure I understand. There should be no SMTP authentication
failure once a message has entered "the system". Only clients should get
that, and it should happen before a message enters. There should be no
bounces with this error.
It would be helpful to see an example, complete with headers (redacted
where you must). This would show how the messages originated and was
relayed (Email forensics if you will).
The only way I can think of this happening is if a message got "in"
through an open or compromised relay. I've seen this happen with Yahoo
accounts in the past, but they didn't have failure notice messages that
I recall.
I'm not sure how you'd differentiate these from legitimate failure
notices. The message headers might provide a way. With Sieve you could
probably examine the headers for a legitimate authenticated submission
header, and discard it if that doesn't exist. Unfortunately, it'll be
several months before we have server-side sieve filtering.
You could probably write some maildrop rules to do this as well, but
maildrop is being deprecated in favor of sieve. Also, all client
messages don't go through maildrop by default. You'd need to set up
something custom for that along the same lines as spambox.
In the meantime you could probably filter these messages with a custom
filter on TBird or perhaps Outlook. Not a nice solution though.
Sorry there's presently no server-side solution for this. Having SPF and
DKIM set up might help, but I'd look for Sieve to provide the long term
solution. Server side filtering is a feature I'm greatly looking forward to.
--
-Eric 'shubes'
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
