Mail loop

Over the weekend I seem to have built up a 23M procmail log for my test
box… Can anyone help me find the cause/stop this loop?

Here’s a bit of the procmail log:

— Logging /home/rt_dispatcher/procmail.log for rt_dispatcher,
procmail: [30459] Mon Apr 25 09:07:36 2005
procmail: Assigning "MAILDOMAIN=rt.example.com"
procmail: Assigning "RT_MAILGATE=/opt/rt3/bin/rt-mailgate"
procmail: Assigning "RT_URL=https://rt.example.com"
procmail: Assigning "LOGABSTRACT=all"
procmail: Executing "formail -c -xReceived: |grep $MAILDOMAIN |sed -e
’s/.for <(.)>* ;.$/\1/’"
procmail: Assigning "TO="
procmail: Executing "echo $TO| $HOME/get_queue.pl"
procmail: [30459] Mon Apr 25 09:07:37 2005
procmail: Assigning "QUEUE=general"
procmail: Executing "echo $TO| $HOME/get_action.pl"
procmail: Assigning “ACTION=correspond"
procmail: Executing
”/opt/rt3/bin/rt-mailgate,–queue,general,–action,correspond,–url,https://rt.example.com,–debug"
Connecting to https://rt.example.com/REST/1.0/NoAuth/mail-gateway at
/opt/rt3/bin/rt-mailgate line 99, <> chunk 1.
not ok - Could not load a valid user at /opt/rt3/bin/rt-mailgate line
108, <> chunk 1.
procmail: [30435] Mon Apr 25 09:07:41 2005
procmail: Assigning "LASTFOLDER=/opt/rt3/bin/rt-mailgate --queue general
–action correspond --url https://rt.example.com --debug"
procmail: Notified comsat: "rt_dispatcher@:/opt/rt3/bin/rt-mailgate
–queue general --action correspond --url https://rt.example.com --debug"
From MAILER-DAEMON Mon Apr 25 09:07:31 2005
Folder: /opt/rt3/bin/rt-mailgate --queue general --action correspond
32382

Phil Lawrence wrote:

Over the weekend I seem to have built up a 23M procmail log for my test
box… Can anyone help me find the cause/stop this loop?

Here’s a bit of the procmail log:

Also here’s a bit from /var/log/maillog:

Apr 25 09:15:12 localhost postfix/qmgr[2530]: C2532102E5: removed
Apr 25 09:15:13 localhost postfix/pickup[31921]: 1D81B102ED: uid=48
from=
Apr 25 09:15:13 localhost postfix/cleanup[31805]: 1D81B102ED:
message-id=20050425131513.1D81B102ED@localhost.localdomain
Apr 25 09:15:13 localhost postfix/qmgr[2530]: 1D81B102ED:
from=apache@localhost.localdomain, size=34397, nrcpt=1 (queue active)
Apr 25 09:15:13 localhost postfix/local[31806]: 1D81B102ED:
to=root@localhost.localdomain,
orig_to=MAILER-DAEMON@localhost.localdomain, relay=local, delay=0,
status=bounced (can’t create user output file. Command output: procmail:
Couldn’t create “/var/mail/nobody” )
Apr 25 09:15:13 localhost postfix/cleanup[31567]: 34AB1102E5:
message-id=20050425131513.34AB1102E5@localhost.localdomain
Apr 25 09:15:13 localhost postfix/qmgr[2530]: 34AB1102E5: from=<>,
size=36453, nrcpt=1 (queue active)
Apr 25 09:15:13 localhost postfix/qmgr[2530]: 1D81B102ED: removed
Apr 25 09:15:13 localhost postfix/local[32417]: 34AB1102E5:
to=root@localhost.localdomain, orig_to=apache@localhost.localdomain,
relay=local, delay=0, status=bounced (can’t create user output file.
Command output: procmail: Couldn’t create “/var/mail/nobody” )
Apr 25 09:15:13 localhost postfix/qmgr[2530]: 34AB1102E5: removed
Apr 25 09:15:13 localhost postfix/local[30925]: 686E910E72:
to=rt_dispatcher@localhost.localdomain,
orig_to=apache@rt.example.com, relay=local, delay=214045, status=sent
(delivered to command: /usr/bin/procmail)
Apr 25 09:15:13 localhost postfix/qmgr[2530]: 686E910E72: removed

