A message was sent to an incorrect email address from RT 2.0.7. The
mailer-daemon sent the usual message stating that the address does not
exist, whereupon RT sent a reply to the new mailer-daemon user. Is
there a way to keep RT from sending these messages to the mailer-daemon?
-Shawn Page
bspage@unity.ncsu.eduA message was sent to an incorrect email address from RT 2.0.7. The
mailer-daemon sent the usual message stating that the address does not
exist, whereupon RT sent a reply to the new mailer-daemon user. Is
there a way to keep RT from sending these messages to the mailer-daemon?
My current madness (see other ticket) is reimplementing
AutoReplyToRequestors to observe a ‘do not send autoreplies’ field in the
given user’s comment. (so we can not autoreply to all of our cutsie log
reports etc). Would that help you?
( ie, find the mailer-daemon’s user record, put this do not send
autoreplies in there, and RT will happily ignore its ever-after )
The main thing that is driving me mad is my desire to also catch runaway
mail loops, by doing the classic leaky bucket routine in my OnCorrespond
condition (ie, loop is detected, automagically add in the comment to
suppress replies, loop goes away), but this is proving more difficult than
I first thought as one cannot keep the user on autoreply-ignore 
Bruce Campbell RIPE
NCC
Operations
Hi Shawn,
I solved this here by adding an entry to /etc/aliases as follows:
Mailer-Daemon: my@email.address.com
YMMV, of course. I’m using Slackware 8, with Exim as my MTA - that may or may not have an impact on how effective the above fix is. You could also redirect the Mailer-Daemon alias to /dev/null or to any other convenient place, if you have no interest in being informed of such errors.
IIRC the default Slackware sendmail package does include an alias for Mailer-Daemon, redirecting it to root? I’m no longer sure though - last time I installed sendmail on Slackware was back in the good old days of Slackware 2… 
That’s where I got the idea for the above fix from, at any rate.
Hope that helps,
Jonathan-----Original Message-----
From: Shawn Page [mailto:bspage@unity.ncsu.edu]
Sent: 10 January 2002 20:17
To: rt-users@lists.fsck.com
Subject: [rt-users] mailer daemon email
A message was sent to an incorrect email address from RT 2.0.7. The mailer-daemon sent the usual message stating that the address does not exist, whereupon RT sent a reply to the new mailer-daemon user. Is there a way to keep RT from sending these messages to the mailer-daemon?
-Shawn Page
bspage@unity.ncsu.edu
A message was sent to an incorrect email address from RT 2.0.7. The
mailer-daemon sent the usual message stating that the address does not
exist, whereupon RT sent a reply to the new mailer-daemon user. Is
there a way to keep RT from sending these messages to the mailer-daemon?My current madness (see other ticket) is reimplementing
AutoReplyToRequestors to observe a ‘do not send autoreplies’ field in the
given user’s comment. (so we can not autoreply to all of our cutsie log
reports etc). Would that help you?
Ok, the above will shortly be available as AutoReplySquelch.tgz from
http://www.amsterdamned.org/~bc/rt/
It works by looking in the User’s Comment field for:
Autoreply on Transaction: Suppress
(case insensitive, doesn’t care whats after ‘suppress’).
If theres a match, it doesn’t continue (no mail sent). If theres no
match, its just the same as AutoReplyToRequestors (calls the same code).
Next up (after I sleep), code to dynamically add/remove that field based
on whether a given user is mailing us too often (ie, mail loop).
Bruce Campbell RIPE
NCC
Operations
Hi Jonathan,
It’s good to see another Slackware devotee here. I’ve recently
installed RT on Slack 8 and learning its intricacies.
BTW, you are correct; Slack does alias Mailer-Daemon to root. I’m
trying to track down one such error right now. Fortunately, it did
not get sent back to RT.
ttfn,
kevin-----Original Message-----
From: Hunter, Jonathan [mailto:JHunter@7global.com]
Sent: Friday, January 11, 2002 4:29 PM
To: Shawn Page
Cc: rt-users@lists.fsck.com
Subject: RE: [rt-users] mailer daemon email
Hi Shawn,
I solved this here by adding an entry to /etc/aliases as follows:
Mailer-Daemon: my@email.address.com
YMMV, of course. I’m using Slackware 8, with Exim as my MTA - that may or
may not have an impact on how effective the above fix is. You could also
redirect the Mailer-Daemon alias to /dev/null or to any other convenient
place, if you have no interest in being informed of such errors.
IIRC the default Slackware sendmail package does include an alias for
Mailer-Daemon, redirecting it to root? I’m no longer sure though - last time
I installed sendmail on Slackware was back in the good old days of Slackware
2… That’s where I got the idea for the above fix from, at any rate.
Hope that helps,
Jonathan
-----Original Message-----
From: Shawn Page [mailto:bspage@unity.ncsu.edu]
Sent: 10 January 2002 20:17
To: rt-users@lists.fsck.com
Subject: [rt-users] mailer daemon email
A message was sent to an incorrect email address from RT 2.0.7. The
mailer-daemon sent the usual message stating that the address does not
exist, whereupon RT sent a reply to the new mailer-daemon user. Is there a
way to keep RT from sending these messages to the mailer-daemon?
-Shawn Page
bspage@unity.ncsu.edu
rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users