David Ramsey wrote: > A few months ago, I set up a Barracuda Spam Firewall to help manage the > loads of spam my mail server was getting. > > I created an MX record for my domain to point to the Barracuda. > Everything worked great. > > Except that there was still some spam coming in because the spammers > were sending directly to the SMTP port on my server, and ignoring the > MX record. > > OK, so I changed my mail server's SMTP port to a non-standard port, and > reconfigured the Barracuda to send to that port. Everything worked > great. Users had to reconfigure their SMTP settings in their mail > clients, but it was all cleared up in a day or two and the spam load > dropped to pretty much zero. > > Except said users can no longer send mail through Squirrelmail. Click > the "Send" button and the error is "Connection refused/Server replied: > 61".
So your server gave an error back to SM. Go see your server log to get a better idea of what went wrong. Post those logs if you still need help. > Yes, I reconfigured Squirrelmail's SMTP settings to use the new port. > No, I didn't change anything else...no TLS, etc. > > Anyone have any ideas? I've searched online, scoured the archives, and > haven't seen anything like this. > > -- David Ramsey > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click -- squirrelmail-users mailing list Posting Guidelines: http://www.squirrelmail.org/wiki/MailingListPostingGuidelines List Address: squirrelmail-users@lists.sourceforge.net List Archives: http://news.gmane.org/thread.php?group=gmane.mail.squirrelmail.user List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