OK, here’s an actual message:

From MAILER-DAEMON Fri Apr 22 21:08:05 2005
X-Original-To: apache@rt.example.com
Delivered-To: rt_dispatcher@localhost.localdomainDate: Fri, 22 Apr 2005 21:07:42 -0400 (EDT)
From: MAILER-DAEMON@localhost.localdomain (Mail Delivery System)
Subject: Undelivered Mail Returned to Sender
To: apache@rt.example.com
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
boundary="CCA10117CB.1114218462/localhost.localdomain"
Content-Transfer-Encoding: 8bit

This is a MIME-encapsulated message.

–CCA10117CB.1114218462/localhost.localdomain
Content-Description: Notification
Content-Type: text/plain

This is the Postfix program at host localhost.localdomain.

I’m sorry to have to inform you that your message could not be
be delivered to one or more recipients. It’s attached below.

For further assistance, please send mail to

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

                     The Postfix program

rt_dispatcher@rt.example.com (expanded from ): mail for
rt.example.com loops back to myself

–CCA10117CB.1114218462/localhost.localdomain
Content-Description: Delivery report
Content-Type: message/delivery-status

Reporting-MTA: dns; localhost.localdomain
X-Postfix-Queue-ID: CCA10117CB
X-Postfix-Sender: rfc822; apache@rt.example.com
Arrival-Date: Fri, 22 Apr 2005 15:02:15 -0400 (EDT)
Final-Recipient: rfc822; rt_dispatcher@rt.example.com
Original-Recipient: rfc822; root
Action: failed
Status: 5.0.0
Diagnostic-Code: X-Postfix; mail for rt.example.com loops back to
myself

–CCA10117CB.1114218462/localhost.localdomain
Content-Description: Undelivered Message
Content-Type: message/rfc822
Content-Transfer-Encoding: 8bit

Received: by rt.example.com (Postfix, from userid 48)
id CCA10117CB; Fri, 22 Apr 2005 15:02:15 -0400 (EDT)
Content-Type: multipart/mixed; boundary="----------=_1114196535-2809-18087"
Content-Transfer-Encoding: binary
MIME-Version: 1.0
X-Mailer: MIME-tools 5.417 (Entity 5.417)
From: RT_CorrespondAddressNotSet@rt.example.com
To: root@rt.example.com
Subject: Could not load a valid user
X-RT-Loop-Prevention: testesirt
Message-Id: 20050422190215.CCA10117CB@rt.example.com
Date: Fri, 22 Apr 2005 15:02:15 -0400 (EDT)

This is a multi-part message in MIME format…

------------=_1114196535-2809-18087
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: binary

RT could not load a valid user, and RT’s configuration does not allow
for the creation of a new user for this email
(RT_CorrespondAddressNotSet@rt.example.com).

You might need to grant ‘Everyone’ the right ‘CreateTicket’ for the
queue general.

------------=_1114196535-2809-18087
Received: by rt.example.com (Postfix, from userid 48) id D5D9310EF6;
Fri, 22 Apr 2005 09:18:22 -0400 (EDT)
Delivered-To: rt_dispatcher@rt.example.comSubject: Could not load a
valid user
MIME-Version: 1.0
Return-Path: apache@rt.example.com
X-Mailer: MIME-tools 5.417 (Entity 5.417)
X-Original-To: root
Date: Fri, 22 Apr 2005 09:18:22 -0400 (EDT)
Message-ID: 20050422131822.D5D9310EF6@rt.example.com
Content-Type: multipart/mixed; boundary="----------=_1114175902-2809-9043"
X-RT-Loop-Prevention: testesirt
To: root@rt.example.com
Content-Transfer-Encoding: binary
From: RT_CorrespondAddressNotSet@rt.example.com

This is a multi-part message in MIME format…

------------=_1114175902-2809-9043
content-type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: ascii

