Community Discussions and Support
No from: field in message error

Yes, I believe the "pre-release" is NOT the same beta "4.80" that was released in January.  At any rate, I think Rolf resolved a post or two ago..

Yes, I believe the "pre-release" is NOT the same beta "4.80" that was released in January.  At any rate, I think Rolf resolved a post or two ago..

We're having lots of problems with this lately, mainly (all?) for people sending to mailing lists.  Apparently mercury cannot parse the headers.  We're on Mercury 4.74, running on windows 2008 r2, which has been running fine for years, then started having this problem a few months ago, and now it seems to be increasing in frequency (we see it most every day now).

 Anyone have suggestions on solutions/where to look?  Details are below.   Any help greatly appreciated.

 
COMPLETE ERROR (with "blank" subject):

With reference to your message with the subject:

   ""

 

The local mail transport system has reported the

following problems it

encountered while trying to deliver your message:

 

-------------------------------------------------------------------

*** <REFDESK@law6.law.virginia.edu>

<REFDESK@law6.law.virginia.edu>

No from: field in message

 

EXAMPLE HEADERS SENT TO POSTMASTER:

 

Subject: Postmaster Notify: Delivery Failure.

MIME-Version: 1.0

Content-type: multipart/mixed; boundary=21986.334791953

 

This message is in MIME format. If you are seeing this text,

then your mailer does not understand this format properly.

 

--21986.334791953

Content-type: Text/Plain; charset=US-ASCII

Content-Disposition: Inline

Content-Description: Reason for delivery failure.

 

The attached message has failed delivery and has been

referred

to you as postmaster. The following error report or reports

were given to explain the problem:

 

   *** <REFDESK@law6.law.virginia.edu>

   <REFDESK@law6.law.virginia.edu>

   No from: field in message.

 

--21986.334791953

Content-type: Message/RFC822

 

Return-path: <aaw7mh@eservices.virginia.edu>

Received: from garlic.mail.virginia.edu (128.143.2.118) by

law6.lawschool.virginia.edu (Mercury/32 v4.72) with ESMTP ID MG000062;

   9 Dec 2014 14:31:13 -0500

Received: from localhost (localhost [127.0.0.1])

               

by garlic.mail.virginia.edu (Postfix) with ESMTP id 2F0C62261FF

               

for <REFDESK@law6.law.virginia.edu>;

Tue,  9 Dec 2014 14:31:13 -0500 (EST)

Received: from garlic.mail.virginia.edu ([127.0.0.1])

               

by localhost (garlic-f.mail.virginia.edu [127.0.0.1]) (amavisd-new, port 10024)

               

with ESMTP id T4e3+SsUsh06 for <REFDESK@law6.law.virginia.edu>;

               

Tue,  9 Dec 2014 14:31:13 -0500 (EST)

Received: from iron5.mail.virginia.edu

(iron5-s.mail.virginia.edu [10.250.200.115])

               

by garlic.mail.virginia.edu (Postfix) with ESMTP id 0A9132261D7

               

for <REFDESK@law6.law.virginia.edu>;

Tue,  9 Dec 2014 14:31:13 -0500 (EST)

X-IronPort-Anti-Spam-Filtered: true

X-IronPort-Anti-Spam-Result:

AlAGAMFNh1QK+sjw/2dsb2JhbABWAw6CNUNSWATDeYIigx6CbwKBKxYBAQEBAX2EAgEBAQQFIAgBSxACAQUDEQQBAQYBAQECCBUHAgUQAQwCDBQJCAEBBA4EAQYCBogq0jyFFAEBAQEBAQEBAQEBAQEBAQEBAQEBARePTzwWCxAGAQkIgxCBFQWODYMKAWSFJoENgl8EjXqDLz8/MAGBRH4BAQE

X-IPAS-Result:

AlAGAMFNh1QK+sjw/2dsb2JhbABWAw6CNUNSWATDeYIigx6CbwKBKxYBAQEBAX2EAgEBAQQFIAgBSxACAQUDEQQBAQYBAQECCBUHAgUQAQwCDBQJCAEBBA4EAQYCBogq0jyFFAEBAQEBAQEBAQEBAQEBAQEBAQEBARePTzwWCxAGAQkIgxCBFQWODYMKAWSFJoENgl8EjXqDLz8/MAGBRH4BAQE

X-Sender-IP: 10.250.200.240

Received: from iron3-s.mail.virginia.edu (HELO

iron3.mail.virginia.edu) ([10.250.200.240])

  by iron5.mail.virginia.edu with ESMTP; 09 Dec 2014

14:31:12 -0500

X-IronPort-Anti-Spam-Filtered: true

X-IronPort-Anti-Spam-Result:

AlIGAMRMh1QK+sgR/2dsb2JhbABWAw6CNUNSWATDeYIigQKCHIJvAoErFgEBAQEBAXyEAgEBAQEDBSAIAUsQAgEFAxEEAQEGAQEBAggVBwIFEAEMAgwUCQgBAQQOBAEGAgaIKtI5hRQBAQEBAQEBAQEBAQEBAQEBAQEBAQEXj088FgsQBgEJCIMQgRUFjg2DCgFkhSaBDYJfBI16gy8/PzABgUR+AQEB

