Originally Posted by mylinear

I was about to post about this too.

I just spent over half an hour trying to tell TM the same thing. I think this is a big mistake, especially that they announce an immediate implementation.

First the initial support person was giving me the wrong info on the changes to be made. He had to put me on hold 3 times to go check the info. Then I insisted on speaking to the supervisor, who was supposedly in a meeting. Finally got to the supervisor.

He did not seem to have much knowledge on this matter. First he said that TM IPs have been blacklisted so they have to make these changes. I said they could have changed the IPs instead while finding a solution. I explained how this would affect hosting companies and their clients and anybody using a hosting mailserver. He did not seem to know that there are such effects. It seems like they think you just need to change the SMTP servername from whatever you are using to what they give you an all will be fine.

I think the mailserver IP of the outgoing email will now show that of TM's, which means if the receiving mailserver is doing verification that your domain and the IP should be matching, it may reject mails. When I checked, their SPF record does not list their new mailservername nor its IP. This could cause problem for receiving mailserver which check on this. I think a lot of emails may end up in Junk or Bulk folders due to this change.

It is silly to implement such a thing without any notice. They just don't seem to care about any negative effects to others, that is, if they even know there are such effects. Yes, all the havoc will start in the morning when offices open when emails don't go out.