RT could not load a valid user, and RT’s configuration does not allow
for the creation of a new user for this email
(RT_CorrespondAddressNotSet@rt.example.com).

You might need to grant ‘Everyone’ the right ‘CreateTicket’ for the
queue general.

------------=_1114175902-2809-9043
Received: by rt.example.com (Postfix, from userid 48) id DE06710856;
Fri, 22 Apr 2005 06:33:35 -0400 (EDT)
Delivered-To: rt_dispatcher@rt.example.com
MIME-Version: 1.0
Subject: Could not load a valid user
Return-Path: apache@rt.example.com
X-Original-To: root
X-Mailer: MIME-tools 5.417 (Entity 5.417)
Date: Fri, 22 Apr 2005 06:33:35 -0400 (EDT)
Content-Type: multipart/mixed; boundary="----------=_1114166015-2809-4521"
Message-ID: 20050422103335.DE06710856@rt.example.com
To: root@rt.example.com
X-RT-Loop-Prevention: testesirt
Content-Transfer-Encoding: binary
From: RT_CorrespondAddressNotSet@rt.example.com

This is a multi-part message in MIME format…

------------=_1114166015-2809-4521
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: ascii
X-RT-Original-Encoding: utf-8

RT could not load a valid user, and RT’s configuration does not allow
for the creation of a new user for this email
(RT_CorrespondAddressNotSet@rt.example.com).

You might need to grant ‘Everyone’ the right ‘CreateTicket’ for the
queue general.

------------=_1114166015-2809-4521
Received: by rt.example.com (Postfix, from userid 48) id 67EE810A8C;
Fri, 22 Apr 2005 05:14:43 -0400 (EDT)
Delivered-To: rt_dispatcher@rt.example.com
Subject: Could not load a valid user
MIME-Version: 1.0
Return-Path: apache@rt.example.com
X-Mailer: MIME-tools 5.417 (Entity 5.417)
X-Original-To: RT_CorrespondAddressNotSet@rt.example.com
Date: Fri, 22 Apr 2005 05:14:43 -0400 (EDT)
Message-ID: 20050422091443.67EE810A8C@rt.example.com
Content-Type: multipart/mixed; boundary="----------=_1114161283-2809-2260"
X-RT-Loop-Prevention: testesirt
To: RT_CorrespondAddressNotSet@rt.example.com
Content-Transfer-Encoding: binary
From: RT_CorrespondAddressNotSet@rt.example.com

This is a multi-part message in MIME format…

------------=_1114161283-2809-2260
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: ascii
X-RT-Original-Encoding: utf-8
X-RT-Original-Encoding: utf-8

RT could not load a valid user, and RT’s configuration does not allow
for the creation of a new user for your email.

------------=_1114161283-2809-2260
Received: by rt.example.com (Postfix, from userid 48) id 40DFB106AE;
Fri, 22 Apr 2005 04:36:57 -0400 (EDT)
Delivered-To: rt_dispatcher@rt.example.com
MIME-Version: 1.0
Subject: Could not load a valid user
Return-Path: apache@rt.example.com
X-Original-To: root
X-Mailer: MIME-tools 5.417 (Entity 5.417)
Date: Fri, 22 Apr 2005 04:36:57 -0400 (EDT)
Content-Type: multipart/mixed; boundary="----------=_1114159016-2809-1129"
Message-ID: 20050422083657.40DFB106AE@rt.example.com
To: root@rt.example.com
X-RT-Loop-Prevention: testesirt
Content-Transfer-Encoding: binary
From: RT_CorrespondAddressNotSet@rt.example.com

This is a multi-part message in MIME format…

------------=_1114159016-2809-1129
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: ascii
X-RT-Original-Encoding: utf-8
X-RT-Original-Encoding: utf-8
X-RT-Original-Encoding: utf-8

RT could not load a valid user, and RT’s configuration does not allow
for the creation of a new user for this email
(RT_CorrespondAddressNotSet@rt.example.com).

You might need to grant ‘Everyone’ the right ‘CreateTicket’ for the
queue general.

