http://msmvps.com/blogs/bradley/archive/2005/02/20/36536.aspxIn case your clients are seeing this... a heads up: "AS OF JANUARY 31, 2005, VERIZON WILL NO LONGER ALLOW BUSINESS OR RESIDENTIAL CUSTOMERS WITH DYNAMIC WAN IPS TO RELAY THROUGH THEIR SMTP SERVERS." Merv had an issue where all of a sudden his clientsenCommunityServer 2008.5 SP2 (Build: 40407.4157)http://msmvps.com/blogs/bradley/archive/2005/02/20/36536.aspx#63470Sat, 20 Aug 2005 08:36:00 GMTd67277c4-116b-43f1-b688-e9ef184ea916:63470TrackBackA few months ago, Verizon enabled some server settings changes on their mail servers which effectively broke the ability to send outbound e-mail through their mail servers (see the discussions on Susan Bradley's blog postings We Do Stop Working For...<div style="clear:both;"></div><img src="http://msmvps.com/aggbug.aspx?PostID=63470" width="1" height="1">http://msmvps.com/blogs/bradley/archive/2005/02/20/36536.aspx#37175Mon, 28 Feb 2005 09:56:00 GMTd67277c4-116b-43f1-b688-e9ef184ea916:37175bradleyHave you, or anyone, gotten Exchange 2003 to work with MailHop Outbound? I got their service and followed the directions in their KB (which they admit they got from a user), but I'm getting an SMTP protocol error in the queue. If possible, please mail kenneth.mcandrew@verizon.net with information. Thanks!<div style="clear:both;"></div><img src="http://msmvps.com/aggbug.aspx?PostID=37175" width="1" height="1">http://msmvps.com/blogs/bradley/archive/2005/02/20/36536.aspx#37163Mon, 28 Feb 2005 02:25:00 GMTd67277c4-116b-43f1-b688-e9ef184ea916:37163bradleyI was told that if I set up my client with a static IP on Verizon DSL, that I could then relay through Verizon's SMTP server. I mentioned to the Verizon tech guy who answered the phone that if I had a static IP I wouldn't be using a !@#$% smarthost to begin with, duh. <br> <br>I am not sure he was terribly sympathentic, but then again, he's just a poor phone jockey. <br> <br>I hate Verizon. <div style="clear:both;"></div><img src="http://msmvps.com/aggbug.aspx?PostID=37163" width="1" height="1">http://msmvps.com/blogs/bradley/archive/2005/02/20/36536.aspx#36730Wed, 23 Feb 2005 02:59:00 GMTd67277c4-116b-43f1-b688-e9ef184ea916:36730TrackBack<div style="clear:both;"></div><img src="http://msmvps.com/aggbug.aspx?PostID=36730" width="1" height="1">http://msmvps.com/blogs/bradley/archive/2005/02/20/36536.aspx#36661Tue, 22 Feb 2005 01:51:00 GMTd67277c4-116b-43f1-b688-e9ef184ea916:36661TrackBack<div style="clear:both;"></div><img src="http://msmvps.com/aggbug.aspx?PostID=36661" width="1" height="1">http://msmvps.com/blogs/bradley/archive/2005/02/20/36536.aspx#36648Mon, 21 Feb 2005 22:07:00 GMTd67277c4-116b-43f1-b688-e9ef184ea916:36648bradleyThe source is a Verizon Tech I talked with yesterday. He didn't have any more info other than to say that it was being &quot;phased in&quot; so all customers wouldn't be affected at the same time. Aaarrrrghhh is right!<div style="clear:both;"></div><img src="http://msmvps.com/aggbug.aspx?PostID=36648" width="1" height="1">http://msmvps.com/blogs/bradley/archive/2005/02/20/36536.aspx#36642Mon, 21 Feb 2005 20:11:00 GMTd67277c4-116b-43f1-b688-e9ef184ea916:36642bradleyOK, an update. I have a client who meets the restrictions listed in the notice above and still cannot relay through Verizon's mail servers. What's the source on that notice from Verizon?<div style="clear:both;"></div><img src="http://msmvps.com/aggbug.aspx?PostID=36642" width="1" height="1">http://msmvps.com/blogs/bradley/archive/2005/02/20/36536.aspx#36604Mon, 21 Feb 2005 13:58:00 GMTd67277c4-116b-43f1-b688-e9ef184ea916:36604bradleyArgh! yeah, this woudl have been good to know in advance. Unfortunately, the lovely people at verizon tech support had no clue that this was going on. <br> <br>*sigh* Time to get a new ISP...<div style="clear:both;"></div><img src="http://msmvps.com/aggbug.aspx?PostID=36604" width="1" height="1">