An exception was thrown: java.lang.NullPointerException
With the following stack trace:
java.lang.NullPointerException at com.netdorm.bo.BoRegTLDList.getRegionTLD(BoRegTLDList.java:130) at org.apache.jsp.sites.domains.domain_002dtop_jsp._jspService(domain_002dtop_jsp.java:210) at com.netdorm.servlet.JspBaseApp.service(JspBaseApp.java:62) at javax.servlet.http.HttpServlet.service(HttpServlet.java:742) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:443) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:386) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:330) at javax.servlet.http.HttpServlet.service(HttpServlet.java:742) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:728) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:591) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:527) at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:894) at org.apache.jsp.index_jsp._jspService(index_jsp.java:359) at com.netdorm.servlet.JspBaseApp.service(JspBaseApp.java:62) at javax.servlet.http.HttpServlet.service(HttpServlet.java:742) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:443) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:386) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:330) at javax.servlet.http.HttpServlet.service(HttpServlet.java:742) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:728) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:591) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:527) at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:894) at org.apache.jsp.services.mail_002dsmtp_002dbackup_002dsecondary_002dmx.index_jsp._jspService(index_jsp.java:109) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:742) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:443) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:386) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:330) at javax.servlet.http.HttpServlet.service(HttpServlet.java:742) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:198) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81) at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:650) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342) at org.apache.coyote.ajp.AjpProcessor.service(AjpProcessor.java:486) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:790) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1459) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:748)
If your mail server goes down or is inaccessible from the internet, your emails will automatically fail over to our backup MX server. Our mail server will queue your emails and automatically forward emails to your server after it comes back available.
All email users will be able to read/reply emails through our webmail or POP3 while your server is down.
Mail Backup FAQ
's mail backup service acts as your second priority mail server. If your mail server cannot be reached, the mail will be routed to our mail backup server and wait in queues. Our server will keep checking your mail server every 20 minutes. Once your mail server is detected available, our mail server will forward the emails to your mail server. Our mail server will keep attempting to deliver mail to your server for 5 days. Mails queued in our mail server exceeding 5 days will be returned to the sender. You have option to turn on Spamassassin Spam checking on your emails. Emails found to be Spam will be drop out before reaching your email server. Web interface was provided to check queued emails and even read your emails even when your mail server is down.You also have option to set the mail back to monitoring mode that we will monitor you mail server every 8 minutes and will only accept emails for your domain only when your server is down.
While your mail server is down, you can turn on the Mail Rescue Mode for the backup and all queued up emails will be re-routed to our mail rescue server where all the domain's email users can access their corresponding mail boxes to read and reply emails. After your mail server is available, you get the option to suck up all emails at their mail boxes to your own server.
The mail backup for your domain can be at Monitoring Mode. In this case, we will monitor your mail server and reject emails to your domain while your primary mail server is up.
The advantage for using Monitoring Mode is that it will reduce at least 80% of Spam emails hitting your server. As you may not know that Spam usually send email in reverse order. Or in other words, they tend to send Spam emails to secondary MX(while it is available) first instead. While sending Spam in such large volume, they usually won't bother to re-try and will drop out if the sending attempts fails. Good emails should never hit the secondary MX while primary MX is up.