------------=_1114159016-2809-1129
Received: by rt.example.com (Postfix, from userid 48) id A149B1073C;
Fri, 22 Apr 2005 04:18:54 -0400 (EDT)
Delivered-To: rt_dispatcher@rt.example.com
Subject: Could not load a valid user
MIME-Version: 1.0
Return-Path: apache@rt.example.com
X-Mailer: MIME-tools 5.417 (Entity 5.417)
X-Original-To: RT_CorrespondAddressNotSet@rt.example.com
Date: Fri, 22 Apr 2005 04:18:54 -0400 (EDT)
Message-ID: 20050422081854.A149B1073C@rt.example.com
Content-Type: multipart/mixed; boundary="----------=_1114157934-2809-564"
X-RT-Loop-Prevention: testesirt
To: RT_CorrespondAddressNotSet@rt.example.com
Content-Transfer-Encoding: binary
From: RT_CorrespondAddressNotSet@rt.example.com

This is a multi-part message in MIME format…

------------=_1114157934-2809-564
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: ascii
X-RT-Original-Encoding: utf-8
X-RT-Original-Encoding: utf-8
X-RT-Original-Encoding: utf-8
X-RT-Original-Encoding: utf-8

RT could not load a valid user, and RT’s configuration does not allow
for the creation of a new user for your email.

------------=_1114157934-2809-564
Received: by rt.example.com (Postfix, from userid 48) id EE62710307;
Fri, 22 Apr 2005 04:10:17 -0400 (EDT)
Delivered-To: rt_dispatcher@rt.example.com
MIME-Version: 1.0
Subject: Could not load a valid user
Return-Path: apache@rt.example.com
X-Original-To: root
X-Mailer: MIME-tools 5.417 (Entity 5.417)
Date: Fri, 22 Apr 2005 04:10:17 -0400 (EDT)
Content-Type: multipart/mixed; boundary="----------=_1114157417-2809-281"
Message-ID: 20050422081017.EE62710307@rt.example.com
To: root@rt.example.com
X-RT-Loop-Prevention: testesirt
Content-Transfer-Encoding: binary
From: RT_CorrespondAddressNotSet@rt.example.com

This is a multi-part message in MIME format…

------------=_1114157417-2809-281
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: ascii
X-RT-Original-Encoding: utf-8
X-RT-Original-Encoding: utf-8
X-RT-Original-Encoding: utf-8
X-RT-Original-Encoding: utf-8
X-RT-Original-Encoding: utf-8

RT could not load a valid user, and RT’s configuration does not allow
for the creation of a new user for this email
(RT_CorrespondAddressNotSet@rt.example.com).

You might need to grant ‘Everyone’ the right ‘CreateTicket’ for the
queue general.

------------=_1114157417-2809-281
Received: by rt.example.com (Postfix, from userid 48) id B3FEE10330;
Fri, 22 Apr 2005 04:05:59 -0400 (EDT)
Delivered-To: rt_dispatcher@rt.example.com
Subject: Could not load a valid user
MIME-Version: 1.0
Return-Path: apache@rt.example.com
X-Mailer: MIME-tools 5.417 (Entity 5.417)
X-Original-To: RT_CorrespondAddressNotSet@rt.example.com
Date: Fri, 22 Apr 2005 04:05:59 -0400 (EDT)
Message-ID: 20050422080559.B3FEE10330@rt.example.com
Content-Type: multipart/mixed; boundary="----------=_1114157159-2809-140"
X-RT-Loop-Prevention: testesirt
To: RT_CorrespondAddressNotSet@rt.example.com
Content-Transfer-Encoding: binary
From: RT_CorrespondAddressNotSet@rt.example.com

This is a multi-part message in MIME format…

Did you do anything to the config files? This looks like you are trying
to use an installation that you haven’t finished setting up.

DB

Phil Lawrence wrote:

OK, here’s an actual message:

From MAILER-DAEMON Fri Apr 22 21:08:05 2005
X-Original-To: apache@rt.example.com
Delivered-To: rt_dispatcher@localhost.localdomain
Date: Fri, 22 Apr 2005 21:07:42 -0400 (EDT)
From: MAILER-DAEMON@localhost.localdomain (Mail Delivery System)
Subject: Undelivered Mail Returned to Sender
To: apache@rt.example.com
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
boundary="CCA10117CB.1114218462/localhost.localdomain"
Content-Transfer-Encoding: 8bit

