Scrip to selectively autorespond?

I was wondering if anybody has already dealt with the issue of RT either
autoresponding to all incoming messages or not autoresponding to any at
all. Specifically, I’d like to try to implement recommendations of RFC
3834 in the autoresponder - such as, if RT gets mail from another auto-
responder that is easily identifiable as such, to stop generating loops.
Any pointers will be welcome.

Atro Tossavainen (Mr.) / The Institute of Biotechnology at
Systems Analyst, Techno-Amish & / the University of Helsinki, Finland,
+358-9-19158939 UNIX Dinosaur / employs me, but my opinions are my own.
< URL : http : / / www . helsinki . fi / %7E atossava / > NO FILE ATTACHMENTS

I was wondering if anybody has already dealt with the issue of RT either
autoresponding to all incoming messages or not autoresponding to any at
all. Specifically, I’d like to try to implement recommendations of RFC
3834 in the autoresponder - such as, if RT gets mail from another auto-
responder that is easily identifiable as such, to stop generating loops.
Any pointers will be welcome.


Atro Tossavainen (Mr.)

Not sure if I remember this correctly, but autoresponse e-mails should
have/contain a header with something like “Precedence: bulk”.
I am not sure what it is between bulk|junk|list, but given that, you can
check for the existence of that header in your MTA or procmail rule and stop
that mail from getting to RT.

My RT usage knowledge is quite rusty after over 1 year not using it, so
you’ll excuse me. I am just catching up. There might be other elegant ways
than this.

Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223


“Okay guys. This is Kenya. You pay taxes because you feel philanthropic,
unlike our MPs!”
– Kenneth Marende, Speaker, 10th Parilament.

Hi!

I was wondering if anybody has already dealt with the issue of RT either
autoresponding to all incoming messages or not autoresponding to any at
all. Specifically, I’d like to try to implement recommendations of RFC
3834 in the autoresponder - such as, if RT gets mail from another auto-
responder that is easily identifiable as such, to stop generating loops.
Any pointers will be welcome.

You can configure for example

Set($RedistributeAutoGeneratedMessages, ‘privileged’);

so that all messages which have “Precedence: bulk or junk”
, AutoSubmitted or X-FC-Machinegenerated set in the mail header,
will only generate mails
to recipients which are privileged users.

I have additionally in my procmail config stuff like

:0fh

  • Precedence: list
    |/usr/bin/formail -f -I “X-FC-Machinegenerated: true”
    <<

regards

sven

Hi Atro,

Why not change the script condition that launches the AutoReply so that
it’s a user defined condition that checks for the common bulk headers in
addition to the create condition?

Regards,
Gene

At 05:28 AM 12/7/2008, Atro Tossavainen wrote:

I was wondering if anybody has already dealt with the issue of RT either
autoresponding to all incoming messages or not autoresponding to any at
all. Specifically, I’d like to try to implement recommendations of RFC
3834 in the autoresponder - such as, if RT gets mail from another auto-
responder that is easily identifiable as such, to stop generating loops.
Any pointers will be welcome.


Atro Tossavainen (Mr.) / The Institute of Biotechnology at
Systems Analyst, Techno-Amish & / the University of Helsinki, Finland,
+358-9-19158939 UNIX Dinosaur / employs me, but my opinions are my own.
< URL : http : / / www . helsinki . fi / %7E atossava / > NO FILE ATTACHMENTS

Gene LeDuc, GSEC
Security Analyst
San Diego State University