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…