This is a MIME-encapsulated message.

–CCA10117CB.1114218462/localhost.localdomain
Content-Description: Notification
Content-Type: text/plain

This is the Postfix program at host localhost.localdomain.

I’m sorry to have to inform you that your message could not be
be delivered to one or more recipients. It’s attached below.

For further assistance, please send mail to

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

                    The Postfix program

rt_dispatcher@rt.example.com (expanded from ): mail for
rt.example.com loops back to myself

–CCA10117CB.1114218462/localhost.localdomain
Content-Description: Delivery report
Content-Type: message/delivery-status

Reporting-MTA: dns; localhost.localdomain
X-Postfix-Queue-ID: CCA10117CB
X-Postfix-Sender: rfc822; apache@rt.example.com
Arrival-Date: Fri, 22 Apr 2005 15:02:15 -0400 (EDT)
Final-Recipient: rfc822; rt_dispatcher@rt.example.com
Original-Recipient: rfc822; root
Action: failed
Status: 5.0.0
Diagnostic-Code: X-Postfix; mail for rt.example.com loops back to
myself

–CCA10117CB.1114218462/localhost.localdomain
Content-Description: Undelivered Message
Content-Type: message/rfc822
Content-Transfer-Encoding: 8bit

Received: by rt.example.com (Postfix, from userid 48)
id CCA10117CB; Fri, 22 Apr 2005 15:02:15 -0400 (EDT)
Content-Type: multipart/mixed;
boundary="----------=_1114196535-2809-18087"
Content-Transfer-Encoding: binary
MIME-Version: 1.0
X-Mailer: MIME-tools 5.417 (Entity 5.417)
From: RT_CorrespondAddressNotSet@rt.example.com
To: root@rt.example.com
Subject: Could not load a valid user
X-RT-Loop-Prevention: testesirt
Message-Id: 20050422190215.CCA10117CB@rt.example.com
Date: Fri, 22 Apr 2005 15:02:15 -0400 (EDT)

This is a multi-part message in MIME format…

------------=_1114196535-2809-18087
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: binary

RT could not load a valid user, and RT’s configuration does not allow
for the creation of a new user for this email
(RT_CorrespondAddressNotSet@rt.example.com).

You might need to grant ‘Everyone’ the right ‘CreateTicket’ for the
queue general.

------------=_1114196535-2809-18087
Received: by rt.example.com (Postfix, from userid 48) id D5D9310EF6;
Fri, 22 Apr 2005 09:18:22 -0400 (EDT)
Delivered-To: rt_dispatcher@rt.example.comSubject: Could not load a
valid user
MIME-Version: 1.0
Return-Path: apache@rt.example.com
X-Mailer: MIME-tools 5.417 (Entity 5.417)
X-Original-To: root
Date: Fri, 22 Apr 2005 09:18:22 -0400 (EDT)
Message-ID: 20050422131822.D5D9310EF6@rt.example.com
Content-Type: multipart/mixed;
boundary="----------=_1114175902-2809-9043"
X-RT-Loop-Prevention: testesirt
To: root@rt.example.com
Content-Transfer-Encoding: binary
From: RT_CorrespondAddressNotSet@rt.example.com

This is a multi-part message in MIME format…

------------=_1114175902-2809-9043
content-type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: ascii

RT could not load a valid user, and RT’s configuration does not allow
for the creation of a new user for this email
(RT_CorrespondAddressNotSet@rt.example.com).

You might need to grant ‘Everyone’ the right ‘CreateTicket’ for the
queue general.

------------=_1114175902-2809-9043
Received: by rt.example.com (Postfix, from userid 48) id DE06710856;
Fri, 22 Apr 2005 06:33:35 -0400 (EDT)
Delivered-To: rt_dispatcher@rt.example.com
MIME-Version: 1.0
Subject: Could not load a valid user
Return-Path: apache@rt.example.com
X-Original-To: root
X-Mailer: MIME-tools 5.417 (Entity 5.417)
Date: Fri, 22 Apr 2005 06:33:35 -0400 (EDT)
Content-Type: multipart/mixed;
boundary="----------=_1114166015-2809-4521"
Message-ID: 20050422103335.DE06710856@rt.example.com
To: root@rt.example.com
X-RT-Loop-Prevention: testesirt
Content-Transfer-Encoding: binary
From: RT_CorrespondAddressNotSet@rt.example.com