X-IPAS-Result:

AlIGAMRMh1QK+sgR/2dsb2JhbABWAw6CNUNSWATDeYIigQKCHIJvAoErFgEBAQEBAXyEAgEBAQEDBSAIAUsQAgEFAxEEAQEGAQEBAggVBwIFEAEMAgwUCQgBAQQOBAEGAgaIKtI5hRQBAQEBAQEBAQEBAQEBAQEBAQEBAQEXj088FgsQBgEJCIMQgRUFjg2DCgFkhSaBDYJfBI16gy8/PzABgUR+AQEB

X-IronPort-AV: E=Sophos;i="5.07,547,1413259200";

   d="jpg'145?scan'145,208,217,145";a="9153656"

X-Sender-IP: 10.250.200.17

Received: from adams1-s.eservices.virginia.edu (HELO

adams1.eservices.virginia.edu) ([10.250.200.17])

  by iron3.mail.virginia.edu with ESMTP; 09 Dec 2014

14:30:12 -0500

Received: from GRANT1.eservices.virginia.edu

([fe80::991f:95f0:f798:60a3]) by

adams1.eservices.virginia.edu ([::1]) with mapi id

14.02.0342.003; Tue, 9 Dec

2014 14:29:50 -0500

From: "Wharton, Amy Ann

(aaw7mh)" <aaw7mh@eservices.virginia.edu>

To: "Monahan, John T. (jtm9p)" <jtm9p@virginia.edu>

CC: Reference Librarians <REFDESK@law6.law.virginia.edu>

Subject: RE: help

Thread-Topic: help

Thread-Index: AdAT4f5jigMTC5aqQ168JlxTO8mQvgABGoDw

Date: Tue, 9 Dec 2014 19:29:50 +0000

Message-ID: <6D6C0A77EEBB3D44AE7C772B41B88C569B89B77D@grant1.eservices.virginia.edu>

References: <332800578.3008.1418133488@law6.law.virginia.edu>

In-Reply-To: <332800578.3008.1418133488@law6.law.virginia.edu>

Accept-Language: en-US

Content-Language: en-US

X-MS-Has-Attach: yes

X-MS-TNEF-Correlator:

x-originating-ip: [137.54.253.218]

Content-Type: multipart/related;

               

boundary="_004_6D6C0A77EEBB3D44AE7C772B41B88C569B89B77Dgrant1eservices_";

               

type="multipart/alternative"

MIME-Version: 1.0

 

--_004_6D6C0A77EEBB3D44AE7C772B41B88C569B89B77Dgrant1eservices_

Content-Type: multipart/alternative;

               

boundary="_000_6D6C0A77EEBB3D44AE7C772B41B88C569B89B77Dgrant1eservices_"

 

--_000_6D6C0A77EEBB3D44AE7C772B41B88C569B89B77Dgrant1eservices_

Content-Type: text/plain; charset="us-ascii"

Content-Transfer-Encoding: quoted-printable

  

. 

