Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Installation
Reload this Page Relatively new install stopped sending email

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 03-12-2008, 08:20 PM
New Member
  
Posts: 3
Default Relatively new install stopped sending email
Was working fine, now I get a network error when sending email. iptables and ip6tables stopped SELinux disabled, not sure what changed. I use an outbound relay, that was working fine.

I am not sure if the cookie warning is related.

As you can see in the trace this is version 5.0.2_GA_1975 on Fedora 7
Stacktrace from mailbox.log

Any help would be appreciated

2008-03-12 22:53:12,920 WARN [btpool0-3] [] HttpMethodBase - Cookie rejected: "$Version=0; B=7e4p2h13th5r1&b=3&s=sv; $Path=/; $Domain=.yahoo.com". Domain attribute ".yahoo.com" violates RFC 2109: host minus domain may not contain any dots
2008-03-12 22:54:21,004 INFO [btpool0-3] [name=myname@mydomain.us;mid=6;ip=10.213.1.11;ua=Zi mbraWebClient - SAF (Mac)/5.0.2_GA_1975.F7;] SendMsg - LC(mbox=42a62d3e-a092-43bf-a348-95c2d614117d, sessions=16)
2008-03-12 22:54:21,006 INFO [btpool0-3] [name=myname@mydomain.us;mid=6;ip=10.213.1.11;ua=Zi mbraWebClient - SAF (Mac)/5.0.2_GA_1975.F7;] smtp - Sending message: Message-ID=<21578710.121205376861006.JavaMail.root@mail.mydoma in.us>, replyType=r
2008-03-12 22:54:21,116 INFO [btpool0-3] [name=myname@mydomain.us;mid=6;ip=10.213.1.11;ua=Zi mbraWebClient - SAF (Mac)/5.0.2_GA_1975.F7;] mailbox - Added message: id=380, digest=QwvH+V8I5gLOM5oIwEOQZNdKlek=, folderId=5, folderName=Sent
2008-03-12 22:54:21,128 WARN [btpool0-3] [name=myname@mydomain.us;mid=6;ip=10.213.1.11;ua=Zi mbraWebClient - SAF (Mac)/5.0.2_GA_1975.F7;] smtp - exception occurred during SendMsg
com.zimbra.cs.mailbox.MailSender$SafeMessagingExce ption: Connection refused; chained exception is:
java.net.ConnectException: Connection refused
at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTra nsport.java:1378)
at com.sun.mail.smtp.SMTPTransport.protocolConnect(SM TPTransport.java:399)
at javax.mail.Service.connect(Service.java:275)
at javax.mail.Service.connect(Service.java:156)
at javax.mail.Service.connect(Service.java:105)
at javax.mail.Transport.send0(Transport.java:168)
at javax.mail.Transport.send(Transport.java:98)
at com.zimbra.cs.mailbox.MailSender.sendMessage(MailS ender.java:428)
at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(M ailSender.java:248)
at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(M ailSender.java:115)
at com.zimbra.cs.service.mail.SendMsg.doSendMessage(S endMsg.java:184)
at com.zimbra.cs.service.mail.SendMsg.handle(SendMsg. java:150)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:342)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:208)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:113)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:272)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:174)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1093)
at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:132)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1084)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:360)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:716)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:406)
at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:211)
at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.handler.RewriteHandler.handle(Re writeHandler.java:176)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:313)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:506)
at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:844)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:644)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:205)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:381)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:396)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:442)
2008-03-12 22:54:21,129 INFO [btpool0-3] [name=ellen@altschuler.us;mid=6;ip=10.213.1.11;ua=Z imbraWebClient - SAF (Mac)/5.0.2_GA_1975.F7;] SoapEngine - handler exception
com.zimbra.common.service.ServiceException: system failure: MessagingException
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:183)
at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(M ailSender.java:315)
at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(M ailSender.java:115)
at com.zimbra.cs.service.mail.SendMsg.doSendMessage(S endMsg.java:184)
at com.zimbra.cs.service.mail.SendMsg.handle(SendMsg. java:150)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:342)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:208)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:113)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:272)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:174)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1093)
at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:132)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1084)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:360)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:716)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:406)
at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:211)
at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.handler.RewriteHandler.handle(Re writeHandler.java:176)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:313)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:506)
at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:844)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:644)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:205)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:381)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:396)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:442)
Caused by: com.zimbra.cs.mailbox.MailSender$SafeMessagingExce ption: Connection refused; chained exception is:
java.net.ConnectException: Connection refused
at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTra nsport.java:1378)
at com.sun.mail.smtp.SMTPTransport.protocolConnect(SM TPTransport.java:399)
at javax.mail.Service.connect(Service.java:275)
at javax.mail.Service.connect(Service.java:156)
at javax.mail.Service.connect(Service.java:105)
at javax.mail.Transport.send0(Transport.java:168)
at javax.mail.Transport.send(Transport.java:98)
at com.zimbra.cs.mailbox.MailSender.sendMessage(MailS ender.java:428)
at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(M ailSender.java:248)
... 33 more
Reply With Quote
  #2 (permalink)  
Old 03-13-2008, 02:09 AM
Moderator
  
Posts: 7,928
Default
Welcome to the forums

Can you still connect to the outbound relay okay from the command line ? eg. if on port 25 and relay is called relay.domain.com :-

Code:
telnet relay.domain.com 25
Does it answer ?
__________________
Reply With Quote
  #3 (permalink)  
Old 03-13-2008, 06:01 AM
New Member
  
Posts: 3
Default Follow up on port test
AT&T.net (Formerly Bellsouth.net) has been blocking port 25 for years.

I had been using 2525 and tried 10465 for funsies. Both continue to answer to telnet.

I am hoping you have a next question for me. I really appreciate the rapid response to my post.
Reply With Quote
  #4 (permalink)  
Old 03-13-2008, 08:55 AM
Moderator
  
Posts: 7,928
Default
What does :-
Code:
zmcontrol status
show ? Is the MTA service actually running.
__________________
Reply With Quote
  #5 (permalink)  
Old 03-13-2008, 11:09 AM
New Member
  
Posts: 3
Default
It sure is.
Reply With Quote
Reply

« Previous Thread | Today's Posts or Week's Posts | Next Thread »

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes
Linear Mode Linear Mode


Similar Threads

Product Information

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com


Home - Blog - Contact Us - Archive - Top


 

SEO by vBSEO ©2011, Crawlability, Inc.