Hey people: tried to reach out to Verizon, and they basically told me to piss off. So if you have a Verizon email account (and probably reading this from the archives), please contact Verizon and ask them to reconsider.
Begin forwarded message:
From: whitelist@verizononline.net Subject: RE: Whitelist Request for IP Address 104.236.203.188 Date: January 14, 2016 at 8:00:54 AM CST To: ed@leafe.com
After investigation, Verizon Online Security has determined that e-mail from your IP address will not be allowed access to the Verizon Online e-mail domain due to one or more of the following reasons:
Your IP has been blocked because of spam issues or because your ISP indicates that it is dynamically assigned
Once you have addressed any security-related issues on your network, you should contact Verizon Online Security via this form. At that time, we will work with you to restore normal e-mail traffic or to take other action as we deem appropriate.
Sincerely,
Verizon Online Security http://www2.verizon.net/policies abuse@verizon.net
-- Ed Leafe
--- StripMime Report -- processed MIME parts --- multipart/signed text/plain (text body -- kept) application/pgp-signature ---
On 2016-01-14 10:23, Edward Leafe wrote:
Hey people: tried to reach out to Verizon, and they basically told me to piss off.
Do any of them NOT SUCK? I can't stand Verizon, AT&T, and Comcast. For as long as I can remember, they've sucked and it's just the same as the Lily Tomlin skit years ago: https://www.youtube.com/watch?v=CHgUN_95UAw
They're as bad as presidential candidates (...or nare I say, WORSE.)
ISPs here suck too, but the ones in the US seem to uber-suck.
Sadly, it's a pretty common issue to have email sent directly from an IP address range designated as "dynamic" get blocked by various spam filters.
On Thu, Jan 14, 2016 at 1:49 PM, Alan Bourke alanpbourke@fastmail.fm wrote:
ISPs here suck too, but the ones in the US seem to uber-suck.
-- Alan Bourke alanpbourke (at) fastmail (dot) fm
On Thu, 14 Jan 2016, at 04:42 PM, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
On 2016-01-14 10:23, Edward Leafe wrote:
Hey people: tried to reach out to Verizon, and they basically told me to piss off.
Do any of them NOT SUCK? I can't stand Verizon, AT&T, and Comcast. For as long as I can remember, they've sucked and it's just the same as the Lily Tomlin skit years ago: https://www.youtube.com/watch?v=CHgUN_95UAw
They're as bad as presidential candidates (...or nare I say, WORSE.)
[excessive quoting removed by server]
On Jan 14, 2016, at 2:34 PM, Ted Roche tedroche@gmail.com wrote:
Sadly, it's a pretty common issue to have email sent directly from an IP address range designated as "dynamic" get blocked by various spam filters.
But that's the thing: it isn't a dynamic address. It's part of a block of addresses managed by Digital Ocean, but it can't change. That's the whole point of providing reverse DNS.
-- Ed Leafe
--- StripMime Report -- processed MIME parts --- multipart/signed text/plain (text body -- kept) application/pgp-signature ---
Edward Leafe wrote on 2016-01-14:
On Jan 14, 2016, at 2:34 PM, Ted Roche tedroche@gmail.com wrote:
Sadly, it's a pretty common issue to have email sent directly from an IP address range designated as "dynamic" get blocked by various spam filters.
But that's the thing: it isn't a dynamic address. It's part of a block of
addresses managed by Digital Ocean, but it can't change. That's the whole point of providing reverse DNS.
-- Ed Leafe
Ed,
When PowerChurch first moved the email servers to RackSpace we had a similar problem. The user that had the IP prior to us may have put an open relay email server on it. This caused a lot of grieve for us. We ended up getting RackSpace to move us to a different IP after a few days of attempting to get off the blacklist servers.
Tracy Pearson PowerChurch Software
Sorry, bad assumption on my part.
Spamhaus reports the IP is not on their blacklists, which includes the dynamic/static feature.
So, Verizon seems pretty unjustified.
On Thu, Jan 14, 2016 at 3:51 PM, Edward Leafe ed@leafe.com wrote:
On Jan 14, 2016, at 2:34 PM, Ted Roche tedroche@gmail.com wrote:
Sadly, it's a pretty common issue to have email sent directly from an IP address range designated as "dynamic" get blocked by various spam filters.
But that's the thing: it isn't a dynamic address. It's part of a block of addresses managed by Digital Ocean, but it can't change. That's the whole point of providing reverse DNS.
-- Ed Leafe
--- StripMime Report -- processed MIME parts --- multipart/signed text/plain (text body -- kept) application/pgp-signature
[excessive quoting removed by server]
On Jan 14, 2016, at 5:49 PM, Mike Copeland mike@ggisoft.com wrote:
So, Verizon seems pretty unjustified.
Then at least they're consistent.
Oh, snap!
-- Ed Leafe
--- StripMime Report -- processed MIME parts --- multipart/signed text/plain (text body -- kept) application/pgp-signature ---
You might check to see if there's a glitch with your DKIM settings, as these look unusual:
Thu, 14 Jan 2016 07:24:22 -0800 (PST) Received-SPF: pass (google.com: domain of profoxtech-bounces@leafe.com designates 104.236.203.188 as permitted sender) client-ip=104.236.203.188; Authentication-Results: mx.google.com; spf=pass (google.com: domain of profoxtech-bounces@leafe.com designates 104.236.203.188 as permitted sender) smtp.mailfrom=profoxtech-bounces@leafe.com; dkim=temperror (no key for signature) header.i=@leafe.com; dkim=neutral (body hash did not verify) header.i=@leafe.com; dkim=neutral (body hash did not verify) header.i=@leafe.com Received: from [127.0.1.1] (localhost [127.0.0.1]) by mail.leafe.com (Postfix) with ESMTP id 1888D12635A; Thu, 14 Jan 2016 09:23:50 -0600 (CST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=leafe.com; s=mail; t=1452785030; bh=dtPNmP+RgBgXRQ8DRtxdMfd60HePBt38EhHikDYUXuA=; h=From:Subject:Date:References:To:List-Id:List-Unsubscribe: List-Help:List-Subscribe:Reply-To:From; b=qhHEyhxova24LP9XdjBDJkqdQKLDEqPueBbLgETtpgi5toLDhiB8a7WN7jEhGJ+zt vM0gYfHdQT3jcLZ5VqfXtxnpy0sE0AkJmm8Ndb+9IXb0wQUx+fbsnSZDcl0pQcRVfO Xc3z9sOcZWabn/Iw29NW04gMSo5FRwgkPLCGq+6g=
On Thu, Jan 14, 2016 at 10:23 AM, Edward Leafe ed@leafe.com wrote:
Hey people: tried to reach out to Verizon, and they basically told me to piss off. So if you have a Verizon email account (and probably reading this from the archives), please contact Verizon and ask them to reconsider.
Begin forwarded message:
From: whitelist@verizononline.net Subject: RE: Whitelist Request for IP Address 104.236.203.188 Date: January 14, 2016 at 8:00:54 AM CST To: ed@leafe.com
After investigation, Verizon Online Security has determined that e-mail from your IP address will not be allowed access to the Verizon Online e-mail domain due to one or more of the following reasons:
Your IP has been blocked because of spam issues or because your ISP indicates that it is dynamically assigned
Once you have addressed any security-related issues on your network, you should contact Verizon Online Security via this form. At that time, we will work with you to restore normal e-mail traffic or to take other action as we deem appropriate.
Sincerely,
Verizon Online Security http://www2.verizon.net/policies abuse@verizon.net
-- Ed Leafe
--- StripMime Report -- processed MIME parts --- multipart/signed text/plain (text body -- kept) application/pgp-signature
[excessive quoting removed by server]
-
Alan Bourke -
Edward Leafe -
mbsoftwaresolutions＠mbsoftwaresolutions.com -
Mike Copeland -
Ted Roche -
Tracy Pearson