&lt;p&gt;We&#039;re having lots of problems with this lately, mainly (all?) for people sending to mailing lists. &amp;nbsp;Apparently mercury cannot parse the headers. &amp;nbsp;We&#039;re on Mercury 4.74, running on windows 2008 r2, which has been running fine for years, then started having this problem a few months ago, and now it seems to be increasing in frequency (we see it most every day now).&lt;/p&gt;&lt;p&gt;&amp;nbsp;Anyone have suggestions on solutions/where to look? &amp;nbsp;Details are below.&lt;span style=&quot;font-size: 10pt;&quot;&gt;&amp;nbsp; &amp;nbsp;Any help greatly appreciated.&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&amp;nbsp; COMPLETE ERROR (with &quot;blank&quot; subject):&lt;/p&gt;&lt;p class=&quot;MsoPlainText&quot;&gt;With reference to your message with the subject:&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoPlainText&quot;&gt;&amp;nbsp;&amp;nbsp; &quot;&quot;&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoPlainText&quot;&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;span style=&quot;font-size: 10pt;&quot;&gt;The local mail transport system has reported the following problems it&lt;/span&gt;&lt;/p&gt;&lt;p class=&quot;MsoPlainText&quot;&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoPlainText&quot;&gt;encountered while trying to deliver your message:&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoPlainText&quot;&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoPlainText&quot;&gt;-------------------------------------------------------------------&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoPlainText&quot;&gt;*** &amp;lt;&lt;a mce_href=&quot;mailto:REFDESK@law6.law.virginia.edu&quot; href=&quot;mailto:REFDESK@law6.law.virginia.edu&quot;&gt;REFDESK@law6.law.virginia.edu&lt;/a&gt;&amp;gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoPlainText&quot;&gt;&amp;lt;&lt;a mce_href=&quot;mailto:REFDESK@law6.law.virginia.edu&quot; href=&quot;mailto:REFDESK@law6.law.virginia.edu&quot;&gt;REFDESK@law6.law.virginia.edu&lt;/a&gt;&amp;gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoPlainText&quot;&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;&lt;p&gt;&lt;span style=&quot;font-size: 10pt;&quot;&gt;No from: field in message&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;span style=&quot;font-size: 10pt;&quot;&gt;EXAMPLE HEADERS SENT TO POSTMASTER:&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p class=&quot;MsoNormal&quot;&gt;Subject: Postmaster Notify: Delivery Failure.&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;MIME-Version: 1.0&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;Content-type: multipart/mixed; boundary=21986.334791953&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;This message is in MIME format. If you are seeing this text,&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;then your mailer does not understand this format properly.&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;--21986.334791953&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;Content-type: Text/Plain; charset=US-ASCII&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;Content-Disposition: Inline&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;Content-Description: Reason for delivery failure.&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;The attached message has failed delivery and has been referred&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;to you as postmaster. The following error report or reports&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;were given to explain the problem:&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;&amp;nbsp;&amp;nbsp; *** &amp;lt;&lt;a mce_href=&quot;mailto:REFDESK@law6.law.virginia.edu&quot; href=&quot;mailto:REFDESK@law6.law.virginia.edu&quot;&gt;REFDESK@law6.law.virginia.edu&lt;/a&gt;&amp;gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;lt;&lt;a mce_href=&quot;mailto:REFDESK@law6.law.virginia.edu&quot; href=&quot;mailto:REFDESK@law6.law.virginia.edu&quot;&gt;REFDESK@law6.law.virginia.edu&lt;/a&gt;&amp;gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;&amp;nbsp;&amp;nbsp; No from: field in message.&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;--21986.334791953&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;Content-type: Message/RFC822&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;Return-path: &amp;lt;&lt;a mce_href=&quot;mailto:aaw7mh@eservices.virginia.edu&quot; href=&quot;mailto:aaw7mh@eservices.virginia.edu&quot;&gt;aaw7mh@eservices.virginia.edu&lt;/a&gt;&amp;gt; &lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;Received: from garlic.mail.virginia.edu (128.143.2.118) by law6.lawschool.virginia.edu (Mercury/32 v4.72) with ESMTP ID MG000062;&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;&amp;nbsp;&amp;nbsp; 9 Dec 2014 14:31:13 -0500&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;Received: from localhost (localhost [127.0.0.1])&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; by garlic.mail.virginia.edu (Postfix) with ESMTP id 2F0C62261FF&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; for &amp;lt;&lt;a mce_href=&quot;mailto:REFDESK@law6.law.virginia.edu&quot; href=&quot;mailto:REFDESK@law6.law.virginia.edu&quot;&gt;REFDESK@law6.law.virginia.edu&lt;/a&gt;&amp;gt;; Tue,&amp;nbsp; 9 Dec 2014 14:31:13 -0500 (EST)&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;Received: from garlic.mail.virginia.edu ([127.0.0.1])&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; by localhost (garlic-f.mail.virginia.edu [127.0.0.1]) (amavisd-new, port 10024)&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; with ESMTP id T4e3+SsUsh06 for &amp;lt;&lt;a mce_href=&quot;mailto:REFDESK@law6.law.virginia.edu&quot; href=&quot;mailto:REFDESK@law6.law.virginia.edu&quot;&gt;REFDESK@law6.law.virginia.edu&lt;/a&gt;&amp;gt;;&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Tue,&amp;nbsp; 9 Dec 2014 14:31:13 -0500 (EST)&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;Received: from iron5.mail.virginia.edu (iron5-s.mail.virginia.edu [10.250.200.115])&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; by garlic.mail.virginia.edu (Postfix) with ESMTP id 0A9132261D7&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; for &amp;lt;&lt;a mce_href=&quot;mailto:REFDESK@law6.law.virginia.edu&quot; href=&quot;mailto:REFDESK@law6.law.virginia.edu&quot;&gt;REFDESK@law6.law.virginia.edu&lt;/a&gt;&amp;gt;; Tue,&amp;nbsp; 9 Dec 2014 14:31:13 -0500 (EST)&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;X-IronPort-Anti-Spam-Filtered: true&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;X-IronPort-Anti-Spam-Result: AlAGAMFNh1QK+sjw/2dsb2JhbABWAw6CNUNSWATDeYIigx6CbwKBKxYBAQEBAX2EAgEBAQQFIAgBSxACAQUDEQQBAQYBAQECCBUHAgUQAQwCDBQJCAEBBA4EAQYCBogq0jyFFAEBAQEBAQEBAQEBAQEBAQEBAQEBARePTzwWCxAGAQkIgxCBFQWODYMKAWSFJoENgl8EjXqDLz8/MAGBRH4BAQE&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;X-IPAS-Result: AlAGAMFNh1QK+sjw/2dsb2JhbABWAw6CNUNSWATDeYIigx6CbwKBKxYBAQEBAX2EAgEBAQQFIAgBSxACAQUDEQQBAQYBAQECCBUHAgUQAQwCDBQJCAEBBA4EAQYCBogq0jyFFAEBAQEBAQEBAQEBAQEBAQEBAQEBARePTzwWCxAGAQkIgxCBFQWODYMKAWSFJoENgl8EjXqDLz8/MAGBRH4BAQE&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;X-Sender-IP: 10.250.200.240&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;Received: from iron3-s.mail.virginia.edu (HELO iron3.mail.virginia.edu) ([10.250.200.240])&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;&amp;nbsp; by iron5.mail.virginia.edu with ESMTP; 09 Dec 2014 14:31:12 -0500&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;X-IronPort-Anti-Spam-Filtered: true&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;X-IronPort-Anti-Spam-Result: AlIGAMRMh1QK+sgR/2dsb2JhbABWAw6CNUNSWATDeYIigQKCHIJvAoErFgEBAQEBAXyEAgEBAQEDBSAIAUsQAgEFAxEEAQEGAQEBAggVBwIFEAEMAgwUCQgBAQQOBAEGAgaIKtI5hRQBAQEBAQEBAQEBAQEBAQEBAQEBAQEXj088FgsQBgEJCIMQgRUFjg2DCgFkhSaBDYJfBI16gy8/PzABgUR+AQEB&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;X-IPAS-Result: AlIGAMRMh1QK+sgR/2dsb2JhbABWAw6CNUNSWATDeYIigQKCHIJvAoErFgEBAQEBAXyEAgEBAQEDBSAIAUsQAgEFAxEEAQEGAQEBAggVBwIFEAEMAgwUCQgBAQQOBAEGAgaIKtI5hRQBAQEBAQEBAQEBAQEBAQEBAQEBAQEXj088FgsQBgEJCIMQgRUFjg2DCgFkhSaBDYJfBI16gy8/PzABgUR+AQEB&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;X-IronPort-AV: E=Sophos;i=&quot;5.07,547,1413259200&quot;; &lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;d=&quot;jpg&#039;145?scan&#039;145,208,217,145&quot;;a=&quot;9153656&quot;&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;X-Sender-IP: 10.250.200.17&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;Received: from adams1-s.eservices.virginia.edu (HELO adams1.eservices.virginia.edu) ([10.250.200.17])&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;&amp;nbsp; by iron3.mail.virginia.edu with ESMTP; 09 Dec 2014 14:30:12 -0500&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;Received: from GRANT1.eservices.virginia.edu ([fe80::991f:95f0:f798:60a3]) by&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;adams1.eservices.virginia.edu ([::1]) with mapi id 14.02.0342.003; Tue, 9 Dec&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;2014 14:29:50 -0500&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;From: &quot;Wharton, Amy Ann (aaw7mh)&quot; &amp;lt;&lt;a mce_href=&quot;mailto:aaw7mh@eservices.virginia.edu&quot; href=&quot;mailto:aaw7mh@eservices.virginia.edu&quot;&gt;aaw7mh@eservices.virginia.edu&lt;/a&gt;&amp;gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;To: &quot;Monahan, John T. (jtm9p)&quot; &amp;lt;&lt;a mce_href=&quot;mailto:jtm9p@virginia.edu&quot; href=&quot;mailto:jtm9p@virginia.edu&quot;&gt;jtm9p@virginia.edu&lt;/a&gt;&amp;gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;CC: Reference Librarians &amp;lt;&lt;a mce_href=&quot;mailto:REFDESK@law6.law.virginia.edu&quot; href=&quot;mailto:REFDESK@law6.law.virginia.edu&quot;&gt;REFDESK@law6.law.virginia.edu&lt;/a&gt;&amp;gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;Subject: RE: help&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;Thread-Topic: help&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;Thread-Index: AdAT4f5jigMTC5aqQ168JlxTO8mQvgABGoDw&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;Date: Tue, 9 Dec 2014 19:29:50 +0000&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;Message-ID: &amp;lt;&lt;a mce_href=&quot;mailto:6D6C0A77EEBB3D44AE7C772B41B88C569B89B77D@grant1.eservices.virginia.edu&quot; href=&quot;mailto:6D6C0A77EEBB3D44AE7C772B41B88C569B89B77D@grant1.eservices.virginia.edu&quot;&gt;6D6C0A77EEBB3D44AE7C772B41B88C569B89B77D@grant1.eservices.virginia.edu&lt;/a&gt;&amp;gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;References: &amp;lt;&lt;a mce_href=&quot;mailto:332800578.3008.1418133488@law6.law.virginia.edu&quot; href=&quot;mailto:332800578.3008.1418133488@law6.law.virginia.edu&quot;&gt;332800578.3008.1418133488@law6.law.virginia.edu&lt;/a&gt;&amp;gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;In-Reply-To: &amp;lt;&lt;a mce_href=&quot;mailto:332800578.3008.1418133488@law6.law.virginia.edu&quot; href=&quot;mailto:332800578.3008.1418133488@law6.law.virginia.edu&quot;&gt;332800578.3008.1418133488@law6.law.virginia.edu&lt;/a&gt;&amp;gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;Accept-Language: en-US&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;Content-Language: en-US&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;X-MS-Has-Attach: yes&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;X-MS-TNEF-Correlator:&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;x-originating-ip: [137.54.253.218]&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;Content-Type: multipart/related;&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; boundary=&quot;_004_6D6C0A77EEBB3D44AE7C772B41B88C569B89B77Dgrant1eservices_&quot;;&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; type=&quot;multipart/alternative&quot;&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;MIME-Version: 1.0&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;--_004_6D6C0A77EEBB3D44AE7C772B41B88C569B89B77Dgrant1eservices_&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;Content-Type: multipart/alternative;&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; boundary=&quot;_000_6D6C0A77EEBB3D44AE7C772B41B88C569B89B77Dgrant1eservices_&quot;&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;--_000_6D6C0A77EEBB3D44AE7C772B41B88C569B89B77Dgrant1eservices_&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;Content-Type: text/plain; charset=&quot;us-ascii&quot;&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p class=&quot;MsoNormal&quot;&gt;Content-Transfer-Encoding: quoted-printable&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt; &lt;p&gt;&lt;span style=&quot;font-size: 10pt;&quot;&gt;&amp;nbsp;&lt;/span&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;span style=&quot;font-size: 10pt;&quot;&gt;.&lt;/span&gt;&amp;nbsp;&lt;/p&gt;

