From list-managers-owner@greatcircle.com Tue Jan 10 15:33:55 2006
X-Original-To: list-managers@greatcircle.com
Received: from dishpan.dreamhost.com (dishpan.dreamhost.com [205.196.218.12])
by mycroft.greatcircle.com (Postfix) with ESMTP id 123C132C337
for ; Tue, 10 Jan 2006 15:33:55 -0800 (PST)
Received: from [192.168.11.106] (ppp-71-139-7-81.dsl.snfc21.pacbell.net [71.139.7.81])
by dishpan.dreamhost.com (Postfix) with ESMTP id D93C0EE781
for ; Tue, 10 Jan 2006 15:33:53 -0800 (PST)
Message-ID: <43C44464.2090503@equinephotoart.com>
Date: Tue, 10 Jan 2006 15:33:56 -0800
From: JC Dill
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: list-managers@greatcircle.com
Subject: Increasing problems with disappearing list email
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Archive-Number: 200601/1
X-Sequence-Number: 1876
A list I'm a member (not a list manager) on has a recent problem with
some subscribers not getting list email.
The list is hosted at PSU.EDU. The list server and the server it relays
outgoing email thru are not listed on any blacklists that I can find.
But suddenly many subscribers are not receiving email sent to the list.
The subscribers are at different ISPs, some big, some small.
One subscriber's recent post TO the list has:
>> Received: by LISTS.PSU.EDU (LISTSERV-TCP/IP release 14.4) with spool id
>> 67394116 for mungedlistname@LISTS.PSU.EDU; Tue, 10 Jan 2006 11:40:02 -0500
>> Received: from mail.pshift.com (MAIL.pshift.com [63.166.217.30]) by
>> f05n16.cac.psu.edu (8.12.11/8.12.11) with ESMTP id k0AGdvkw098116 for
>> ; Tue, 10 Jan 2006 11:39:57 -0500
>> Received: from mungedusername (unverified [64.30.34.237]) by mail.pshift.com
>> (Vircom SMTPRS 4.2.425.24) with SMTP id
>> ; Tue, 10 Jan 2006 11:39:41 -0500
>> Received-SPF: softfail (mail.pshift.com: domain of transitioning
>> mungeduserid@pshift.com does not designate 64.30.34.237 as
>> permitted sender)
>> X-Modus-BlackList: mungeduserid@pshift.com=OK
I don't know that much about SPF - I was wondering if anyone else has
encountered this and if this is working correctly? Could SPF settings
be causing messages like this to be classified as spam and if so to then
result in messages from the list being classified as spam?
Thanks!
jc
From list-managers-owner@greatcircle.com Tue Jan 10 19:28:15 2006
X-Original-To: list-managers@greatcircle.com
Received: from rivendell.cc.uky.edu (rivendell.cc.uky.edu [128.163.18.60])
by mycroft.greatcircle.com (Postfix) with ESMTP id 2EEA932C1D6
for ; Tue, 10 Jan 2006 19:28:13 -0800 (PST)
Received: (qmail 73188 invoked from network); 10 Jan 2006 22:28:06 -0500
Received: from 209-209-136-156.dialup.blueone.net (HELO ?209.209.136.156?) (somebody@209.209.136.156)
by rivendell.cc.uky.edu with AES256-SHA encrypted SMTP; 10 Jan 2006 22:28:06 -0500
Mime-Version: 1.0
Message-Id:
In-Reply-To: <43C44464.2090503@equinephotoart.com>
References: <43C44464.2090503@equinephotoart.com>
Date: Tue, 10 Jan 2006 22:27:41 -0500
To: list-managers@greatcircle.com
From: Matt Simpson
Subject: Re: Increasing problems with disappearing list email
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Archive-Number: 200601/2
X-Sequence-Number: 1877
At 3:33 PM 1/10/06, JC Dill wrote:
>>>Received: from mail.pshift.com (MAIL.pshift.com [63.166.217.30]) by
>>> f05n16.cac.psu.edu (8.12.11/8.12.11) with ESMTP id
>>>k0AGdvkw098116 for
>>> ; Tue, 10 Jan 2006 11:39:57 -0500
>>>Received: from mungedusername (unverified [64.30.34.237]) by mail.pshift.com
>>> (Vircom SMTPRS 4.2.425.24) with SMTP id
>>> ; Tue, 10 Jan 2006 11:39:41 -0500
>>>Received-SPF: softfail (mail.pshift.com: domain of transitioning
>>> mungeduserid@pshift.com does not designate 64.30.34.237 as
>>> permitted sender)
>>>X-Modus-BlackList: mungeduserid@pshift.com=OK
>
>I don't know that much about SPF - I was wondering if anyone else has
>encountered this and if this is working correctly?
No, this is not working correctly. The folks at pshift.com are
morons. The SPF check, done by their own server, on mail received
from their client, is failing.
Their published SPF record is
v=spf1 mx ip4:63.166.217.0/24 ip4:198.68.168.0/24 ip4:216.57.116.64 ~all
That tells the world that mail claiming to be from pshift.com should
be delivered by a server in one of those IP ranges. And in this
case, the mail delivered to psu.edu from pshit's server at
63.166.217.30 would pass an SPF check, if psu bothered to check it,
since it's in the 63.166.217.0/24 range. But the check isn't being
done by psu. It's being done by pshit's server when it receives the
mail from the client. They shouldn't be SPF-checking within their
own network.
>Could SPF settings
>be causing messages like this to be classified as spam and if so to then
>result in messages from the list being classified as spam?
It shouldn't. The SPF failure didn't occur on a message FROM the
list. It was on a message from the individual subscriber TO the
list. When mail is received FROM the list, if the receiving server
does SPF checking, they should check the sending server's IP address
(which would presumably be somewhere at psu.edu) against any
published SPF information for lists.psu.edu. And, since psu.edu
doesn't publish any SPF information, no server in the world should
SPF-fail any of their mail.
However, based on this, and from the message posted from the
subscriber about her discussion with pshit's chief of IT, it's
obvious that they shouldn't be in the ISP business. There's no
telling what other moronic stuff they might be doing with the mail
when it gets back to them.