This is a multi-part message in MIME format…

------------=_1114166015-2809-4521
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: ascii
X-RT-Original-Encoding: utf-8

RT could not load a valid user, and RT’s configuration does not allow
for the creation of a new user for this email
(RT_CorrespondAddressNotSet@rt.example.com).

You might need to grant ‘Everyone’ the right ‘CreateTicket’ for the
queue general.

------------=_1114166015-2809-4521
Received: by rt.example.com (Postfix, from userid 48) id 67EE810A8C;
Fri, 22 Apr 2005 05:14:43 -0400 (EDT)
Delivered-To: rt_dispatcher@rt.example.com
Subject: Could not load a valid user
MIME-Version: 1.0
Return-Path: apache@rt.example.com
X-Mailer: MIME-tools 5.417 (Entity 5.417)
X-Original-To: RT_CorrespondAddressNotSet@rt.example.com
Date: Fri, 22 Apr 2005 05:14:43 -0400 (EDT)
Message-ID: 20050422091443.67EE810A8C@rt.example.com
Content-Type: multipart/mixed;
boundary="----------=_1114161283-2809-2260"
X-RT-Loop-Prevention: testesirt
To: RT_CorrespondAddressNotSet@rt.example.com
Content-Transfer-Encoding: binary
From: RT_CorrespondAddressNotSet@rt.example.com

This is a multi-part message in MIME format…

------------=_1114161283-2809-2260
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: ascii
X-RT-Original-Encoding: utf-8
X-RT-Original-Encoding: utf-8

RT could not load a valid user, and RT’s configuration does not allow
for the creation of a new user for your email.

------------=_1114161283-2809-2260
Received: by rt.example.com (Postfix, from userid 48) id 40DFB106AE;
Fri, 22 Apr 2005 04:36:57 -0400 (EDT)
Delivered-To: rt_dispatcher@rt.example.com
MIME-Version: 1.0
Subject: Could not load a valid user
Return-Path: apache@rt.example.com
X-Original-To: root
X-Mailer: MIME-tools 5.417 (Entity 5.417)
Date: Fri, 22 Apr 2005 04:36:57 -0400 (EDT)
Content-Type: multipart/mixed;
boundary="----------=_1114159016-2809-1129"
Message-ID: 20050422083657.40DFB106AE@rt.example.com
To: root@rt.example.com
X-RT-Loop-Prevention: testesirt
Content-Transfer-Encoding: binary
From: RT_CorrespondAddressNotSet@rt.example.com

This is a multi-part message in MIME format…

------------=_1114159016-2809-1129
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: ascii
X-RT-Original-Encoding: utf-8
X-RT-Original-Encoding: utf-8
X-RT-Original-Encoding: utf-8

RT could not load a valid user, and RT’s configuration does not allow
for the creation of a new user for this email
(RT_CorrespondAddressNotSet@rt.example.com).

You might need to grant ‘Everyone’ the right ‘CreateTicket’ for the
queue general.

------------=_1114159016-2809-1129
Received: by rt.example.com (Postfix, from userid 48) id A149B1073C;
Fri, 22 Apr 2005 04:18:54 -0400 (EDT)
Delivered-To: rt_dispatcher@rt.example.com
Subject: Could not load a valid user
MIME-Version: 1.0
Return-Path: apache@rt.example.com
X-Mailer: MIME-tools 5.417 (Entity 5.417)
X-Original-To: RT_CorrespondAddressNotSet@rt.example.com
Date: Fri, 22 Apr 2005 04:18:54 -0400 (EDT)
Message-ID: 20050422081854.A149B1073C@rt.example.com
Content-Type: multipart/mixed; boundary="----------=_1114157934-2809-564"
X-RT-Loop-Prevention: testesirt
To: RT_CorrespondAddressNotSet@rt.example.com
Content-Transfer-Encoding: binary
From: RT_CorrespondAddressNotSet@rt.example.com