No idea at what point this error was introduced, but from the provided text it looks like line folding in headers is broken at this place:

Received: from GRANT1.eservices.virginia.edu ([fe80::991f:95f0:f798:60a3]) by

adams1.eservices.virginia.edu ([::1]) with mapi id 14.02.0342.003; Tue, 9 Dec

2014 14:29:50 -0500

 

A folded line must start with one or more whitespace characters.

 

&lt;p&gt;No idea at what point this error was introduced, but from the provided text it looks like line folding in headers is broken at this place:&lt;/p&gt;&lt;blockquote&gt;&lt;p&gt;&lt;i&gt;Received: from GRANT1.eservices.virginia.edu ([fe80::991f:95f0:f798:60a3]) by&lt;/i&gt;&lt;/p&gt;&lt;p&gt;&lt;i&gt;adams1.eservices.virginia.edu ([::1]) with mapi id 14.02.0342.003; Tue, 9 Dec&lt;/i&gt;&lt;/p&gt;&lt;p&gt;&lt;i&gt;2014 14:29:50 -0500&lt;/i&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;span style=&quot;font-size: 10pt;&quot;&gt;A folded line must start with one or more whitespace characters.&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style=&quot;font-size: 10pt;&quot;&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;

Rolf,

 Thanks very much for your quick and helpful response. 

