2007-12-23 19:31:13

by Gene Heskett

[permalink] [raw]
Subject: More verizon problems

Resend, with more odd data from fetchmail.log appended.

Just for a heads up, for about the last 8 hours, verizon, my ISP, has been
inserting themselves into the path between my gmail account and my local
fetchmail of this email subcription at pop.gmail.com.

Worse yet they are bouncing the messages in a way that makes it look as if I
sent them when they in fact originated at vger.kernel.org. Somehow they have
convinced themselves that any mailing list this busy must be spam and is to be
bounced. Either that or they, verizon, since they sleep with M$, have taken a
large under the table payment to screw with linux in any way they can. It
bears investigating.

I called just now and screamed bloody murder at tech support, and in about 15
minutes I started getting the list again, BUT they are still in the path
between vger and my fetchmail daemon as shown below.

Or at least that is how I am interpreting the incoming headers, which now look
like this by the time they hit my inbox but with my SA headers clipped:
-----------------------
Received: from incoming.verizon.net [206.46.232.10]
by coyote.coyote.den with POP3 (fetchmail-6.3.6)
for <gene@localhost> (single-drop); Thu, 20 Dec 2007 21:10:08 -0500
(EST)
Received: from mailbag1.bizmailsrvcs.net ([172.18.12.131])
by vms051.mailsrvcs.net
(Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006))
with ESMTP id <[email protected]> for
[email protected]; Thu, 20 Dec 2007 20:08:11 -0600 (CST)
Received: from [64.233.162.238] (port=3333 helo=nz-out-0506.google.com)
by mailbag1.bizmailsrvcs.net with esmtp (Exim 4.68)
(envelope-from <[email protected]>)
id 1J5XG9-00052G-Du for [email protected]; Thu,
20 Dec 2007 20:05:09 -0600
Received: by nz-out-0506.google.com with SMTP id x7so90741nzc.3 for
<[email protected]>; Thu, 20 Dec 2007 18:08:08 -0800 (PST)
Received: by 10.142.132.2 with SMTP id f2mr436687wfd.221.1198202887677; Thu,
20 Dec 2007 18:08:07 -0800 (PST)
Received: by 10.142.222.3 with SMTP id u3cs177296wfg; Thu,
20 Dec 2007 18:08:07 -0800 (PST)
Received: by 10.100.202.9 with SMTP id z9mr1420295anf.42.1198202883749; Thu,
20 Dec 2007 18:08:03 -0800 (PST)
Received: from vger.kernel.org (vger.kernel.org [209.132.176.167])
by mx.google.com with ESMTP id q26si917844ele.6.2007.12.20.18.07.38; Thu,
20 Dec 2007 18:08:03 -0800 (PST)
Received: ([email protected]) by vger.kernel.org via listexpand id
S1759056AbXLUCHP (ORCPT <rfc822;[email protected]> + 49 others); Thu,
20 Dec 2007 21:07:15 -0500
Received: ([email protected]) by vger.kernel.org id S1754373AbXLUB7V
(ORCPT <rfc822;linux-kernel-outgoing>); Thu, 20 Dec 2007 20:59:21 -0500
Received: from smtp.polymtl.ca
([132.207.4.11]:53375 "EHLO smtp.polymtl.ca" rhost-flags-OK-OK-OK-OK)
by vger.kernel.org with ESMTP id S1761264AbXLUB7M
(ORCPT <rfc822;[email protected]>); Thu, 20 Dec 2007
20:59:12 -0500
Received: from dijkstra.casi.polymtl.ca
(dijkstra.casi.polymtl.ca [132.207.72.10]) by smtp.polymtl.ca
(8.13.8/8.13.8)
with ESMTP id lBL1vVHB024689
(version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Thu,
20 Dec 2007 20:57:32 -0500
Received: from compudj by dijkstra.casi.polymtl.ca with local (Exim 4.63)
(envelope-from <[email protected]>) id 1J5X8g-00040X-Gt; Thu,
20 Dec 2007 20:57:26 -0500
Date: Thu, 20 Dec 2007 20:54:50 -0500
From: Mathieu Desnoyers <[email protected]>
Subject: [patch 12/24] Immediate Values - Architecture Independent Code
X-Originating-IP: [172.18.12.131]
Sender: [email protected]
To: [email protected],
Ingo Molnar <[email protected]>,
[email protected]
Cc: Mathieu Desnoyers <[email protected]>,
Rusty Russell <[email protected]>
Message-id: <[email protected]>
X-Forwarded-for: [email protected] [email protected]
Content-disposition: inline;
filename=immediate-values-architecture-independent-code.patch
Precedence: bulk
Delivered-to: [email protected]
Received-SPF: pass (google.com: best guess record for domain of
[email protected] designates 209.132.176.167 as permitted
sender) client-ip=209.132.176.167;
Authentication-Results: mx.google.com; spf=pass (google.com: best guess
record
for domain of [email protected] designates 209.132.176.167
as
permitted sender) [email protected]
X-Forwarded-To: [email protected]
X-Poly-FromMTA: (dijkstra.casi.polymtl.ca [132.207.72.10]) at Fri,
21 Dec 2007 01:57:31 +0000
References: <[email protected]>
X-Mailing-List: [email protected]
List-Id: <linux-kernel.vger.kernel.org>
User-Agent: quilt/0.46-1
X-procmail: user=gene
Status: RO
X-Status: UC
X-KMail-EncryptionState:
X-KMail-SignatureState:
X-KMail-MDN-Sent:

Any mail experts here want to debunk my findings, jump right in, I'm not an
email guru, but it sure looks to me as if they are rerouting ANY port 25
access through their servers now. And M$ would pay millions to screw us,
and has, its a matter of record.

PS: From my fetchmail.log since I turned on the -v -v options an hour ago:
--------------
fetchmail: 6.3.6 querying pop.gmail.com (protocol POP3) at Sun 23 Dec 2007
02:20:56 PM EST: poll started
fetchmail: Trying to connect to 209.85.133.109/995...connected.
fetchmail: Issuer Organization: Equifax
fetchmail: Unknown Issuer CommonName
fetchmail: Server CommonName: pop.gmail.com
fetchmail: pop.gmail.com key fingerprint:
44:A8:E9:2C:FB:A9:7E:6D:F9:DB:F3:62:B2:9E:F1:A9
fetchmail: POP3< +OK Gpop ready for requests from 72.65.67.83
b11pf2510187ana.0
fetchmail: POP3> CAPA
fetchmail: POP3< +OK Capability list follows
fetchmail: POP3< USER
fetchmail: POP3< RESP-CODES
fetchmail: POP3< EXPIRE 0
fetchmail: POP3< LOGIN-DELAY 300
fetchmail: POP3< X-GOOGLE-VERHOEVEN
fetchmail: POP3< UIDL
fetchmail: POP3< .
fetchmail: POP3> USER gene.heskett
fetchmail: POP3< +OK send PASS
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Welcome.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for gene.heskett at pop.gmail.com
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Farewell.
fetchmail: 6.3.6 querying pop.gmail.com (protocol POP3) at Sun 23 Dec 2007
02:20:57 PM EST: poll completed
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
-----------

about 30 of those, there is never any mail for me at gmail.

Has my subscription info gotten contaminated somehow?

sorry for the noise folks, but this is a classic case of me and road rage.

--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Lo! Men have become the tool of their tools.
-- Henry David Thoreau


2007-12-23 20:13:16

by Matti Aarnio

[permalink] [raw]
Subject: Re: More verizon problems

On Sun, Dec 23, 2007 at 02:30:50PM -0500, Gene Heskett wrote:
> Date: Sun, 23 Dec 2007 14:30:50 -0500
> From: Gene Heskett <[email protected]>
> Subject: More verizon problems
> To: [email protected]
> Content-type: text/plain; charset=iso-8859-1
>
> Resend, with more odd data from fetchmail.log appended.

Looking at that log..


> PS: From my fetchmail.log since I turned on the -v -v options an hour ago:
> --------------
> fetchmail: 6.3.6 querying pop.gmail.com (protocol POP3) at Sun 23 Dec 2007
> 02:20:56 PM EST: poll started
> fetchmail: Trying to connect to 209.85.133.109/995...connected.
> fetchmail: Issuer Organization: Equifax
> fetchmail: Unknown Issuer CommonName
> fetchmail: Server CommonName: pop.gmail.com
> fetchmail: pop.gmail.com key fingerprint: 44:A8:E9:2C:FB:A9:7E:6D:F9:DB:F3:62:B2:9E:F1:A9

This looks like correct and genuine gmail service.

> fetchmail: POP3< +OK Gpop ready for requests from 72.65.67.83 b11pf2510187ana.0
> fetchmail: POP3> CAPA
> fetchmail: POP3< +OK Capability list follows
> fetchmail: POP3< USER
> fetchmail: POP3< RESP-CODES
> fetchmail: POP3< EXPIRE 0
> fetchmail: POP3< LOGIN-DELAY 300
> fetchmail: POP3< X-GOOGLE-VERHOEVEN
> fetchmail: POP3< UIDL
> fetchmail: POP3< .
> fetchmail: POP3> USER gene.heskett
> fetchmail: POP3< +OK send PASS
> fetchmail: POP3> PASS *
> fetchmail: POP3< +OK Welcome.
> fetchmail: selecting or re-polling default folder
> fetchmail: POP3> STAT
> fetchmail: POP3< +OK 0 0
> fetchmail: No mail for gene.heskett at pop.gmail.com
> fetchmail: POP3> QUIT
> fetchmail: POP3< +OK Farewell.
> fetchmail: 6.3.6 querying pop.gmail.com (protocol POP3) at Sun 23 Dec 2007 02:20:57 PM EST: poll completed
> fetchmail: not swapping UID lists, no UIDs seen this query
> fetchmail: Query status=1 (NOMAIL)
> -----------
>
> about 30 of those, there is never any mail for me at gmail.
>
> Has my subscription info gotten contaminated somehow?

re-forward at gmail to verizon ?

> sorry for the noise folks, but this is a classic case of me and road rage.

I try to avoid that. Gives others an illusion of me being smarter
than I am in reality... :-)

