Getting caught by SPAM Filters because of Mailman handoff
Companies are now starting to block Mailman lists (among others) because of the way the headers are sent out stating the hand-off to the server:
Received: from localhost.localdomain ([127.0.0.1] helo=mail.python.org) by mail.python.org with esmtp (Exim 4.22) id 1BH7Kx-0001vz-7S; Fri, 23 Apr 2004 16:31:51 -0400
Anything with that format - they are marking as "probable SPAM"
Any thoughts on how to zap?
Also, as I mine is an announce only list - it would be nice to be able to zap the other received from headers and show the message as coming directly from the server. One webmail program does it - but it cannot send HTML.
Received: from localhost.localdomain ([127.0.0.1] helo=mail.python.org) by mail.python.org with esmtp (Exim 4.22) id 1BH7Kx-0001vz-7S; Fri, 23 Apr 2004 16:31:51 -0400 Received: from mydomain.com ([111.111.11.111]) by mail.python.org with esmtp (Exim 4.22) id 1BH7Ko-0001tP-Ph for mailman-users@python.org; Fri, 23 Apr 2004 16:31:42 -0400
BTW - usim exim as MTA.
Thanks.
Lloyd F. Tennison lloyd_tennison@whoever.com
No trees were harmed in the transmission of this message. However, a rather large number of electrons were temporarily inconvenienced.
On 24 Apr 2004, at 02:10, Lloyd F. Tennison wrote:
Companies are now starting to block Mailman lists (among others) because of the way the headers are sent out stating the hand-off to the server:
Received: from localhost.localdomain ([127.0.0.1] helo=mail.python.org) by mail.python.org with esmtp (Exim 4.22) id 1BH7Kx-0001vz-7S; Fri, 23 Apr 2004 16:31:51 -0400
Anything with that format - they are marking as "probable SPAM"
Any thoughts on how to zap?
Although I run the outgoing MTA and Mailman on the same machine, my Mailman SMTP configuration tells it not to address the MTA using localhost (127.0.0.1) but by the FQDN and IP number which appears in our globally published MX record for that server. Thus the Received: header added by the outbound MTA at this juncture refers to reception form a host (itself) which is resolvable via DNS to an MX record by MTAs which subsequently handle the message. In that respect, it is thus fairly indistinguishable from other Received: headers that precede and follow it.
Would this be avoid triggering the approach in anti-spam measures you refer to?
Also, as I mine is an announce only list - it would be nice to be able to zap the other received from headers and show the message as coming directly from the server. One webmail program does it - but it cannot send HTML.
Received: from localhost.localdomain ([127.0.0.1] helo=mail.python.org) by mail.python.org with esmtp (Exim 4.22) id 1BH7Kx-0001vz-7S; Fri, 23 Apr 2004 16:31:51 -0400 Received: from mydomain.com ([111.111.11.111]) by mail.python.org with esmtp (Exim 4.22) id 1BH7Ko-0001tP-Ph for mailman-users@python.org; Fri, 23 Apr 2004 16:31:42 -0400
BTW - usim exim as MTA.
Thanks.
Lloyd F. Tennison lloyd_tennison@whoever.com
No trees were harmed in the transmission of this message. However, a rather large number of electrons were temporarily inconvenienced.
How did you change the configuration to accomplish that, please.
Copies to: mailman-users@python.org, mailman-developers@python.org From: Richard Barrett r.barrett@ftel.co.uk Subject: Re: [Mailman-Users] Getting caught by SPAM Filters because of Mailman handoff Date sent: Sat, 24 Apr 2004 18:16:55 +0100 To: lloyd_tennison@whoever.com
On 24 Apr 2004, at 02:10, Lloyd F. Tennison wrote:
Companies are now starting to block Mailman lists (among others) because of the way the headers are sent out stating the hand-off to the server:
Received: from localhost.localdomain ([127.0.0.1] helo=mail.python.org) by mail.python.org with esmtp (Exim 4.22) id 1BH7Kx-0001vz-7S; Fri, 23 Apr 2004 16:31:51 -0400
Anything with that format - they are marking as "probable SPAM"
Any thoughts on how to zap?
Although I run the outgoing MTA and Mailman on the same machine, my Mailman SMTP configuration tells it not to address the MTA using localhost (127.0.0.1) but by the FQDN and IP number which appears in our globally published MX record for that server. Thus the Received: header added by the outbound MTA at this juncture refers to reception form a host (itself) which is resolvable via DNS to an MX record by MTAs which subsequently handle the message. In that respect, it is thus fairly indistinguishable from other Received: headers that precede and follow it.
Would this be avoid triggering the approach in anti-spam measures you refer to?
Also, as I mine is an announce only list - it would be nice to be able to zap the other received from headers and show the message as coming directly from the server. One webmail program does it - but it cannot send HTML.
Received: from localhost.localdomain ([127.0.0.1] helo=mail.python.org) by mail.python.org with esmtp (Exim 4.22) id 1BH7Kx-0001vz-7S; Fri, 23 Apr 2004 16:31:51 -0400 Received: from mydomain.com ([111.111.11.111]) by mail.python.org with esmtp (Exim 4.22) id 1BH7Ko-0001tP-Ph for mailman-users@python.org; Fri, 23 Apr 2004 16:31:42 -0400
BTW - usim exim as MTA.
Thanks.
Lloyd F. Tennison lloyd_tennison@whoever.com
No trees were harmed in the transmission of this message. However, a rather large number of electrons were temporarily inconvenienced.
Thanks.
Lloyd F. Tennison lloyd_tennison@whoever.com
No trees were harmed in the transmission of this message. However, a rather large number of electrons were temporarily inconvenienced.
participants (2)
-
Lloyd F. Tennison -
Richard Barrett