Hi there.
I've been a Sonic customer for about ten years, and until recently, I've been sending mail without having to authenticate to mail.sonic.net so long as I connect from a Sonic IP address. Earlier this year, the server started refusing my messages, but only sometimes. The error given is "Relaying denied. Proper authentication required." If I retry enough times, my message is eventually accepted.
I have multiple machines running various kinds of email software (desktop user agents, command line user agents, transfer agents, etc.), so configuring every one of them with my Sonic username and password is both cumbersome and a bit of a security problem. (Storing my password unencrypted in multiple places makes the security admin in me twitch, as I think about how it can be used to access my incoming email and therefore most of my accounts on the internet.) In other words, I really don't want to have to start managing SMTP server logins just to keep my mail-sending systems working as they have for a decade.
I find it really puzzling that Sonic would deliberately disable the functionality that has worked so well for so long, and even more puzzling that the change would only take effect some of the time. Can someone shed some light on this, and better yet, fix it?
I've been a Sonic customer for about ten years, and until recently, I've been sending mail without having to authenticate to mail.sonic.net so long as I connect from a Sonic IP address. Earlier this year, the server started refusing my messages, but only sometimes. The error given is "Relaying denied. Proper authentication required." If I retry enough times, my message is eventually accepted.
I have multiple machines running various kinds of email software (desktop user agents, command line user agents, transfer agents, etc.), so configuring every one of them with my Sonic username and password is both cumbersome and a bit of a security problem. (Storing my password unencrypted in multiple places makes the security admin in me twitch, as I think about how it can be used to access my incoming email and therefore most of my accounts on the internet.) In other words, I really don't want to have to start managing SMTP server logins just to keep my mail-sending systems working as they have for a decade.
I find it really puzzling that Sonic would deliberately disable the functionality that has worked so well for so long, and even more puzzling that the change would only take effect some of the time. Can someone shed some light on this, and better yet, fix it?