> --
> Cheers, Gene

/Matti Aarnio

2007-12-27 03:24:55

by Bill Davidsen

[permalink] [raw]
Subject: Re: More verizon problems

Gene Heskett wrote:
> Resend, with more odd data from fetchmail.log appended.
>
> Just for a heads up, for about the last 8 hours, verizon, my ISP, has been
> inserting themselves into the path between my gmail account and my local
> fetchmail of this email subcription at pop.gmail.com.
>
> Worse yet they are bouncing the messages in a way that makes it look as if I
> sent them when they in fact originated at vger.kernel.org. Somehow they have
> convinced themselves that any mailing list this busy must be spam and is to be
> bounced. Either that or they, verizon, since they sleep with M$, have taken a
> large under the table payment to screw with linux in any way they can. It
> bears investigating.
>
> I called just now and screamed bloody murder at tech support, and in about 15
> minutes I started getting the list again, BUT they are still in the path
> between vger and my fetchmail daemon as shown below.
>
> Or at least that is how I am interpreting the incoming headers, which now look
> like this by the time they hit my inbox but with my SA headers clipped:
> -----------------------
> Received: from incoming.verizon.net [206.46.232.10]
> by coyote.coyote.den with POP3 (fetchmail-6.3.6)
> for <gene@localhost> (single-drop); Thu, 20 Dec 2007 21:10:08 -0500
> (EST)
> Received: from mailbag1.bizmailsrvcs.net ([172.18.12.131])
> by vms051.mailsrvcs.net
> (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006))
> with ESMTP id <[email protected]> for
> [email protected]; Thu, 20 Dec 2007 20:08:11 -0600 (CST)
> Received: from [64.233.162.238] (port=3333 helo=nz-out-0506.google.com)
> by mailbag1.bizmailsrvcs.net with esmtp (Exim 4.68)
> (envelope-from <[email protected]>)
> id 1J5XG9-00052G-Du for [email protected]; Thu,
> 20 Dec 2007 20:05:09 -0600

Right here I see that google forwarded your mail from their (google)
server sending to the bizmailsrvcs.net (verizon) server, and VZ didn't
jump in the path, google put them there.

> Received: by nz-out-0506.google.com with SMTP id x7so90741nzc.3 for
> <[email protected]>; Thu, 20 Dec 2007 18:08:08 -0800 (PST)

Most likely cause is that you forwarded mail from google to verizon,
which is probably a bad thing on many levels.

Not Verizon's fault.

--
Bill Davidsen <[email protected]>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot