RT sends double e-mails

Hi.

I’ve just installed RT with qmail and PostgreSQL. Everything seems to work
fine, but everyone who gets an e-mail (e.g. the
OnCreate-AutoreplyToRequestors mail) from RT gets this mail two times, one of
which is a CC or a BCC.

I did not change any Scrib.

I don’t know where to look to solve this problem. Can you give me a hint?

TIA

Greetings,
Matthias

I’ve just installed RT with qmail and PostgreSQL. Everything seems to work
fine, but everyone who gets an e-mail (e.g. the
OnCreate-AutoreplyToRequestors mail) from RT gets this mail two times, one of
which is a CC or a BCC.

I did not change any Scrib.

I don’t know where to look to solve this problem. Can you give me a hint?

Can you list the Scrips that you have active both on the Queue, and any
global Scrips that you may have?

                         Bruce Campbell                            RIPE
               Systems/Network Engineer                             NCC
             www.ripe.net - PGP562C8B1B                      Operations

Can you list the Scrips that you have active both on the Queue, and any
global Scrips that you may have?

Sure.

Global Scrips:

OnCreate AutoreplyToRequestors with template Autoreply
OnCorrespond NotifyAllWatchers with template Correspondence
OnComment NotifyAdminCcsAsComment with template AdminComment
OnComment NotifyOtherRecipientsAsComment with template Correspondence
OnCorrespond NotifyOtherRecipients with template Correspondence
OnCreate NotifyAdminCcs with template InitialNotify

No queue specific scrips.

These scrips are the default scrips of version 2.0.13. I have only changed
the template for OnCreate-NotifyAdminCcs.

Regards,
Matthias

Can you list the Scrips that you have active both on the Queue, and any
global Scrips that you may have?

Sure.

These scrips are the default scrips of version 2.0.13. I have only changed
the template for OnCreate-NotifyAdminCcs.

Thats odd. Possibly you’ve run into an oddity with invoking the mailer.
Your next step would be to look at how RT is invoking postfix (config.pm,
$MailCommand) and trying the other varient (either ‘sendmail’ or
‘sendmailpipe’), and ensuring that the $SendmailArguments are correct.

Could anyone with a working postfix installation share their
configurations?

( sorry, I don’t have a postfix installation at present )

                         Bruce Campbell                            RIPE
               Systems/Network Engineer                             NCC
             www.ripe.net - PGP562C8B1B                      Operations

Can you list the Scrips that you have active both on the Queue, and any
global Scrips that you may have?

Sure.

These scrips are the default scrips of version 2.0.13. I have only
changed the template for OnCreate-NotifyAdminCcs.

Thats odd. Possibly you’ve run into an oddity with invoking the mailer.
Your next step would be to look at how RT is invoking postfix (config.pm,
$MailCommand) and trying the other varient (either ‘sendmail’ or
‘sendmailpipe’), and ensuring that the $SendmailArguments are correct.

Well, actually it is qmail, as I wrote in my first e-mail :slight_smile:

Here is the configuration for incoming and outgoing mail:

(/usr/sbin/sendmail is the one that comes with qmail)

outgoing mail configuration variables
$CorrespondAddress=‘general@domain.com’;
$CommentAddress=‘general-comment@domain.com’;
$MailCommand = ‘sendmail’;
$SendmailArguments=“-oi”;
$SendmailPath = “/usr/sbin/sendmail”;
$UseFriendlyToLine = 1;

This means that mail is sent this way:
$MIMEObj->send(“sendmail”, “-oi”)

For testing purposes, I have used sendmailpipe with logger as command, so the whole mail went to syslog.
(syslog did not get duplicate mails)

Here’s the header of the mail:

Subject: [domain.com #11] AutoReply: test nummer 2
From: “general” general-correspond@domain.com
Reply-To: general-correspond@domain.com
In-Reply-To: rt-11@domain.com
Message-ID: rt-11-37.16.0156184717524@domain.com
Precedence: bulk
X-RT-Loop-Prevention: domain.com
RT-Ticket: domain.com #11
Managed-by: Request Tracker 2.0.13 (http://www.fsck.com/projects/rt/)
RT-Originator: requestor@req.com
To: requestor@req.com

Here’s what qmail says in such situations:

May 28 23:05:18 host qmail: 1022619918.155583 info msg 88994: bytes 1937 from rt@domain.com qp 17908 uid 666
May 28 23:05:18 host qmail: 1022619918.183402 starting delivery 21386: msg 88994 to remote requestor@req.com
May 28 23:05:18 host qmail: 1022619918.183500 status: local 1/10 remote 1/20
May 28 23:05:18 host qmail: 1022619918.183523 starting delivery 21387: msg 88994 to remote requestor@req.com
May 28 23:05:18 host qmail: 1022619918.183543 status: local 1/10 remote 2/20

The message ID 88994 in both deliveries shows that RT send one mail.

You wanna more information? I’ll give you :slight_smile:

Best regards,
Matthias

Here is the configuration for incoming and outgoing mail:

(/usr/sbin/sendmail is the one that comes with qmail)

outgoing mail configuration variables

$CorrespondAddress=‘general@domain.com’;
$CommentAddress=‘general-comment@domain.com’;
$MailCommand = ‘sendmail’;

You want “sendmailpipe” here, not “sendmail”. “Sendmail” uses
Mail::Mailer qw(sendmail); it’s of questionable reliability, probably
makes Sendmail[tm]-specific assumptions, and is entirely unnecessary.

(Our RT is working fine with qmail, but would not work at all with
Mail::Mailer.)

-Rich

Rich Lafferty --------------±----------------------------------------------
Ottawa, Ontario, Canada | Save the Pacific Northwest Tree Octopus!
http://www.lafferty.ca/ | Save The Pacific Northwest Tree Octopus
rich@lafferty.ca -----------±----------------------------------------------

You want “sendmailpipe” here, not “sendmail”. “Sendmail” uses
Mail::Mailer qw(sendmail); it’s of questionable reliability, probably
makes Sendmail[tm]-specific assumptions, and is entirely unnecessary.

(Our RT is working fine with qmail, but would not work at all with
Mail::Mailer.)

Fine. It is working now. Thank you for your help.

I somehow did not want to change to ‘sendmailpipe’, maybe because of this
comment in config.pm:

We know that ‘sendmail’ works fairly well.

That sounded good enough for me :slight_smile:

Regards,
Matthias

“RL” == Rich Lafferty rich+rt@lafferty.ca writes:

RL> (Our RT is working fine with qmail, but would not work at all with
RL> Mail::Mailer.)

Even with $MailCommand=‘qmail’?

“RL” == Rich Lafferty rich+rt@lafferty.ca writes:

RL> (Our RT is working fine with qmail, but would not work at all with
RL> Mail::Mailer.)

Even with $MailCommand=‘qmail’?

Do you mean ‘qmail-inject’? I haven’t tried it, have you?
Anyway, sendmailpipe works fine for me with qmail.

Matthias

“RL” == Rich Lafferty rich+rt@lafferty.ca writes:

RL> (Our RT is working fine with qmail, but would not work at all with
RL> Mail::Mailer.)

Even with $MailCommand=‘qmail’?

Do you mean ‘qmail-inject’? I haven’t tried it, have you?

That’s not what that is. $MailCommand is either “sendmailpipe” or
an argument for Mail::Mailer.

-Rich

Rich Lafferty --------------±----------------------------------------------
Ottawa, Ontario, Canada | Save the Pacific Northwest Tree Octopus!
http://www.lafferty.ca/ | Save The Pacific Northwest Tree Octopus
rich@lafferty.ca -----------±----------------------------------------------

“MJ” == Matthias Juchem juchem@uni-mannheim.de writes:

MJ> On Wednesday, 29. May 2002 16:09, you wrote:

“RL” == Rich Lafferty rich+rt@lafferty.ca writes:

RL> (Our RT is working fine with qmail, but would not work at all with
RL> Mail::Mailer.)

Even with $MailCommand=‘qmail’?

MJ> Do you mean ‘qmail-inject’? I haven’t tried it, have you?
MJ> Anyway, sendmailpipe works fine for me with qmail.

No. $MailCommand sets the type of mailer used by Mail::Mailer, not the
program name. The special case is sendmailpipe which causes RT to use
the sendmail program directly, rather than via the Mail::Mailer
module. That is, sendmialpipe and sendmail should be identical in
functionality.

Read the Mail::Mailer man page to see what other values you can set.

No. $MailCommand sets the type of mailer used by Mail::Mailer, not the
program name. The special case is sendmailpipe which causes RT to use
the sendmail program directly, rather than via the Mail::Mailer
module.

(Yep.)

That is, sendmialpipe and sendmail should be identical in
functionality.

Only if you explicitly make it so. Mail::Mailer qw(sendmail) will try
/usr/lib/sendmail, then /usr/sbin/sendmail, then /usr/ucblib/sendmail
(help! flashbacks!), and will always call it with the “right”
arguments, for its own idea of “right” (which should be correct with
things that implement the sendmail API accurately.)

But the point of sendmailpipe is to let you specify the location of
the program to run and the arguments it is called with, so that you
don’t have to use Mail::Mailer’s guess. In other words,
sendmailpipe’s purpose is to not be identical in functionality. :slight_smile:

-Rich

Rich Lafferty --------------±----------------------------------------------
Ottawa, Ontario, Canada | Save the Pacific Northwest Tree Octopus!
http://www.lafferty.ca/ | Save The Pacific Northwest Tree Octopus
rich@lafferty.ca -----------±----------------------------------------------