Skip to Content.
Sympa Menu

en - [sympa-users] Recent upgrade -- some messages failing with "No Message ID"

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: Aaron Bennett <address@concealed>
  • To: "address@concealed" <address@concealed>
  • Subject: [sympa-users] Recent upgrade -- some messages failing with "No Message ID"
  • Date: Wed, 21 Mar 2018 15:29:15 +0000

Hi,

 

I recently migrated from 5.4 (yes, really) to 6.2.24.  We’ve got a simple round-trip email flow monitor that’s built-in to PRTG’s Network Monitor. It drops a message off and checks an imap server to see that it got delivered.  On 5.4, the messages were coming through like this:

 

 

Return-Path: <address@concealed>

Received: from watchdog.clarku.edu (scooter.clarku.edu [140.232.1.86])

                by lists.clarku.edu (Postfix) with ESMTP id E11B162E80E

                for <address@concealed>; Wed, 21 Mar 2018 06:37:33 -0400 (EDT)

From: "address@concealed" <address@concealed>

Subject: PRTG Roundtrip Mail: {4E54A8FF-1668-4BA6-80D3-B2EC85EDE1A8}

To: address@concealed

Date: Wed, 21 Mar 2018 06:37:34 -0400

Message-Id: <address@concealed>

 

This is an email created by PRTG for SMTP/POP3 Roundtrip Testing (18.1.36.3728)

Timestamp: 3/21/2018 6:37:34 AM

 

It’s a very, very simple monitor.  However, on 6.2.24, every one generates “Mar 21 11:28:13 oatmeal sympa_msg[13463]: err main::#243 > Sympa::Spindle::spin#83 > Sympa::Spindle::ProcessIncoming::_twist#108 Message Sympa::Message <address@concealed> has no message ID”

 

And never gets queued.  Does anyone have a guess as to why?

 

Thanks for your time,

 

Aaron

 

---

Aaron Bennett

Manager of Systems Administration

Clark University ITS

 




Archive powered by MHonArc 2.6.19+.

Top of Page