Hi!
I have configured a mail server with Sendmail on my office and mails are sent fine.
I'm using MailMan to send a newsletter to a test list of five people, one from hotmail, one from gmail, one from yahoo and two from my ISP (including my address).
The newsletter is sent fine to all of the recipients (I've checked sendmail queue) but for some reason my ISP is discarding the message for their addresses (hotmail, gmail and yahoo are working fine).
I suspect the problem is related to the headers sent by MailMan because when I send the newsletter directly from my mail client trough my office server, it is received without problems (the only difference between the one sent by MailMan and the one sent by my mail client is the headers).
Is there some special header sent by MailMan that is well known as some kind of SPAM header?
Thanks in advance!
Greetings,
Antonio
On 5/20/06 4:46 PM, "Antonio Dragone" dragone_se@hotmail.com wrote:
Hi!
I have configured a mail server with Sendmail on my office and mails are sent fine.
I'm using MailMan to send a newsletter to a test list of five people, one from hotmail, one from gmail, one from yahoo and two from my ISP (including my address).
The newsletter is sent fine to all of the recipients (I've checked sendmail queue) but for some reason my ISP is discarding the message for their addresses (hotmail, gmail and yahoo are working fine).
I suspect the problem is related to the headers sent by MailMan because when I send the newsletter directly from my mail client trough my office server, it is received without problems (the only difference between the one sent by MailMan and the one sent by my mail client is the headers).
Is there some special header sent by MailMan that is well known as some kind of SPAM header?
The obvious one is Precedence: list
But that's a silly thing to filter on, and it is correct for Mailman to insert it.
They might not like From: <your address with them> coming with the envelope sender.
Or they might be running a silly challenge-response system
All of those would essentially mean that one can't receive messages from mailing lists at that ISP (or that you have to configure something related to your account to allow it).
Anyone else?
--John
John W. Baxter wrote:
On 5/20/06 4:46 PM, "Antonio Dragone" dragone_se@hotmail.com wrote:
Hi!
I have configured a mail server with Sendmail on my office and mails are sent fine.
I'm using MailMan to send a newsletter to a test list of five people, one from hotmail, one from gmail, one from yahoo and two from my ISP (including my address).
Presumably, Mailman is sending via the same Sendmail server.
The newsletter is sent fine to all of the recipients (I've checked sendmail queue) but for some reason my ISP is discarding the message for their addresses (hotmail, gmail and yahoo are working fine).
I suspect the problem is related to the headers sent by MailMan because when I send the newsletter directly from my mail client trough my office server, it is received without problems (the only difference between the one sent by MailMan and the one sent by my mail client is the headers).
And the envelope.
They might not like From: <your address with them> coming with the envelope sender.
I just want to emphasize this. When you send via your mail client, the message is From: you and the envelope is most likely from you, but when you post to your list and Mailman sends, the message is still From: you (assuming you don't have an anonymous list), but the envelope is from <listname>-bounces@list.domain.
Your ISP may well decide that a message purportedly from you@your.isp sent by some other domain is forged.
-- Mark Sapiro msapiro@value.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thus spake Mark Sapiro msapiro@value.net, circa 5/20/2006 9:26 PM:
I just want to emphasize this. When you send via your mail client, the message is From: you and the envelope is most likely from you, but when you post to your list and Mailman sends, the message is still From: you (assuming you don't have an anonymous list), but the envelope is from <listname>-bounces@list.domain. Your ISP may well decide that a message purportedly from you@your.isp sent by some other domain is forged.
This is certainly possible, but I want to emphasize this: if the ISP is doing this they are 100% WRONG!
RFC 2821 specifies that the envelope header "From" can -- and in some cases MUST -- differ from the "From" in the message itself. There are a variety of headers, such as From, Resent-From, Errors-To, and there are legitimate reasons for all of them to be different.
If you find an ISP that is blocking mail from your list due to the makeup of the envelope headers, you should encourage them to read the relevant mail transport RFCs and invest in some decent Bayesian spam filtering software. Then encourage your subscribers at that ISP to find another ISP
-- Peter C.S. Adams (617) 287-7118 Director of Information and Communication Technologies College of Public and Community Service, UMass Boston "Be civil to all; sociable to many; familiar with few; friend to one; enemy to none." -- Benjamin Franklin, Poor Richard's Almanack
participants (4)
-
Antonio Dragone -
John W. Baxter -
Mark Sapiro -
Peter C.S. Adams