Since last evening, I can only receive emails, but can not send any. I'm getting a note that Dynadot has been listed as spam when I try to send through Outlook. Are you aware of this issue?
Over here, neither sending nor receiving e-mail is working ("server connection terminated"), website is down for "scheduled maintenance" (when was it scheduled?) -- would be nice to hear from Dynadot what's going on. Thanks.
Would anyone, by chance, have Comcast as their ISP? Here is the exact message that I'm getting using MSOutlook:
Task '[[email protected]] - Sending' reported error (0x800CCC0F) : 'The connection to the server was interrupted. If this problem continues, contact your server administrator or Internet service provider (ISP). The server responded: 421 smtp.webhost.dynadot.com your ip address has been banned due to spam complaints'
IP address that my system is using is 67.189.209.246
We have removed the IP checking from our SMTP server, so this problem should be resolved now. Please let us know if you continue to experience any difficulties. Thank you again for your patience and understanding.
Technical details of temporary failure: The recipient server did not accept our requests to connect. Learn more at http://support.google.com/mail/bin/answer.py?answer=7720 [(0) parkmail.dynadot.com. [54.214.28.174]:25: 421 parkmail.dynadot.com your ip address has been banned due to spam complaints]
Technical details of temporary failure: The recipient server did not accept our requests to connect. Learn more at http://support.google.com/mail/bin/answer.py?answer=7720 [(0) parkmail.dynadot.com. [54.214.28.174]:25: 421 parkmail.dynadot.com your ip address has been banned due to spam complaints]
Those errors relate to email received. As it turns out, many spammers use gmail addresses. When we initially added our spam filters, we would block the sending IP when an unwanted message was received. This was a bit too broad, however, as many addresses will share the same IP. We have now focused the filter to block only the specific address, so this error too should now be resolved.
We'd like to thank you all again for your patience and understanding.