OT: MAILER-DAEMON deliverability

[Charles Gregory <cg...@hwcn.org>]

I'm wondering whether I would be breaking any 'standards' to block mail to
my 'MAILER-DAEMON' address?

I'm seeing an increasing amount of mail to my 'MAILER-DAEMON@mydomain'
which are obvious cases where:

1) Virus or Spam has tried to deliver to a non-existent address here.
2) Our mail server has attempted to return the mail to the faked sender.
3) The faked sender doesn't exist OR the faked sender's system has an
anti-virus program stupidly sending bounces....

End result an 'undeliverable' or 'virus' notice sent *TO* our
MAILER-DAEMON. And usually with no useful information at all about the
original source of the trouble..... 

So can I just block that? Or could I block it with a limited list of
exceptions? 

Thanks for all advice.

- Charles

Re: OT: MAILER-DAEMON deliverability

[Charles Gregory <cg...@hwcn.org>]

On Tue, 30 Mar 2004, Kevin Peuhkurinen wrote:
> I don't like the idea of blocking any mailer-daemon email.   Some of it 
> is useful.   

Not mail FROM mailer-daemons. Mail TO specifically *our* mailer-daemon.
How often do we see 'useful' mail coming back to the daemon?

> I've written a bunch of rules that try to catch just the 
> virus-bounce related emails and mark them as spam.  
> http://www.exit0.us/index.php/VirusBounceRules2

I have had them installed for a long time, and have even tweaked them, but
they do no good when the bounced mail only quotes headers from our mailer
daemon's bounce, and there aren't many of those. A pathetically small
amount of information to try and score off of.....

- Charles

> Charles Gregory wrote:
> 
> >I'm wondering whether I would be breaking any 'standards' to block mail to
> >my 'MAILER-DAEMON' address?
> >
> >I'm seeing an increasing amount of mail to my 'MAILER-DAEMON@mydomain'
> >which are obvious cases where:
> >
> >1) Virus or Spam has tried to deliver to a non-existent address here.
> >2) Our mail server has attempted to return the mail to the faked sender.
> >3) The faked sender doesn't exist OR the faked sender's system has an
> >anti-virus program stupidly sending bounces....
> >
> >End result an 'undeliverable' or 'virus' notice sent *TO* our
> >MAILER-DAEMON. And usually with no useful information at all about the
> >original source of the trouble..... 
> >
> >So can I just block that? Or could I block it with a limited list of
> >exceptions? 
> >
> >Thanks for all advice.
> >
> >- Charles
> >
> >
> >  
> >
> 

Re: OT: MAILER-DAEMON deliverability

[Kevin Peuhkurinen <ke...@hepcoe.com>]

I don't like the idea of blocking any mailer-daemon email.   Some of it 
is useful.   I've written a bunch of rules that try to catch just the 
virus-bounce related emails and mark them as spam.    You can find them 
here:
http://www.exit0.us/index.php/VirusBounceRules2

Let me know if they help.
Kevin


Charles Gregory wrote:

>I'm wondering whether I would be breaking any 'standards' to block mail to
>my 'MAILER-DAEMON' address?
>
>I'm seeing an increasing amount of mail to my 'MAILER-DAEMON@mydomain'
>which are obvious cases where:
>
>1) Virus or Spam has tried to deliver to a non-existent address here.
>2) Our mail server has attempted to return the mail to the faked sender.
>3) The faked sender doesn't exist OR the faked sender's system has an
>anti-virus program stupidly sending bounces....
>
>End result an 'undeliverable' or 'virus' notice sent *TO* our
>MAILER-DAEMON. And usually with no useful information at all about the
>original source of the trouble..... 
>
>So can I just block that? Or could I block it with a limited list of
>exceptions? 
>
>Thanks for all advice.
>
>- Charles
>
>
>  
>