All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gene Heskett <gene.heskett@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: More verizon problems
Date: Sun, 23 Dec 2007 14:30:50 -0500	[thread overview]
Message-ID: <200712231430.50493.gene.heskett@gmail.com> (raw)

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 <0JTD00L5XN9KBGD0@vms051.mailsrvcs.net> for
 gene.heskett@verizon.net; 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 <gene.heskett+caf_=gene.heskett=verizononline.net@gmail.com>)
 id 1J5XG9-00052G-Du    for gene.heskett@verizononline.net; Thu,
 20 Dec 2007 20:05:09 -0600
 Received: by nz-out-0506.google.com with SMTP id x7so90741nzc.3 for
 <gene.heskett@verizononline.net>; 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: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand   id
 S1759056AbXLUCHP (ORCPT <rfc822;wyh817@gmail.com> + 49 others); Thu,
 20 Dec 2007 21:07:15 -0500
 Received: (majordomo@vger.kernel.org) 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;linux-kernel@vger.kernel.org>); 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 <mathieu.desnoyers@polymtl.ca>) id 1J5X8g-00040X-Gt; Thu,
 20 Dec 2007 20:57:26 -0500
 Date: Thu, 20 Dec 2007 20:54:50 -0500
 From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
 Subject: [patch 12/24] Immediate Values - Architecture Independent Code
 X-Originating-IP: [172.18.12.131]
 Sender: linux-kernel-owner@vger.kernel.org
 To: akpm@linux-foundation.org,
 Ingo Molnar <mingo@elte.hu>,
 linux-kernel@vger.kernel.org
 Cc: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
 Rusty Russell <rusty@rustcorp.com.au>
 Message-id: <20071221015726.253261266@polymtl.ca>
 X-Forwarded-for: gene.heskett@gmail.com gene.heskett@verizononline.net
 Content-disposition: inline;
 filename=immediate-values-architecture-independent-code.patch
 Precedence: bulk
 Delivered-to: gene.heskett@gmail.com
 Received-SPF: pass (google.com: best guess record for domain of
 linux-kernel-owner@vger.kernel.org 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 linux-kernel-owner@vger.kernel.org designates 209.132.176.167 
as
 permitted sender) smtp.mail=linux-kernel-owner@vger.kernel.org
 X-Forwarded-To: gene.heskett@verizononline.net
 X-Poly-FromMTA: (dijkstra.casi.polymtl.ca [132.207.72.10]) at Fri,
 21 Dec 2007 01:57:31 +0000
 References: <20071221015438.433195466@polymtl.ca>
 X-Mailing-List: linux-kernel@vger.kernel.org
 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

             reply	other threads:[~2007-12-23 19:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-23 19:30 Gene Heskett [this message]
2007-12-23 20:13 ` More verizon problems Matti Aarnio
2007-12-27  3:45 ` Bill Davidsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200712231430.50493.gene.heskett@gmail.com \
    --to=gene.heskett@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.