The line(s) you mention DO appear to have a whitespace (one space) after the CR/LF in the source.  It got lost when I pasted it for some reason.

 This IS different from all the other wrapped lines, which have either a tab or 2-3 spaces--should this matter?

 

I had wondered about this line because it had two oddities--it has only one space after the line wrap and it references IPv6 addresses.  Is it possible Mercury has some problem with one of these two? 

 

Thanks,

George 

&lt;p&gt;Rolf,&lt;/p&gt;&lt;p&gt;&amp;nbsp;Thanks very much for your quick and helpful response.&lt;span style=&quot;font-size: 10pt;&quot;&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;The line(s) you mention DO appear to have a whitespace (one space) after the CR/LF in the source. &amp;nbsp;It got lost when I pasted it for some reason.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;span style=&quot;font-size: 10pt;&quot;&gt;This IS different from all the other wrapped lines, which have either a tab or 2-3 spaces--should this matter?&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;I had wondered about this line because it had two oddities--it has only one space after the line wrap and it references IPv6 addresses. &amp;nbsp;Is it possible Mercury has some problem with one of these two?&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Thanks,&lt;/p&gt;&lt;p&gt;George&amp;nbsp;&lt;/p&gt;

One whitespace character is enough, but it seems odd that those space characters disappeared in copying if the rest of the text is intact. Could you check if they are regular space characters (chr 32)? As long as line folding is correct Mercury wouldn't have any reason to examine the contents of a Received header.

 

&lt;p&gt;One whitespace character is enough, but it seems odd that those space characters disappeared in copying if the rest of the text is intact. Could you check if they are regular space characters (chr 32)? As long as line folding is correct Mercury wouldn&#039;t have any reason to examine the contents of a Received header.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;

They are regular space characters (hex 20 in my hex editor)  I've attached the actual file (with some of the MIME version stripped out for some attempt at brevity).  I can send you the whole file if stripping out any stuff causes problems.

 Re the ipv6 stuff, I was just wondering if all the ipv6 notation (colons, brackets) could confuse Mercury about where a line was starting/ending. Grasping at straws, maybe.

