From: "Will Honea" <os2-wireless_users@2rosenthals.com>
Received: from mxout4.mailhop.org ([63.208.196.168] verified)
  by 2rosenthals.com (CommuniGate Pro SMTP 5.1.3)
  with ESMTP id 767151 for os2-wireless_users@2rosenthals.com; Mon, 29 Jan 2007 16:34:01 -0500
Received: from mxin2.mailhop.org ([63.208.196.176])
	by mxout4.mailhop.org with esmtp (Exim 4.63)
	(envelope-from <whonea@whonea.net>)
	id 1HBdpc-0000DX-Dy
	for os2-wireless_users@2rosenthals.com; Mon, 29 Jan 2007 16:14:31 -0500
Received: from smtp107.biz.mail.mud.yahoo.com ([68.142.200.255])
	by mxin2.mailhop.org with smtp (Exim 4.63)
	(envelope-from <whonea@whonea.net>)
	id 1HBdpX-000IlC-6V
	for os2-wireless_users@2rosenthals.com; Mon, 29 Jan 2007 16:14:23 -0500
Received: (qmail 65760 invoked from network); 29 Jan 2007 21:14:12 -0000
Received: from unknown (HELO 192.168.100.7) (whonea@whonea.net@70.59.203.124 with login)
  by smtp107.biz.mail.mud.yahoo.com with SMTP; 29 Jan 2007 21:14:11 -0000
X-YMail-OSG: V2FAi5cVM1nMLLKZUsiRRmXlQKoLGsKvmVCniXjjcLEgpMwTDLH0AFIZirBVhWr_aLsy.RVAbQP2FuEG_k1XFb8tIUFr7_ZFmTGzT7ADIxP0M3oqNZMEpXRC2U9VGV4mz5IC1SrrntY_423Bg0ya1ytuW_YW3ADIBQA-
Date: Mon, 29 Jan 2007 14:14:07 -0700
To: "OS/2 Wireless Users Mailing List" <os2-wireless_users@2rosenthals.com>
Reply-To: "Will Honea" <whonea@whonea.net>
In-Reply-To: <list-766196@2rosenthals.com>
References: <list-766196@2rosenthals.com>
Subject: Re: [OS2Wireless]Possible sluggishness due to Verizon DSL issues
MIME-Version: 1.0
X-Mailer: The Polarbar Mailer; version=1.25d; build=2006
X-Mailer-Platform: Linux; architecture=i386; version=2.6.18.2-34-default
X-Mailer-Java-VM: Sun Microsystems Inc.; version=1.5.0_10; compiler=null
X-Mail-Handler: MailHop by DynDNS
X-Originating-IP: 68.142.200.255
X-Spam-Score: -1.0 (-)
Message-ID: <auto-000000767151@2rosenthals.com>

Something funny is going on - I've been fighting the same problem with at least
two other sites I maintain for the last week.  One turned out to be an open
SMTP forwarder on the server spewing SPAM and chewing up the bandwidth, the
other is ongoing with a different provider.

** Reply to message from "Lewis G Rosenthal"
<os2-wireless_users@2rosenthals.com> on Mon, 29 Jan 2007 12:15:58 -0500


> (N.B.: I am sending this posting to hosted mailing lists as this issue 
> may impact list messages as well. I will subscribe all hosted lists to 
> the mailusers list for future notices.)
> 
> Beginning Saturday, January 27, we started seeing some
> unusual performance issues with the primary DSL connection
> here on the network. This condition manifested itself as
> erratic bandwidth (perceived as "speed" by end users)
> while sending mail through our server, fetching mail from
> it, or connecting through IMAP or webmail. In addition,
> websites and ftp repositories hosted here were similarly
> affected.
> 
> As the condition continued into Sunday, I performed some
> standard troubleshooting which culminated in my opening a
> trouble ticket with Verizon. (According to their system
> status log, there was a ticket opened and "resolved" on
> Friday in our immediate vicinity; it is entirely possible
> that this "resolution" is the cause of our current
> trouble.) We are currently rolled over to our backup
> interface which, though reliable, is somewhat
> bandwidth-constrained. This constraint may appear to the
> end user as slow response from our servers, but should not
> result in timeout conditions as several people were
> observing with the primary interface.
> 
> As soon as Verizon has resolved the issue(s) to my
> satisfaction, I will return connectivity to the primary
> interface, and performance should return to expected
> levels.
> 
> To help alleviate any possible saturation of the available
> bandwidth here, I would kindly ask for your patience when
> checking for mail, and request that you exercise restraint
> in not immediately re-trying for mail while operations may
> already be in progress at your end of the link. Such
> repeated attempts to fetch mail serve only to further bog
> the network and make things more difficult for everyone.
> 
> My apologies for any inconvenience this may have caused,
> and for any additional delays while this trouble ticket
> remains open.
>

-- 
Will Honea <whonea@whonea.net>