5.0.0 status code
When one of our SJMS users has exceeded their mailbox quota limit, and someone sends them a message, the server returns: "Status: 5.0.0 (Over quota)" to the sender.
Which is fine when they're a gmail or another SJMS user, they'll see the explanation in parentheses.
When an Exchange 2003 user sends them an email, Exchange hides the error and reports:"The e-mail system was unable to deliver the message, but did not report a specific reason. ". When users see a message like this they assume something is wrong with their computer and start calling the helpdesk, which is bad.
According to RFC 3463, it appears that a more precise code to indicate a full mailbox is 5.2.2 ( See ftp://ftp.rfc-editor.org/in-notes/rfc3463.txt ).
I can't ask exchange admins to change their systems, so how can I send them the 5.2.2 status code (instead of 5.0.0) when a mailbox hits capacity?
My system is running:
root@ims-a:// > imsimta version
Sun Java(tm) System Messaging Server 6.2-4.03 (built Sep 22 2005)
libimta.so 6.2-4.03 (built 04:37:42, Sep 22 2005)
SunOS ims-a 5.9 Generic_118558-24 sun4u sparc SUNW,Sun-Fire-480R
[1195 byte] By [
bnderan] at [2007-11-26 10:16:39]
# 1
Hm. I don't find an exact answer for you, including the code. That message, "status: 5.0.0 (over quota)", doesn't look like one of ours, though.
# 2
Hi,A little bit of testing shows that messaging server sends out extended error codes (e.g. 4.2.2/5.2.2 for overquota). Do you have a copy of the email that had the 5.0.0 status message? Can you cut/paste the relevant section.Shane.
# 3
Shane, thanks for ruling out SJMS as a source of the problem.
Jay, thanks for taking a look too.
We use PMDF MTA for our incoming/outgoing mail gateways.
I guess that could be altering the status code before returning it to the sender.
Below is an example of a message an exchange user recieved.
From: System Administrator
Sent: Wednesday, September 20, 2006 10:21 AM
To: Shirv, Prasad
Subject: Undeliverable: Lecture today@4PM in Stern Auditorium
Your message did not reach some or all of the intended recipients.
Subject: Lecture today@4PM in Stern Auditorium
Sent:9/20/2006 10:21 AM
The following recipient(s) could not be reached:
Shirv, Prasad on 9/20/2006 10:17 AM
The e-mail system was unable to deliver the message, but did not report a specific reason. Check the address and try again. If it still fails, contact your system administrator.The MTS-ID of the original message is:0J5W00A03AB9RJ@egr-2.mssm.edu
# 4
This must be what you get from the Exchange thingy.
I think what Shane was looking for is what you actually get from your MTA.
Is there some major reason you're using PMDF instead of our MTA? It might make good sense for you to install our MTA. It has ability to query your LDAP for user and quota status, and reduce the number of messages actually processed.
# 5
I've heard back from a process.com engineer who said:
PMDF would only generate a message about being over quota if it itself
is delivering the mail locally to a popstore/msgstore user or a local
vms or unix mailbox. And PMDF wouldn't "alter" any "status code" "before returning it to the sender". So this does not appear to be a PMDF issue.
Below is a test message I sent from my own Imail account to another user on the same system. It goes to our outgoing mail gateway named egress-2 before returning a 5.0.0 status code.
Return-path: <>
Received: from egress-2.mssm.edu (egress-2.mssm.edu [146.203.100.23])
by ims.mssm.edu
(Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) with ESMTP id
<0J67009R9FMS2CD0@ims.mssm.edu> for brendan.keller@ims.mssm.edu; Tue,
26 Sep 2006 10:44:52 -0400 (EDT)
Received: from CONVERSION-DAEMON.egress-2.mssm.edu by egress-2.mssm.edu
(PMDF V6.2-1 #31335) id <0J6700L01FKYJ3@egress-2.mssm.edu> for
brendan.keller@ims.mssm.edu (ORCPT brendan.keller@mssm.edu); Tue,
26 Sep 2006 10:43:46 -0400 (EDT)
Received: from ims-a.mssm.edu ([146.203.75.40])
by egress-2.mssm.edu (PMDF V6.2-1 #31335)
with ESMTP id <0J6700J7RFKYY6@egress-2.mssm.edu> for
brendan.keller@ims.mssm.edu (ORCPT brendan.keller@mssm.edu); Tue,
26 Sep 2006 10:43:46 -0400 (EDT)
Received: from process-daemon.ims.mssm.edu by ims.mssm.edu
(Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005))
id <0J6700901ESEGV00@ims.mssm.edu> for brendan.keller@mssm.edu; Tue,
26 Sep 2006 10:44:52 -0400 (EDT)
Received: from ims.mssm.edu
(Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005))
id <0J67002K1FMSQC00@ims.mssm.edu>; Tue, 26 Sep 2006 10:44:52 -0400 (EDT)
Date: Tue, 26 Sep 2006 10:44:52 -0400 (EDT)
From: postmaster@mssm.edu
Subject: Delivery Notification: Delivery has failed
To: brendan.keller@mssm.edu
Message-id: <0J67002K3FMSQC00@ims.mssm.edu>
MIME-version: 1.0
Content-type: multipart/report; report-type=delivery-status;
boundary="Boundary_(ID_An9Q6chPdzi9RRsW1Lk5xA)"
Original-recipient: rfc822;brendan.keller@mssm.edu
[-- Attachment #1 --]
[-- Type: text/plain, Encoding: 7bit, Size: 0.4K --]
Content-type: text/plain; charset=us-ascii
Content-language: en-US
Content-transfer-encoding: 7BIT
This report relates to a message you sent with the following header fields:
Message-id: <45193CE0.9020701@mssm.edu>
Date: Tue, 26 Sep 2006 10:44:48 -0400
From: Brendan <brendan.keller@mssm.edu>
To: paulfoo.zambar@mssm.edu
Subject: Test from Imail account
Your message cannot be delivered to the following recipients:
Recipient address: paulfoo.zambar@ims.mssm.edu
Original address: paulfoo.zambar@mssm.edu
Reason: Over quota
[-- Attachment #2 --]
[-- Type: message/delivery-status, Encoding: 7bit, Size: 0.2K --]
Content-type: message/delivery-status
Original-envelope-id: 0J6700L03FKYJ1@egress-2.mssm.edu
Reporting-MTA: dns;ims.mssm.edu (ims-ms-daemon)
Original-recipient: rfc822;paulfoo.zambar@mssm.edu
Final-recipient: rfc822;paulfoo.zambar@ims.mssm.edu
Action: failed
Status: 5.0.0 (Over quota)
[-- Attachment #3 --]
[-- Type: message/rfc822, Encoding: 7bit, Size: 1.3K --]
Content-type: message/rfc822
Return-path: brendan.keller@mssm.edu
Received: from ims-ms-daemon.ims.mssm.edu by ims.mssm.edu
(Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005))
id <0J67002K1FMSQC00@ims.mssm.edu>; Tue, 26 Sep 2006 10:44:52 -0400 (EDT)
Received: from egress-2.mssm.edu (egress-2.mssm.edu [146.203.100.23])
by ims.mssm.edu
(Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) with ESMTP id
<0J67009XMFMS2AE0@ims.mssm.edu> for paulfoo.zambar@ims.mssm.edu; Tue,
26 Sep 2006 10:44:52 -0400 (EDT)
Received: from CONVERSION-DAEMON.egress-2.mssm.edu by egress-2.mssm.edu
(PMDF V6.2-1 #31335) id <0J6700L01FKYJ1@egress-2.mssm.edu> for
paulfoo.zambar@ims.mssm.edu (ORCPT paulfoo.zambar@mssm.edu); Tue,
26 Sep 2006 10:43:46 -0400 (EDT)
Received: from [146.203.8.32] by egress-2.mssm.edu (PMDF V6.2-1 #31335)
with ESMTP id <0J6700J7NFKXY6@egress-2.mssm.edu> for paulfoo.zambar@ims.mssm.edu
(ORCPT paulfoo.zambar@mssm.edu); Tue, 26 Sep 2006 10:43:46 -0400 (EDT)
Date: Tue, 26 Sep 2006 10:44:48 -0400
From: Brendan <brendan.keller@mssm.edu>
Subject: Test from Imail account
To: paulfoo.zambar@mssm.edu
Message-id: <45193CE0.9020701@mssm.edu>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Thunderbird 1.5.0.5 (X11/20060728)
Test, please ignore this.
# 6
When sent from Gmail.com, gmail now returns a new status code:
Status: 5.963.624 (Over quota)
Strange, because it was returning a 5.0.0 code last week.
I've altered the recepient email address slightly (added foo and bar) to stop spam to this otherwise inactive account.
Tue, 26 Sep 2006 07:42:34 -0700 (PDT)
Received-SPF: pass (gmail.com: best guess record for domain of egress-2.mssm.edu designates 146.203.100.23 as permitted sender)
Received: from CONVERSION-DAEMON.egress-2.mssm.edu by egress-2.mssm.edu
(PMDF V6.2-1 #31335) id <0J6700L01FGX1K@egress-2.mssm.edu> for
bkeller@gmail.com; Tue, 26 Sep 2006 10:41:22 -0400 (EDT)
Received: from ims-a.mssm.edu ([146.203.75.40])
by egress-2.mssm.edu (PMDF V6.2-1 #31335)
with ESMTP id <0J6700J5LFGXY6@egress-2.mssm.edu> for bkeller@gmail.com; Tue,
26 Sep 2006 10:41:22 -0400 (EDT)
Received: from process-daemon.ims.mssm.edu by ims.mssm.edu
(Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005))
id <0J6700901ESEGV00@ims.mssm.edu> for bkeller@gmail.com; Tue,
26 Sep 2006 10:42:27 -0400 (EDT)
Received: from ims.mssm.edu
(Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005))
id <0J67002JQFIRQC00@ims.mssm.edu>; Tue, 26 Sep 2006 10:42:27 -0400 (EDT)
Date: Tue, 26 Sep 2006 10:42:27 -0400 (EDT)
From: Internet Mail Delivery <postmaster@mssm.edu>
Subject: Delivery Notification: Delivery has failed
To: bkeller@gmail.com
Message-id: <0J67002JSFIRQC00@ims.mssm.edu>
MIME-version: 1.0
Content-type: multipart/report; report-type=delivery-status;
boundary="Boundary_(ID_Zwvm18WBwFQ7X4rdjhqIHw)"
--Boundary_(ID_Zwvm18WBwFQ7X4rdjhqIHw)
Content-type: text/plain; charset=us-ascii
Content-language: en-US
Content-transfer-encoding: 7BIT
This report relates to a message you sent with the following header fields:
Message-id: <62a8cfb90609260741o180c3b03nbe012c2252b456ea@mail.gmail.com>
Date: Tue, 26 Sep 2006 10:41:18 -0400
From: Brendan <bkeller@gmail.com>
To: paulfoo.zambar@mssm.edu
Subject: Test from Gmail
Your message cannot be delivered to the following recipients:
Recipient address: paulfoo.zambar@ims.mssm.edu
Original address: paulfoo.zambar@mssm.edu
Reason: Over quota
--Boundary_(ID_Zwvm18WBwFQ7X4rdjhqIHw)
Content-type: message/delivery-status
Original-envelope-id: 0J6700I07FI1TZ@ing-2.mssm.edu
Reporting-MTA: dns;ims.mssm.edu (ims-ms-daemon)
Original-recipient: rfc822;paulfoo.zambar@mssm.edu
Final-recipient: rfc822;paulfoo.zambar@ims.mssm.edu
Action: failed
Status: 5.963.624 (Over quota)
--Boundary_(ID_Zwvm18WBwFQ7X4rdjhqIHw)
Content-type: message/rfc822
Return-path: <bkeller@gmail.com>
Received: from ims-ms-daemon.ims.mssm.edu by ims.mssm.edu
(Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005))
id <0J67002JQFIRQC00@ims.mssm.edu>; Tue, 26 Sep 2006 10:42:27 -0400 (EDT)
Received: from ing-2.mssm.edu (ing-2.mssm.edu [146.203.100.22])
by ims.mssm.edu (Sun Java System Messaging Server 6.2-4.03 (built Sep 22
2005)) with ESMTP id <0J67009OGFIR2CD0@ims.mssm.edu> for
paulfoo.zambar@ims.mssm.edu; Tue, 26 Sep 2006 10:42:27 -0400 (EDT)
Received: from CONVERSION-DAEMON.ing-2.mssm.edu by ing-2.mssm.edu
(PMDF V6.2-X27 #31335) id <0J6700I01FI2VM@ing-2.mssm.edu> for
paulfoo.zambar@ims.mssm.edu (ORCPT paulfoo.zambar@mssm.edu); Tue,
26 Sep 2006 10:42:03 -0400 (EDT)
Received: from PMAS-DAEMON.ing-2.mssm.edu by ing-2.mssm.edu
(PMDF V6.2-X27 #31335) id <0J6700I06FI1TZ@ing-2.mssm.edu> for
paulfoo.zambar@ims.mssm.edu (ORCPT paulfoo.zambar@mssm.edu); Tue,
26 Sep 2006 10:42:01 -0400 (EDT)
Received: from nz-out-0102.google.com ([64.233.162.192])
by ing-2.mssm.edu (PMDF V6.2-X27 #31335)
with ESMTP id <0J6700ESSFGVQA@ing-2.mssm.edu> for paulfoo.zambar@ims.mssm.edu
(ORCPT paulfoo.zambar@mssm.edu); Tue, 26 Sep 2006 10:41:19 -0400 (EDT)
Received: by nz-out-0102.google.com with SMTP id z6so864516nzd for
<paulfoo.zambar@mssm.edu>; Tue, 26 Sep 2006 07:41:19 -0700 (PDT)
Received: by 10.64.181.12 with SMTP id d12mr1301573qbf; Tue,
26 Sep 2006 07:41:19 -0700 (PDT)
Received: by 10.65.204.14 with HTTP; Tue, 26 Sep 2006 07:41:18 -0700 (PDT)
Date: Tue, 26 Sep 2006 10:41:18 -0400
From: Brendan <bkeller@gmail.com>
Subject: Test from Gmail
To: paulfoo.zambar@mssm.edu
Message-id: <62a8cfb90609260741o180c3b03nbe012c2252b456ea@mail.gmail.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
Content-disposition: inline
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
h=received:message-id:date:from:to:subject:mime-version:content-type:content-tr ansfer-encoding:content-disposition;
b=aiWvaopfhuPqzKSMw3hPPjzMRExmS7lKnoncANRv08kzWjO9pN2kGsWZbG+uYreghF29FDbyVKy1A 6wPI85HkjUV+ldOMzwFkJO68G2/EDU4i1tSWwPCMUNgGphpN/Y3h6OjkvqLoIJmFN9F4qsAQE244I2qs KeEtYJidF9IZbU=
X-PMAS-Software: PreciseMail V2.0-1 [060922] (ing-2.mssm.edu)
X-PMAS-Not-Spam: 0.000
Test message,
please ignore.
--Boundary_(ID_Zwvm18WBwFQ7X4rdjhqIHw)--
# 7
What I'm looking at, appears to be a "DSN" (Delivery Status Notification). I"m starting to wonder how you have this system set up, honestly.
My system acts quite differently, when I have an overquota user.
When the "grace period" is still going on, I accept the message, and queue it up. When that grace period expires, I do return it, but not with a 5.0.0. your 5.963.624 is totally bugus, and non-rfc. It's not likely coming from Messaging Server.
You must have something else involved that's generating these.