&lt;p&gt;They are regular space characters (hex 20 in my hex editor) &amp;nbsp;I&#039;ve attached the actual file (with some of the MIME version stripped out for some attempt at brevity). &amp;nbsp;I can send you the whole file if stripping out any stuff causes problems.&lt;/p&gt;&lt;p&gt;&amp;nbsp;Re the ipv6 stuff, I was just wondering if all the ipv6 notation (colons, brackets) could confuse Mercury about where a line was starting/ending.&lt;span style=&quot;font-size: 10pt;&quot;&gt;&amp;nbsp;Grasping at straws, maybe.&lt;/span&gt;&lt;/p&gt;

I copied the original message (without the notification part in the beginning) as a .101 file to Mercury queue, and it was delivered without any problem. That seems to indicate either that the error message originates from some other system, or that the incoming message data in some respect was different than the data in the file.

 

&lt;p&gt;I copied the original message (without the notification part in the beginning) as a .101 file to Mercury queue, and it was delivered without any problem. That seems to indicate either that the error message originates from some other system, or that the incoming message data in some respect was different than the data in the file.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;

Thank you.  I'm a bit stumped at to how to further troubleshoot this.  When you tested it, did it deliver to a mercury list?  That's where the problems always are.

 I'm going to comb though our setup for anything (filters, etc) that's unique to us and remove it (I'm not sure if there is much) , but assuming that's not the problem, would you have suggestions on how to determine, for instance, if this originated from another system?  I'm not sure either how I'd detect if the incoming messages were different.  I have lots more problem examples if that's useful..

 Thanks,

George 

&lt;p&gt;Thank you. &amp;nbsp;I&#039;m a bit stumped at to how to further troubleshoot this. &amp;nbsp;When you tested it, did it deliver to a mercury list? &amp;nbsp;That&#039;s where the problems always are.&lt;/p&gt;&lt;p&gt;&amp;nbsp;I&#039;m going to comb though our setup for anything (filters, etc) that&#039;s unique to us and remove it (I&#039;m not sure if there is much)&lt;span style=&quot;font-size: 10pt;&quot;&gt;&amp;nbsp;, but assuming that&#039;s not the problem, would you have suggestions on how to determine, for instance, if this originated from another system? &amp;nbsp;I&#039;m not sure either how I&#039;d detect if the incoming messages were different. &amp;nbsp;I have lots more problem examples if that&#039;s useful..&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&amp;nbsp;Thanks,&lt;/p&gt;&lt;p&gt;&lt;span style=&quot;font-size: 10pt;&quot;&gt;George&amp;nbsp;&lt;/span&gt;&lt;/p&gt;

Determining whether it is your system that is generating the error report might be achieved by creating a mailing list on your Mercury/32 server and populating it with local addresses only (using the full name.domain.com address format). Mercury/32 will recognise the addresses as local and bypass your mail filtering provider. Do several mail shots to test it and see if the error reports still occur.

&lt;P&gt;Determining whether it is your system that is generating the error report&amp;nbsp;might be achieved by creating a mailing list on your Mercury/32 server and populating it with local addresses only (using the full name.domain.com address format). Mercury/32 will recognise the addresses as local and bypass your mail filtering provider. Do several mail shots to test it and see if the error reports still occur.&lt;/P&gt;

We still have this problem, I just haven't had more time to experiment with it.  It happens a few times a week and still appears to be stubbornly random.  People can resend the same message and it works fine the second time..or third time.

 If I capture a problem message, can I just capture the headers from outlook, paste them in a text file with some text under them, and stick them in the mercury QUEUE folder with a .101 extension to see if I have a repeatable problem (given that all headers are EXACTLY the same)?  I'm unclear on how this sort of test should work, and what format a proper 101 file should have.

 Incidentally,this is what the error looks like in the log.  It says there is no from field..and then it replies to the person in the from field with an error.

 

E 20150601 1056 MG000032 :REFDESK                       No from: field in message.

O 20150601 1057 MG000034 <>                             kco4f@virginia.edu   

&lt;p&gt;We still have this problem, I just haven&#039;t had more time to experiment with it. &amp;nbsp;It happens a few times a week and still appears to be stubbornly random. &amp;nbsp;People can resend the same message and it works fine the second time..or third time.&lt;/p&gt;&lt;p&gt;&amp;nbsp;If I capture a problem message, can I just capture the headers from outlook, paste them in a text file with some text under them, and stick them in the mercury QUEUE folder with a .101 extension to see if I have a repeatable problem (given that all headers are EXACTLY the same)? &amp;nbsp;I&#039;m unclear on how this sort of test should work, and what format a proper 101 file should have.&lt;/p&gt;&lt;p&gt;&amp;nbsp;Incidentally,this is what the error looks like in the log. &amp;nbsp;It says there is no from field..and then it replies to the person in the from field with an error.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;E 20150601 1056 MG000032 :REFDESK &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; No from: field in message.&lt;/p&gt;&lt;p&gt;&lt;span style=&quot;font-size: 10pt;&quot;&gt;O 20150601 1057 MG000034 &amp;lt;&amp;gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; kco4f@virginia.edu &amp;nbsp;&lt;/span&gt;&lt;span style=&quot;font-size: 10pt;&quot;&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;

There was a post on the Mercury mailing list a short while ago with a similar problem, again involving Ironport scanning headers, if that maybe is a clue.

The error notification you mention was presumably sent to the address given in the SMTP envelope (Mail From), which is known to Mercury even if the From header in the message itself isn't located. 

&lt;p&gt;There was a post on the Mercury mailing list a short while ago with a similar problem, again involving Ironport scanning headers, if that maybe is a clue.&lt;/p&gt;&lt;p&gt;The error notification you mention was presumably sent to the address given in the SMTP envelope (Mail From), which is known to Mercury even if the From header in the message itself isn&#039;t located.&lt;span style=&quot;font-size: 10pt;&quot;&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;

Could be the same Ironport problem, though the mailer that chokes on the problem [in the case of the Mercury list message you referred to, mercury was adding a blank line after the X-IronPort-AV header], in this case, is the mercury listserver when it tries to prepare to distribute the list.  I'll turn on session logging, but I'm not sure this will add anything to the puzzle.

 I've attached another example from yesterday, FWIW

If it's not obvious, <REFDESK@law6.law.virginia.edu> is a mercury mailing list. 


&lt;p&gt;Could be the same Ironport problem, though the mailer that chokes on the problem [in the case of the Mercury list message you referred to, mercury was adding a blank line after the X-IronPort-AV header], in this case, is the mercury listserver when it tries to prepare to distribute the list. &amp;nbsp;I&#039;ll turn on session logging, but I&#039;m not sure this will add anything to the puzzle.&lt;/p&gt;&lt;p&gt;&amp;nbsp;I&#039;ve attached another example from yesterday, FWIW&lt;/p&gt;&lt;p&gt;If it&#039;s not obvious,&amp;nbsp;&lt;span style=&quot;font-size: 10pt; white-space: pre-wrap;&quot;&gt;&amp;lt;REFDESK@law6.law.virginia.edu&amp;gt; is a mercury mailing list.&lt;/span&gt;&lt;span style=&quot;font-size: 10pt;&quot;&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;p&gt; &lt;/p&gt;

[quote user="ghpayne"]

Could be the same Ironport problem, though the mailer that chokes on the problem [in the case of the Mercury list message you referred to, mercury was adding a blank line after the X-IronPort-AV header], in this case, is the mercury listserver when it tries to prepare to distribute the list.  I'll turn on session logging, but I'm not sure this will add anything to the puzzle.

 I've attached another example from yesterday, FWIW

If it's not obvious, <REFDESK@law6.law.virginia.edu> is a mercury mailing list. 


[/quote]

I don't know if this is relevant but I've just been looking through the header fields of several messages I've received (internal, external and from Mercury distribution lists), and all I have is "name" <address>. I notice that yours have "name" (name) <address>. The difference being (name)

[quote user=&quot;ghpayne&quot;] &lt;P&gt;Could be the same Ironport problem, though the mailer that chokes on the problem [in the case of the Mercury list message you referred to, mercury was adding a blank line after the X-IronPort-AV header], in this case, is the mercury listserver when it tries to prepare to distribute the list. &amp;nbsp;I&#039;ll turn on session logging, but I&#039;m not sure this will add anything to the puzzle.&lt;/P&gt; &lt;P&gt;&amp;nbsp;I&#039;ve attached another example from yesterday, FWIW&lt;/P&gt; &lt;P&gt;If it&#039;s not obvious,&amp;nbsp;&lt;SPAN style=&quot;FONT-SIZE: 10pt; WHITE-SPACE: pre-wrap&quot;&gt;&amp;lt;REFDESK@law6.law.virginia.edu&amp;gt; is a mercury mailing list.&lt;/SPAN&gt;&lt;SPAN style=&quot;FONT-SIZE: 10pt&quot;&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt; &lt;P&gt; &lt;/P&gt; &lt;P&gt;[/quote]&lt;/P&gt; &lt;P&gt;I don&#039;t know if this is relevant but I&#039;ve just been looking through the header fields of several messages I&#039;ve received (internal, external and from Mercury distribution lists),&amp;nbsp;and all I have is &quot;name&quot; &amp;lt;address&amp;gt;. I notice that yours have &quot;name&quot; (name) &amp;lt;address&amp;gt;. The difference being (name)&lt;/P&gt;

Thanks, but I'm guessing this is not relevant, as all of our addresses are formatted this way (and any message will go if you resend enough), and my understanding (I am not an expert..) is that any text other than an angle bracket can live before the <>..but the RFC is not terribly clear on this, at least to my reading.

 

&lt;p&gt;Thanks, but I&#039;m guessing this is not relevant, as all of our addresses are formatted this way (and any message will go if you resend enough), and my understanding (I am not an expert..) is that any text other than an angle bracket can live before the &amp;lt;&amp;gt;..but the RFC is not terribly clear on this, at least to my reading.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;

Rolf--When you tested, did you test to a mailing list?  That seems to be an essential ingredient.  After months of having this problem, I'm now still suspicious that it is the ironport headers, as others seem to have problems with the ironport headers.  I have many examples.  I'm attaching a few more for good measure, two failures, two similar-appearing successes...

update: actually I'm only allowed to attache one in the forum.  If you want more, I have them..

&lt;p&gt;Rolf--When you tested, did you test to a mailing list? &amp;nbsp;That seems to be an essential ingredient. &amp;nbsp;After months of having this problem, I&#039;m now still suspicious that it is the ironport headers, as others seem to have problems with the ironport headers. &amp;nbsp;I have many examples. &amp;nbsp;I&#039;m attaching a few more for good measure, two failures, two similar-appearing successes...&lt;/p&gt;&lt;p&gt;update: actually I&#039;m only allowed to attache one in the forum. &amp;nbsp;If you want more, I have them..&lt;/p&gt;

The attachment looks a bit suspicious to me. What is causing so many similar Ironport headers to be added?  Almost like a loop...

The attachment looks a bit suspicious to me. What is causing so many similar Ironport headers to be added?&amp;nbsp; Almost like a loop...

I don't know quite what the ironport headers mean, but lots of them doesn't seem to be a pattern for failure for mercury.  (Maybe you get lots for a multipart mime message?, I'm not sure). Attached is message that went just fine with lots of headers.

I don&#039;t know quite what the ironport headers mean, but lots of them doesn&#039;t seem to be a pattern for failure for mercury. &amp;nbsp;(Maybe you get lots for a multipart mime message?, I&#039;m not sure). Attached is message that went just fine with lots of headers.

Do have the same problem: incoming message to a mailinglist produces this error - ironport involved.

So did some testing with that message:

  1. removed all ending whitespaces (one in X-IronPort-AV and one after return-path) -> bouncing message -> problem remains the same
  2. removed all headers by ironport -> bouncing message -> messages passes the list
  3. removed only the longest header X-IPAS-Result -> bouncing message -> message passes the list

Because the ironport protects our university, the headers are in every mail to Mercury coming from outside, but only mails to a mailinglist produce that error.

I can't see anything in the headers that could be a problem except perhaps the length of the header. It is 254 characters plus CR and LF -> 256 characters. It seems, the routines of distributing mails via mailinglists have a problem with the stringlength.

bye   Olaf

 

&lt;p&gt;Do have the same problem: incoming message to a mailinglist produces this error - ironport involved.&lt;/p&gt;&lt;p&gt;So did some testing with that message:&lt;/p&gt;&lt;ol&gt;&lt;li&gt;removed all ending whitespaces (one in X-IronPort-AV and one after return-path) -&amp;gt; bouncing message -&amp;gt; problem remains the same&lt;/li&gt;&lt;li&gt;removed all headers by ironport -&amp;gt; bouncing message -&amp;gt; messages passes the list&lt;/li&gt;&lt;li&gt;removed only the longest header X-IPAS-Result -&amp;gt; bouncing message -&amp;gt; message passes the list &lt;/li&gt;&lt;/ol&gt;&lt;p&gt;Because the ironport protects our university, the headers are in every mail to Mercury coming from outside, but only mails to a mailinglist produce that error.&lt;/p&gt;&lt;p&gt;I can&#039;t see anything in the headers that could be a problem except perhaps the length of the header. It is 254 characters plus CR and LF -&amp;gt; 256 characters. It seems, the routines of distributing mails via mailinglists have a problem with the stringlength.&lt;/p&gt;&lt;p&gt;bye &amp;nbsp; Olaf&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;

Yes!  This does seem to be the pattern!  I have 10 examples of successes and failures, and each failure has a line which, w CR/LF, is greater than or equal to 256 characters. None of successes do.

 The longest lines for me are not always the X-IPAS-Result lines,  but are sometimes the  X-IronPort-Anti-Spam-Result lines.

So, the next question is:  can anything be done about this?  Is there any reason to believe the beta will handle this better than 4.74?  I'm not really anxious to use the beta on our production mailserver unless it seems to be a possible path to a solution... 

&lt;p&gt;Yes! &amp;nbsp;This does seem to be the pattern! &amp;nbsp;I have 10 examples of successes and failures, and each failure has a line which, w CR/LF, is greater than or equal to 256 characters. None of successes do.&lt;/p&gt;&lt;p&gt;&amp;nbsp;The longest lines for me are not always the X-IPAS-Result lines, &amp;nbsp;but are sometimes the&amp;nbsp;&lt;span style=&quot;font-size: 10pt;&quot;&gt;&amp;nbsp;&lt;/span&gt;X-IronPort-Anti-Spam-Result lines.&lt;/p&gt;&lt;p&gt;So, the next question is: &amp;nbsp;can anything be done about this? &amp;nbsp;Is there any reason to believe the beta will handle this better than 4.74? &amp;nbsp;I&#039;m not really anxious to use the beta on our production mailserver unless it seems to be a possible path to a solution...&lt;span style=&quot;font-size: 10pt;&quot;&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;

I've sent this on to the beta group and David.


&lt;p&gt;I&#039;ve sent this on to the beta group and David.&lt;/p&gt;&lt;p&gt; &lt;/p&gt;
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Cancel
Delete
Pending draft ... Click to resume editing
Discard draft