The incredible disapearing post?
Greetings, all!
I have a mailing list set up for company-wide emails to which any member can post (in other words, a plain vanilla list). However, I have one user that has been attempting to post to the list but his emails are disappearing.
I can see the message hitting the server and being passed off to mailman, but I can not find anything in the mailman logs to indicate that it was ever received. His account is identical to everyone else, but he 'appears' to be the only member that has this issue. I have removed and recreated his account several times, but there has been no change.
Any ideas on where to look?
MAIL.LOG:
Jan 2 09:19:27 mail sendmail[13025]: l02EJNaC013025: from=<user@MYDOMAIN.com>, size=1791, class=0, nrcpts=1, msgid=<001801c72e79$02aa6370$163b0a0a@MYDOMAIN.com>, proto=ESMTP, daemon=MTA, relay=[10.10.57.184]
Jan 2 09:21:04 mail sendmail[13363]: l02EJNaC013025: to="|/usr/local/mailman/mail/mailman post COMPANY", ctladdr=<COMPANY@MYDOMAIN.com> (8/0), delay=00:01:37, xdelay=00:00:02, mailer=prog, pri=121791, dsn=2.0.0, stat=Sent
Here is another user sending the same post (text-wise) to the same list: MAIL.LOG:
Jan 2 11:44:05 mail sendmail[13136]: l02Gi16Y013136: from=<user@tlcdelivers.com>, size=5831, class=0, nrcpts=1, msgid=<200701021644.l02Gi16Y013136@MYDOMAIN.com>, proto=ESMTP, daemon=MTA, relay=[10.10.59.56]
Jan 2 11:45:04 mail sendmail[13368]: l02Gi16Y013136: to="|/usr/local/mailman/mail/mailman post COMPANY", ctladdr=<COMPANY@MYDOMAIN.com> (8/0), delay=00:00:59, xdelay=00:00:00, mailer=prog, pri=125831, dsn=2.0.0, stat=Sent
Jan 2 11:45:09 mail sendmail[13419]: l02Gj9dq013419: from=<COMPANY-bounces@MYDOMAIN.com>, size=6793, class=-30, nrcpts=53, msgid=<200701021644.l02Gi16Y013136@MYDOMAIN.com>, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1]
Jan 2 11:46:36 mail sendmail[13419]: l02Gj9dr013419: from=<COMPANY-bounces@MYDOMAIN.com>, size=6793, class=-30, nrcpts=149, msgid=<200701021644.l02Gi16Y013136@MYDOMAIN.com>, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1]
-- Brian
"An adventure is never an adventure when it's happening. Challenging experiences need time to ferment, and an adventure is simply physical and emotional discomfort recollected in tranquility." -- Tim Cahill
Quoting Brian Atkins (batkins@tlcdelivers.com):
Look on the admindb page to see if they're being held for some reason.
-- Paul Tomblin <ptomblin@xcski.com> http://blog.xcski.com/ If men are from Mars and women are from Venus, there's going to be one big-ass fight over where to set the thermostat. -- Jim Rosenberg
I guess I forgot to add that info to my previous post. No, it's not getting hung up in the admindb.
I was able to get one message from him to go through this afternoon by unchecking 'log on to the server before sending' in Outlook.
Hmmm... I can't imagine why that would have prevented him from sending through mailman. I decided to look there after I noticed that the message he was sending had a message ID of "@AD-DOMAIN.DOMAIN.COM" and the other user was "@mail.DOMAIN.COM".
Weird. Any idea why that would have caused an issue with Mailman?
Brian
Paul Tomblin wrote:
Quoting Brian Atkins (batkins@tlcdelivers.com):
If it's changing the Message-ID, it might be changing the From address as well. Is your mailing list set to reject mail from non-members? If so, it's possible that Outlook is changing his From to something other than what he subscribed as. Is there anything in the vette log?
-- Paul Tomblin <ptomblin@xcski.com> http://blog.xcski.com/ Quality Control, n.: The process of testing one out of every 1,000 units coming off a production line to make sure that at least one out of 100 works.
Brian Atkins sent the message below at 13:30 1/2/2007:
Based on your previous post and the fact that the e-mail addresses show have host parts as well as the TLD, you would probably want to try a revised RE like this:
^.*@DOMAIN\.com|^.*@.*\.DOMAIN\.com
This change allows any e-mail address that has a host part to pass as well as any from the TLD without a host part.
Dragon
Venimus, Saltavimus, Bibimus (et naribus canium capti sumus)
Brian Atkins sent the message below at 12:08 1/2/2007:
It appears that something is happening to either discard or shunt that user's posts prior to them being handed off to mailman's outgoing queue. The message is being handed off from the SMTP server to mailman but something is happening after that occurs.
Have you looked in mailman's vette and error logs? If the message was discarded, it should appear in the vette log. If mailman had a problem processing the message, there should be an entry in the error log.
If you have archiving enabled, is the message hitting the archive?
Is the person who is having difficulty using an MUA that is the same or different from what others use?
Are you doing any sort of content filtering or scrubbing? It could be that after scrubbing of the mail message there are no valid parts left to send.
Dragon
Venimus, Saltavimus, Bibimus (et naribus canium capti sumus)
Dragon wrote:
No log entires.
If you have archiving enabled, is the message hitting the archive?
Yes, it is enabled. No, it's not getting there.
Is the person who is having difficulty using an MUA that is the same or different from what others use?
Same. Everyone pretty much uses Outlook, 'cept those of us in the know.
No filtering is enabled.
Brian Atkins wrote:
It looks that way to me too.
It appears from the mail log that the message is delivered to the wrapper for posting to the list, and thus should get to the in queue (qfiles/in/), yet it doesn't get as far in the pipeline as ToArchive.
If it is held, it should be in the admindb interface as a held message. If it is rejected, a reject message will be sent to the poster, but this doesn't appear to be in the mail log. If it is discarded for any reason, the discard should be logged in the vette log. If something goes seriously wrong, the exception should be logged in the error log.
Is there anything in any of Mailman's queues?
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Quoting Brian Atkins (batkins@tlcdelivers.com):
Look on the admindb page to see if they're being held for some reason.
-- Paul Tomblin <ptomblin@xcski.com> http://blog.xcski.com/ If men are from Mars and women are from Venus, there's going to be one big-ass fight over where to set the thermostat. -- Jim Rosenberg
I guess I forgot to add that info to my previous post. No, it's not getting hung up in the admindb.
I was able to get one message from him to go through this afternoon by unchecking 'log on to the server before sending' in Outlook.
Hmmm... I can't imagine why that would have prevented him from sending through mailman. I decided to look there after I noticed that the message he was sending had a message ID of "@AD-DOMAIN.DOMAIN.COM" and the other user was "@mail.DOMAIN.COM".
Weird. Any idea why that would have caused an issue with Mailman?
Brian
Paul Tomblin wrote:
Quoting Brian Atkins (batkins@tlcdelivers.com):
If it's changing the Message-ID, it might be changing the From address as well. Is your mailing list set to reject mail from non-members? If so, it's possible that Outlook is changing his From to something other than what he subscribed as. Is there anything in the vette log?
-- Paul Tomblin <ptomblin@xcski.com> http://blog.xcski.com/ Quality Control, n.: The process of testing one out of every 1,000 units coming off a production line to make sure that at least one out of 100 works.
Brian Atkins sent the message below at 13:30 1/2/2007:
Based on your previous post and the fact that the e-mail addresses show have host parts as well as the TLD, you would probably want to try a revised RE like this:
^.*@DOMAIN\.com|^.*@.*\.DOMAIN\.com
This change allows any e-mail address that has a host part to pass as well as any from the TLD without a host part.
Dragon
Venimus, Saltavimus, Bibimus (et naribus canium capti sumus)
Brian Atkins sent the message below at 12:08 1/2/2007:
It appears that something is happening to either discard or shunt that user's posts prior to them being handed off to mailman's outgoing queue. The message is being handed off from the SMTP server to mailman but something is happening after that occurs.
Have you looked in mailman's vette and error logs? If the message was discarded, it should appear in the vette log. If mailman had a problem processing the message, there should be an entry in the error log.
If you have archiving enabled, is the message hitting the archive?
Is the person who is having difficulty using an MUA that is the same or different from what others use?
Are you doing any sort of content filtering or scrubbing? It could be that after scrubbing of the mail message there are no valid parts left to send.
Dragon
Venimus, Saltavimus, Bibimus (et naribus canium capti sumus)
Dragon wrote:
No log entires.
If you have archiving enabled, is the message hitting the archive?
Yes, it is enabled. No, it's not getting there.
Is the person who is having difficulty using an MUA that is the same or different from what others use?
Same. Everyone pretty much uses Outlook, 'cept those of us in the know.
No filtering is enabled.
Brian Atkins wrote:
It looks that way to me too.
It appears from the mail log that the message is delivered to the wrapper for posting to the list, and thus should get to the in queue (qfiles/in/), yet it doesn't get as far in the pipeline as ToArchive.
If it is held, it should be in the admindb interface as a held message. If it is rejected, a reject message will be sent to the poster, but this doesn't appear to be in the mail log. If it is discarded for any reason, the discard should be logged in the vette log. If something goes seriously wrong, the exception should be logged in the error log.
Is there anything in any of Mailman's queues?
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (4)
-
Brian Atkins -
Dragon -
Mark Sapiro -
Paul Tomblin