Happy 7-year Argosoft user, though only a few months with the dot net version.
Our current system is behind a Barracuda router. I have not used SMTP authentication in the past, with only one instance in 7 years of someone sneaking in to do mischief. Pro version was always set to relay for existing accounts only. Seemed to be fine.
Set the dot net version to do the same. Again, it's worked fine for months.
Now, we've been blacklisted by NJABL.com. These folks test for open relays by trying out several combinations of user names and passwords so they can identify servers using the above scheme and tag them as "open relays." (So now I've experienced 2 times in 7 years where someone snuck in to do mischief, one being supposed good guys). Since, apparently, Barracuda uses NJABL, Barracuda servers are now blocking us.
So I gritted my teeth and set Argosoft to require SMTP authentication. It will be a nuisance to go around and change everyone's client, but there you are.
Except SMTP authentication being set makes no difference. Even with it set, folks can get in and relay without having their clients set to provide authentication. Similarly, setting POP3/IMAP before SMTP allows an outsider with an existing account to relay without logging in for POP3 first.
Anybody have any idea what's going on here?
I don't see much point in getting off the NJABL list until I can get it set to block the snoops. Any suggestions of something to try would be welcomed.
Thanks.
Charles