![]() If you recently installed a patch/new version, try downgrading the binary or rolling back the upgrade.Check your resent configuration changes, and undo them (ini_yymmdd.rec is a copy of the config file each time it is modified, so you can use diff to find changes).Send the crash report or crash*.log file to Try disabling the virus scanner.Check startstop.log and mail.err for reasons/explanations.Check your ISP allows outgoing connections to the smtp port: telnet 25 (if it doesn't, ask them, they will usually allow it on request, or failing that you should use a g_gateway setting to send outgoing mail to an external mail server for delivery).Check your g_dns_host setting is pointing to a valid working dns server.Check the main log page in the we admin tool, look for the reason it gives for the failures.Check your router/firewall is letting port 25 into your server. ![]() Use an email test website to check your server:.Check your MX DNS entry points to your server:.Go to the 'log' page in the web admin tool, to see if your server is 'rejecting' the incoming email for some reason.Note: Most authent modules also allow extra options lie -debug to show more info. Check your authent module and backend database, the authent module is defined in surgemail.ini in the setting g_authent_process, you can test it manually like this, lets assume it's nwauth.Check login_failed.log to find out why, it will probably tell you the problem setting you need to adjust.If all else fails then you might just need to purchase another license key from our website to get the system running, we will refund this if it's not something you need once we resolve the activation problem.If your user limit is exceeded, Try tellmail users_recount (this will only work once).If SurgeMail cannot activate due to a firewall issue then it will give you details to email to be sure to send this email using 'text' not 'html' in your email client, and you should get a response within seconds with a key you can load.Check if it's actually expired and is blocking user logins (see login_failed.log), if not don't panic, just email If your key won't load, read the error it gives you carefully, it should give you some advice!.Try manually starting it: /usr/local/surgemail/surgemail_start.sh and then examine mail.log to see when it fails.If 'another' mail server is grabbing the ports then surgemail won't start (port 110, 25 etc), on linux try: netstat -tulpn.Check the end of mail.err it may give a clue to the problem.Check the end of startstop.log file, it should show if it's endlessly restarting and may give the reason.Test locally to see if it's actually running ok, if so it's a network issue: telnet localhost 25, tellmail status.Net start surgemail Server is not responding at all (check list) If you change something related to 'ports' then restart surgemail! If you modify surgemail.ini by hand then issue this command: The main log files are: (in c:\surgemail or /usr/local/surgemail) The main config file is /etc/surgemail.ini or \windows\surgemail.ini These are emergency/disaster recovery procedures to fix the server and get it running if something really bad happens.
0 Comments
Leave a Reply. |