Yes, you are right - it was a remote problem. I was put off the scent
because all three mail servers I was sending to silently rejected the
email. I added an email with from a 4th different server and it succeeded.
Even though the problem occured 'outside' of my server, I'm sure a solution
can be found within it.
Here are the headers from the email that got through. Do they give you any
clues as to why it was rejected by the others?
Return-Path: <[EMAIL PROTECTED]>
Delivery-Date: Thu, 11 May 2006 17:35:12 +0200
Received-SPF: none (mxeu1: 212.158.231.226 is neither permitted nor denied
by domain of list.vawcvs.org) client-ip=212.158.231.226; envelope-from=
[EMAIL PROTECTED]; helo=list.vawcvs.org;
Received: from [212.158.231.226] (helo=list.vawcvs.org)
by mx.kundenserver.de (node=mxeu1) with ESMTP (Nemesis),
id 0MKpV6-1FeDC41ASD-00016j for [EMAIL PROTECTED]; Thu, 11 May
2006 17:35:12 +0200
Received: from list.vawcvs.org (list.vawcvs.org [127.0.0.1])
by list.vawcvs.org (Postfix) with ESMTP id EFA08BD8197;
Thu, 11 May 2006 16:35:06 +0100 (BST)
X-Original-To: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
Received: from nz-out-0102.google.com (nz-out-0102.google.com [
64.233.162.199])
by list.vawcvs.org (Postfix) with ESMTP id C4673BD8197
for <[EMAIL PROTECTED]>; Thu, 11 May 2006 16:35:05 +0100 (BST)
Received: by nz-out-0102.google.com with SMTP id 18so250453nzp
for <[EMAIL PROTECTED]>; Thu, 11 May 2006 08:35:05 -0700 (PDT)
Received: by 10.36.247.53 with SMTP id u53mr978874nzh;
Thu, 11 May 2006 08:35:05 -0700 (PDT)
Received: by 10.36.104.3 with HTTP; Thu, 11 May 2006 08:35:04 -0700 (PDT)
Message-ID: <[EMAIL PROTECTED]>
Date: Thu, 11 May 2006 16:35:04 +0100
From: "Michael McAndrew" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
MIME-Version: 1.0
Subject: [VAW staff] Please email [EMAIL PROTECTED] if you receive
this message.
X-BeenThere: [EMAIL PROTECTED]
X-Mailman-Version: 2.1.7
Precedence: list
List-Id: <vaw-staff.list.vawcvs.org>
List-Unsubscribe: <http://list.vawcvs.org/mailman/listinfo/vaw-staff>,
<mailto:[EMAIL PROTECTED]>
List-Archive: <http://list.vawcvs.org/pipermail/vaw-staff>
List-Post: <mailto:[EMAIL PROTECTED]>
List-Help: <mailto:[EMAIL PROTECTED]>
List-Subscribe: <http://list.vawcvs.org/mailman/listinfo/vaw-staff>,
<mailto:[EMAIL PROTECTED]>
Content-Type: multipart/mixed; boundary="===============1733620005=="
Sender: [EMAIL PROTECTED]
Errors-To: [EMAIL PROTECTED]
Envelope-To: [EMAIL PROTECTED]
X-NAS-Classification: 0
X-NAS-MessageID: 8
X-NAS-Validation: {A2AF7F64-406D-45BA-AC23-F071B8419E46}
And in case it's of any use, the servers that failed are gmail's mail
server, and one operating on Microsoft ESMTP MAIL Service, Version:
6.0.3790.1830. And the one that succeeded was called "(mxeu14) Welcome to
Nemesis ESMTP server."
Many thanks again,
Michael
On 5/11/06, Mark Sapiro < [EMAIL PROTECTED]> wrote:
>
> Michael McAndrew wrote:
> >
> >But, when an email is posted
> >to a list, it is not received by recipients. It is placed in the Mailman
> >archive, though, and there are no obvious signs of trouble in the logs
> I've
> >looked in.
> >
> >Everything seems normal in mailman's SMTP log:
> >May 11 13:11:40 2006 (2237) <
> >[EMAIL PROTECTED] > smtp to michael for 1
> >recips, completed in 0.038 seconds
>
>
> This says it was successfully delivered to Postfix.
>
>
> >And as far as I can tell, Postfix hasn't had any problems either (from
> >Postfix's maillog):
> >May 11 13:11:42 list postfix/smtp[10675]: 33504BD81B5: to=<
> >[EMAIL PROTECTED]>, relay=gmail-smtp-in.l.google.com[64.233.183.27
> ],
> >delay=2, status=sent (250 2.0.0 OK 1147349502 c28si796656nfb)
> >May 11 13:11:42 list postfix/qmgr[10493]: 33504BD81B5: removed
>
>
> And Postfix is saying it sent the mail to gmail-smtp-in.l.google.com
> for [EMAIL PROTECTED] and received confirmation (250 2.0.0 OK
> 1147349502 c28si796656nfb) from that server.
>
>
> >But still, the email doesn't reach the recipients. I'm pretty sure it
> isn't
> >a problem with communication between the server and the destination email
>
> >account, as I can successfully send them an email using telnet to access
> >Postfix on the mailing list server.
> >
> >The mailing list used in the example above was created with bin/newlist
> >command, with no extra configuration. I have a number of other lists set
>
> >up, but the problem is repeated with all of them. I would put it down
> to a
> >problem outside mailman, but the thing is that the mailman admin emails
> get
> >through.
>
>
> It definitely seems to be outside of Mailman and even your local
> Postfix. Since it only affects posts, it seems it must have something
> to do specifically with the sender, headers or body of the post itself.
>
> One thing that may be different is the envelope sender if you are using
> Mailman virtual hosts. In this case, (un-VERPed) list mail will have
> an envelope sender of [EMAIL PROTECTED] , but some
> administrative messages may be sent by
> [EMAIL PROTECTED] See
> <http://mail.python.org/pipermail/mailman-users/2006-April/050706.html >
> which is not exactly relevant to your situation, but may be
> interesting.
>
> --
> Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
> San Francisco Bay Area, California better use your sense - B. Dylan
>
>
------------------------------------------------------
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
