Off topic, how to get in verizon.net's good graces?
All:
We moved to a new server, new IP address and have SPF, DMARC, and DKIM working and being accepted by all the major email providers. We implemented Send_as_List as well. By inspecting the relayed email content we can see the major email providers are saying we pass on SPF, DMARC and DKIM.
But, try as we may verizon.net still refuses to talk to our servers except to say it is rejecting our messages.
Here is an example:
Apr 3 06:53:13 www postfix/error[12377]: 4A718272B: to=< verizonclient@verizon.net>, relay=none, delay=0.12, delays=0.03/0.06/0/0.03, dsn=4.0.0, status=deferred (delivery temporarily suspended: host relay.verizon.net[206.46.232.11] refused to talk to me: 571 Email from 192.168.1.1 is currently blocked by Verizon Online's anti-spam system. The email sender or Email Service Provider may visit http://www.verizon.net/whitelist and request removal of the block. 160403)
The email address above is changed as well as the IP address of our email server.
I have submitted multiple whitelist requests as shown above, and have seen no response whatsoever from Verizon. Frustrating. This has been going on for 5 days now.
I am about to send emails out directly to our list subscribers asking them to migrate to another email provider, but thought I would ask the list if anyone else had any success with verizon.net and how they did it.
Thanks in advance,
Arlen Raasch
Arlen Raasch writes:
But, try as we may verizon.net still refuses to talk to our servers except to say it is rejecting our messages.
I thank the members of the Olympic Pantheon that my list members respond to "get an address with a Provider That Cares[tm]" with "I've been meaning to do that for a while, thanks for the reminder!"
suspended: host relay.verizon.net[206.46.232.11] refused to talk to me: 571 Email from 192.168.1.1 is currently blocked by Verizon Online's anti-spam system. The email sender or Email Service Provider may visit http://www.verizon.net/whitelist and request removal of the block. 160403)
Have you checked the RBLs? There are many of them, and now there are services that will check a whole list for you; Googling "RBL checker" got a bunch of services. I've used mxtoolbox.com myself, but I can only say I'm satisfied, I haven't done any comparisons. Since you're actually having problems, you might want to try a couple more if you get a clean bill of health from just one. One advantage of mxtoolbox is that they check more than just your RBL status, they do some validation on your DNS and MTA, too.
I have submitted multiple whitelist requests as shown above, and have seen no response whatsoever from Verizon. Frustrating. This has been going on for 5 days now.
IME, 5 days for a response from the large ISPs is at least a birdie, maybe an eagle. :-) My sister hates Verizon but has no choice of ISP, FWIW. (Her emails are corporate and GMail, for that reason.)
Your users will probably be happier if you can get Verizon to stop blocking you, rather than changing their addresses.
Sorry I can't be of more help, maybe somebody else knows somebody at Verizon....
Steve
On 04/03/2016 07:06 PM, Arlen Raasch wrote:
We moved to a new server, ...
But, try as we may verizon.net still refuses to talk to our servers except to say it is rejecting our messages.
...
I have submitted multiple whitelist requests as shown above, and have seen no response whatsoever from Verizon. Frustrating. This has been going on for 5 days now.
I'm sorry to say, welcome to the club.
This has been going on for 5 months since the old mail.python.org server died and was replaced late last October.
I am about to send emails out directly to our list subscribers asking them to migrate to another email provider, but thought I would ask the list if anyone else had any success with verizon.net and how they did it.
I'm not sure what the current status is with mail.python.org. We haven't seen any Mailman list bounces since mid January. Maybe everyone got unsubscribed by bounce processing. I thought we had actually done something to stop sending to verizon.net, but I can't find anything (if it was done, I didn't do it).
Good luck, and if anyone has a way to actually contact Verizon other than by submitting forms to an apparent black hole, please let us know.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Well, I am glad (in a way) to hear that its not just me.
By the way, I learned that Verizon does not issue verizon.net accounts to its new landline customers. It seems they don't want to compete with AOL, which they now own.
As such, it may be that few company resources are assigned to handling such stuff inside what remains of the deprecated verizon.net company.
Arlen Raasch
On Sun, Apr 3, 2016 at 11:13 PM, Mark Sapiro <mark@msapiro.net> wrote:
On 04/03/2016 07:06 PM, Arlen Raasch wrote:
We moved to a new server, ...
But, try as we may verizon.net still refuses to talk to our servers
except
to say it is rejecting our messages. ... I have submitted multiple whitelist requests as shown above, and have seen no response whatsoever from Verizon. Frustrating. This has been going on for 5 days now.
I'm sorry to say, welcome to the club.
This has been going on for 5 months since the old mail.python.org server died and was replaced late last October.
I am about to send emails out directly to our list subscribers asking them to migrate to another email provider, but thought I would ask the list if anyone else had any success with verizon.net and how they did it.
I'm not sure what the current status is with mail.python.org. We haven't seen any Mailman list bounces since mid January. Maybe everyone got unsubscribed by bounce processing. I thought we had actually done something to stop sending to verizon.net, but I can't find anything (if it was done, I didn't do it).
Good luck, and if anyone has a way to actually contact Verizon other than by submitting forms to an apparent black hole, please let us know.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/araasch%40gmail.com
Oh, and Steve, I have been using mxtoolbox for some time. Great tool. They think our mail server is the man, as in "You da man!".
I got a verizon.net account to use to test against, and could send outbound emails from it to my gmail account fine. But, verizon.net even rejected emails from my gmail account, not through any relay! I also whitelisted the relay domain inside the web interface for the verizon.net test account to see if I could get one email through to inspect. No dice!
Verizon must have its shields set to ludicrous.
I think I have had enough and will email the subscribers using still attempting to use verizon.net to find a provider who cares tomorrow.
Thanks again,
Arlen Raasch
On Sun, Apr 3, 2016 at 11:22 PM, Arlen Raasch <araasch@gmail.com> wrote:
Well, I am glad (in a way) to hear that its not just me.
By the way, I learned that Verizon does not issue verizon.net accounts to its new landline customers. It seems they don't want to compete with AOL, which they now own.
As such, it may be that few company resources are assigned to handling such stuff inside what remains of the deprecated verizon.net company.
Arlen Raasch
On Sun, Apr 3, 2016 at 11:13 PM, Mark Sapiro <mark@msapiro.net> wrote:
On 04/03/2016 07:06 PM, Arlen Raasch wrote:
We moved to a new server, ...
But, try as we may verizon.net still refuses to talk to our servers
except
to say it is rejecting our messages. ... I have submitted multiple whitelist requests as shown above, and have seen no response whatsoever from Verizon. Frustrating. This has been going on for 5 days now.
I'm sorry to say, welcome to the club.
This has been going on for 5 months since the old mail.python.org server died and was replaced late last October.
I am about to send emails out directly to our list subscribers asking them to migrate to another email provider, but thought I would ask the list if anyone else had any success with verizon.net and how they did it.
I'm not sure what the current status is with mail.python.org. We haven't seen any Mailman list bounces since mid January. Maybe everyone got unsubscribed by bounce processing. I thought we had actually done something to stop sending to verizon.net, but I can't find anything (if it was done, I didn't do it).
Good luck, and if anyone has a way to actually contact Verizon other than by submitting forms to an apparent black hole, please let us know.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/araasch%40gmail.com
participants (3)
-
Arlen Raasch -
Mark Sapiro -
Stephen J. Turnbull