This is a multi-part message in MIME format…

------------=_1114157934-2809-564
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: ascii
X-RT-Original-Encoding: utf-8
X-RT-Original-Encoding: utf-8
X-RT-Original-Encoding: utf-8
X-RT-Original-Encoding: utf-8

RT could not load a valid user, and RT’s configuration does not allow
for the creation of a new user for your email.

------------=_1114157934-2809-564
Received: by rt.example.com (Postfix, from userid 48) id EE62710307;
Fri, 22 Apr 2005 04:10:17 -0400 (EDT)
Delivered-To: rt_dispatcher@rt.example.com
MIME-Version: 1.0
Subject: Could not load a valid user
Return-Path: apache@rt.example.com
X-Original-To: root
X-Mailer: MIME-tools 5.417 (Entity 5.417)
Date: Fri, 22 Apr 2005 04:10:17 -0400 (EDT)
Content-Type: multipart/mixed; boundary="----------=_1114157417-2809-281"
Message-ID: 20050422081017.EE62710307@rt.example.com
To: root@rt.example.com
X-RT-Loop-Prevention: testesirt
Content-Transfer-Encoding: binary
From: RT_CorrespondAddressNotSet@rt.example.com

This is a multi-part message in MIME format…

------------=_1114157417-2809-281
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: ascii
X-RT-Original-Encoding: utf-8
X-RT-Original-Encoding: utf-8
X-RT-Original-Encoding: utf-8
X-RT-Original-Encoding: utf-8
X-RT-Original-Encoding: utf-8

RT could not load a valid user, and RT’s configuration does not allow
for the creation of a new user for this email
(RT_CorrespondAddressNotSet@rt.example.com).

You might need to grant ‘Everyone’ the right ‘CreateTicket’ for the
queue general.

------------=_1114157417-2809-281
Received: by rt.example.com (Postfix, from userid 48) id B3FEE10330;
Fri, 22 Apr 2005 04:05:59 -0400 (EDT)
Delivered-To: rt_dispatcher@rt.example.com
Subject: Could not load a valid user
MIME-Version: 1.0
Return-Path: apache@rt.example.com
X-Mailer: MIME-tools 5.417 (Entity 5.417)
X-Original-To: RT_CorrespondAddressNotSet@rt.example.com
Date: Fri, 22 Apr 2005 04:05:59 -0400 (EDT)
Message-ID: 20050422080559.B3FEE10330@rt.example.com
Content-Type: multipart/mixed; boundary="----------=_1114157159-2809-140"
X-RT-Loop-Prevention: testesirt
To: RT_CorrespondAddressNotSet@rt.example.com
Content-Transfer-Encoding: binary
From: RT_CorrespondAddressNotSet@rt.example.com

This is a multi-part message in MIME format…


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Be sure to check out the RT Wiki at http://wiki.bestpractical.com

Drew Barnes
Applications Analyst
Raymond Walters College
University of Cincinnati

rt_dispatcher@rt.example.com (expanded from ): mail for
rt.example.com loops back to myself

That’s an MX collision, I think. Google for “loops back to myself”,
and see what you get. You’re trying to feed root’s mail into RT?

Cheers,
– jra
Jay R. Ashworth jra@baylink.com
Designer Baylink RFC 2100
Ashworth & Associates The Things I Think '87 e24
St Petersburg FL USA http://baylink.pitas.com +1 727 647 1274

  If you can read this... thank a system administrator.  Or two.  --me

Drew Barnes wrote:

Did you do anything to the config files? This looks like you are trying
to use an installation that you haven’t finished setting up.

I think this started because I forgot to give CreateTicket to 'Everyone’
before sending a test email.

So RT replied you can’t create a ticket, but somehow that looped back to
itself, and began to build a monster loop.

Now I have granted create ticket to ‘Everyone’, and lots of tickets are
being created by MAILER-DAEMON.

But I don’t want ‘Everyone’ to be able to create tickets, only Users I
set up.

Phil