Cannot send from WebMail

[kernelklink]

Hello,

We recently setup zimbra on a new server. Running version:
Release 5.0.13_GA_2791.openSUSE_10.2_20090206132026 openSUSE_10.2 FOSS edition

Everything works great up until I wake up in the morning, POP & SMTP still work but when trying to use the webmail to send out were getting "network exception error" on the frontend and this in the mailbox.log

-------------------------------------------

2009-03-13 06:21:29,202 INFO [btpool0-16] [name=user@mydomain.com;mid=136;ip=24.68.230.246;ua =ZimbraWebClient - FF3.0 (Win)/5.0.13_GA_2791.openSUSE_10.2;] soap - SendMsgRequest
2009-03-13 06:21:29,202 INFO [btpool0-16] [name=user@mydomain.com;mid=136;ip=24.68.230.246;ua =ZimbraWebClient - FF3.0 (Win)/5.0.13_GA_2791.openSUSE_10.2;] SendMsg - LC(mbox=6d258651-02f1-48cc-a146-8de1e8a89c88, sessions=1263)
2009-03-13 06:21:29,203 INFO [btpool0-16] [name=user@mydomain.com;mid=136;ip=24.68.230.246;ua =ZimbraWebClient - FF3.0 (Win)/5.0.13_GA_2791.openSUSE_10.2;] smtp - Sending message: Message-ID=<16703963.3581236950489203.JavaMail.root@mail.mydom ain.com>, replyType=r
2009-03-13 06:21:29,212 INFO [btpool0-16] [name=user@mydomain.com;mid=136;ip=24.68.230.246;ua =ZimbraWebClient - FF3.0 (Win)/5.0.13_GA_2791.openSUSE_10.2;] mailop - Adding Message: id=378, Message-ID=<16703963.3581236950489203.JavaMail.root@mail.mydom ain.com>, parentId=-1, folderId=5, folderName=Sent.
2009-03-13 06:21:29,244 INFO [btpool0-16] [name=user@mydomain.com;mid=136;ip=24.68.230.246;ua =ZimbraWebClient - FF3.0 (Win)/5.0.13_GA_2791.openSUSE_10.2;] mailop - Deleting Message (id=378).
2009-03-13 06:21:29,248 WARN [btpool0-16] [name=user@mydomain.com;mid=136;ip=24.68.230.246;ua =ZimbraWebClient - FF3.0 (Win)/5.0.13_GA_2791.openSUSE_10.2;] smtp - exception occurred during SendMsg
com.zimbra.cs.mailbox.MailSender$SafeMessagingExce ption
at javax.mail.Service.connect(Service.java:306)
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:535)
at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(M ailSender.java:253)
at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(M ailSender.java:118)
at com.zimbra.cs.service.mail.SendMsg.doSendMessage(S endMsg.java:196)
at com.zimbra.cs.service.mail.SendMsg.handle(SendMsg. java:156)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:429)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:286)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:160)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:269)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:190)
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.rewrite.RewriteHandler.h andle(RewriteHandler.java:350)
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:211)
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)

-------------------------------------------

Also, I noticed it also occurs with a user setup with an out of office reply.

-------------------------------------------

2009-03-13 06:45:56,086 INFO [LmtpServer-1567] [ip=192.168.220.100;] lmtp - Delivering message: size=6177 bytes, nrcpts=1, sender=smtp@domain.com, msgid=<20090313134550.C6D582338001@mail.mydomain.com>
2009-03-13 06:45:56,091 INFO [LmtpServer-1567] [name=user@mydomain.com;mid=8;] mailop - Adding Message: id=17571, Message-ID=<20090313134550.C6D582338001@mail.mydomain.com>, parentId=-1, folderId=2, folderName=Inbox.
2009-03-13 06:45:56,107 INFO [LmtpServer-1567] [name=user@mydomain.com;mid=8;] mailbox - outofoffice not sent (send failed) mid=17571 rcpt='user@mydomain.com' dest='smtp@domain.com'
javax.mail.AuthenticationFailedException
at javax.mail.Service.connect(Service.java:306)
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.Notification.outOfOfficeIfNe cessary(Notification.java:309)
at com.zimbra.cs.mailbox.Notification.afterDelivery(N otification.java:104)
at com.zimbra.cs.lmtpserver.ZimbraLmtpBackend.deliver MessageToLocalMailboxes(ZimbraLmtpBackend.java:396 )
at com.zimbra.cs.lmtpserver.ZimbraLmtpBackend.deliver (ZimbraLmtpBackend.java:138)
at com.zimbra.cs.lmtpserver.LmtpHandler.processMessag eData(LmtpHandler.java:375)
at com.zimbra.cs.lmtpserver.TcpLmtpHandler.continueDA TA(TcpLmtpHandler.java:67)
at com.zimbra.cs.lmtpserver.LmtpHandler.doDATA(LmtpHa ndler.java:364)
at com.zimbra.cs.lmtpserver.LmtpHandler.processComman d(LmtpHandler.java:174)
at com.zimbra.cs.lmtpserver.TcpLmtpHandler.processCom mand(TcpLmtpHandler.java:61)
at com.zimbra.cs.tcpserver.ProtocolHandler.processCon nection(ProtocolHandler.java:160)
at com.zimbra.cs.tcpserver.ProtocolHandler.run(Protoc olHandler.java:128)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Wo rker.run(Unknown Source)
at java.lang.Thread.run(Thread.java:595)

-----------------------------------------

It seems a simple zmcontrol stop && zmcontrol start fixes the issue but we dont want to have to keep doing this every morning at 6AM.

Any ideas?

Thanks

[uxbod]

Any errors reported in /var/log/zimbra.log for Postfix ?

[kernelklink]

Nothing I can see that stands out...is there something specific I should be looking for?

[kernelklink]

It also happend again sometime today, it's the weekend though it should be my day off. I need this fixed asap No errors in the logs that I can see. Tried doing a zmfixperms, also regenerated the httpd xml configs. This server runs over 500 email addresses and they are all constantly used. POP & SMTP work fine which is weird, only the Web interface gives that network exception error. Ill try to get a copy & paste of it next time it occurs but its something about soap.FAILURE...any ideas?

*EDIT*

Just noticed this, not sure if it would cause just the web interface to stop sending mail...There's an odd time leap from 13:10 to 21:10 then goes back to 13.

Mar 14 13:09:48 mail zmmailboxdmgr[11048]: status requested
Mar 14 13:09:48 mail zmmailboxdmgr[11048]: status OK
Mar 14 13:09:55 mail postfix/smtpd[1163]: connect from 82.198.23.77.satgate.net[82.198.23.77]
Mar 14 13:10:01 mail postfix/sendmail[11104]: warning: inet_protocols: IPv6 support is disabled: Ad$
Mar 14 13:10:01 mail postfix/sendmail[11104]: warning: inet_protocols: configuring for IPv4 support$
Mar 14 13:10:01 mail postfix/sendmail[11107]: warning: inet_protocols: IPv6 support is disabled: Ad$
Mar 14 13:10:01 mail postfix/sendmail[11107]: warning: inet_protocols: configuring for IPv4 support$
Mar 14 21:10:01 mail postfix/postdrop[11115]: warning: inet_protocols: IPv6 support is disabled: Ad$
Mar 14 21:10:01 mail postfix/postdrop[11115]: warning: inet_protocols: configuring for IPv4 support$
Mar 14 21:10:01 mail postfix/postdrop[11116]: warning: inet_protocols: IPv6 support is disabled: Ad$
Mar 14 21:10:01 mail postfix/postdrop[11116]: warning: inet_protocols: configuring for IPv4 support$
Mar 14 13:10:01 mail zimbramon[11093]: 11093:info: 2009-03-14 13:10:01, QUEUE: 3 2

[kernelklink]

Help? Anyone?

[Bill Brock]

[SOLVED] Upgraded to 5.0 OSS - Sendmail Problem

Cron may be trying to start up a conflicting service.

[kernelklink]

Hey,

Thanks for the reply, I've checked and made sure sendmail isnt installed, it was actually removed right after the inital OS install. Checked my cron jobs but nothing is listed.

mail:~ # crontab -l -u root
no crontab for root

Performing a fetchmail -V gives me:

zimbra@mail:~> fetchmail -V
This is fetchmail release 6.3.5+POP2+IMAP-GSS+RPA+NTLM+SDPS+SSL+OPIE+SOCKS+NLS.

Copyright (C) 2002, 2003 Eric S. Raymond
Copyright (C) 2004 Matthias Andree, Eric S. Raymond, Rob F. Funk, Graham Wilson
Copyright (C) 2005-2006 Matthias Andree, Sunil Shetye
Fetchmail comes with ABSOLUTELY NO WARRANTY. This is free software, and you
are welcome to redistribute it under certain conditions. For details,
please see the file COPYING in the source or documentation directory.

Fallback MDA: (none)
Linux mail.mydomain.com 2.6.18.2-34-bigsmp #1 SMP Mon Nov 27 11:46:27 UTC 2006 i686 i686 i386 GNU/Linux
Taking options from command line
No mailservers set up -- perhaps /opt/zimbra/.fetchmailrc is missing?

What should I check next?

[kernelklink]

It's great how everyone else in this forum receives troubleshooting advice except for me, I get one reply to something that doesnt even pertain to my problem. It happend again this morning....network service error...nothing in logs, POP & SMTP work, just not the web interface...need this resolved asap. Tried zmfixperms, regenerating xml configs, nothign in crontab, no conflicting services installed...

[phoenix]

OK, let's get this out of the way first.

Originally Posted by kernelklink

We recently setup zimbra on a new server. Running version:
Release 5.0.13_GA_2791.openSUSE_10.2_20090206132026 openSUSE_10.2 FOSS edition

There will be no support for openSUSE after the current 5.x build of Zimbra, you may want to consider another distribution for running Zimbra. If you want further details please search the forums.

You don't really say whether this problem has always happened, just started happening what recent upgrades you made to openSUSE, whether you've got this on a LAN or Public IP nor whether you have the firewall and AppArmor disabled. Is there a hardware problem such as the cable and the NIC in the server? A Network Exception Error is usually symptomatic of a lost connection to the server. Have you moved this installation of Zimbra from one server to another? If you have, what steps did you use? Have you made any modification to Zimbra and if so, what are they?

If you're on a LAN, have you set-up a Split DNS

Lets do the usual with DNS etc. Run the following commands on the Zimbra server (post the output here):

cat /etc/hosts 
cat /etc/resolv.conf
dig yourdomain.com mx
dig yourdomain.com any
host `hostname`  <-- type that exactly and use backticks not single quotes
host -v name.yourdomain.com  <-- use the FQDN of your server

[kernelklink]

You don't really say whether this problem has always happened, just started happening what recent upgrades you made to openSUSE, whether you've got this on a LAN or Public IP nor whether you have the firewall and AppArmor disabled. Is there a hardware problem such as the cable and the NIC in the server? A Network Exception Error is usually symptomatic of a lost connection to the server. Have you moved this installation of Zimbra from one server to another? If you have, what steps did you use? Have you made any modification to Zimbra and if so, what are they?

If you're on a LAN, have you set-up a Split DNS

-Brand New Server
-Fresh Install of OpenSUSE and Zimbra (No migration invovled)
-AppArmor Disabled
-Sendmail removed
-Its on a LAN, Externally we have opened ports 25, 80, 110
-Split DNS IS Setup, Bind IS installed and working
-Only modification to zimbra was the png file for the 'splash' logo
-It's happend since we went live with it
-Problem is intermitting, doesnt always happen at the same time every night/morning
-Nothing indicates a loss of connection, as POP & SMTP work throughout the time that web mail does NOT
-This ONLY happens with the webmail interface, all other services work fine.
-Daily Mail Reports show "No messages found" even though theres 500+ users sending/recieving mail (possibly related?)


Output of requested commands:

cat /etc/hosts

127.0.0.1 localhost.localdomain localhost
192.168.220.100 mail.mydomain.com mail

cat /etc/resolv.conf

search mydomain.com
nameserver 192.168.220.100
nameserver 207.107.254.183
nameserver 204.50.251.253

dig mydomain.com mx

; <<>> DiG 9.3.2 <<>> mydomain.com mx
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44678
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1

;; QUESTION SECTION:
;mydomain.com.                    IN      MX

;; ANSWER SECTION:
mydomain.com.             86400   IN      MX      10 mail.mydomain.com.

;; AUTHORITY SECTION:
mydomain.com.             86400   IN      NS      mail.mydomain.com.

;; ADDITIONAL SECTION:
mail.mydomain.com.        86400   IN      A       192.168.220.100

;; Query time: 0 msec
;; SERVER: 192.168.220.100#53(192.168.220.100)
;; WHEN: Thu Mar 19 07:39:50 2009
;; MSG SIZE  rcvd: 79

dig mydomain.com any

; <<>> DiG 9.3.2 <<>> mydomain.com any
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42653
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; QUESTION SECTION:
;mydomain.com.                    IN      ANY

;; ANSWER SECTION:
mydomain.com.             86400   IN      SOA     mydomain.com. mail.mydomain.com. 42 172800 14400 3628800 604800
mydomain.com.             86400   IN      NS      mail.mydomain.com.
mydomain.com.             86400   IN      MX      10 mail.mydomain.com.
mydomain.com.             86400   IN      A       192.168.220.100

;; ADDITIONAL SECTION:
mail.mydomain.com.        86400   IN      A       192.168.220.100

;; Query time: 0 msec
;; SERVER: 192.168.220.100#53(192.168.220.100)
;; WHEN: Thu Mar 19 07:40:51 2009
;; MSG SIZE  rcvd: 131

host `hostname`

mail.mydomain.com has address 192.168.220.100

host -v mail.mydomain.com

Trying "mail.mydomain.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28455
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;mail.mydomain.com.               IN      A

;; ANSWER SECTION:
mail.mydomain.com.        86400   IN      A       192.168.220.100

;; AUTHORITY SECTION:
mydomain.com.             86400   IN      NS      mail.mydomain.com.

Received 63 bytes from 192.168.220.100#53 in 0 ms
Trying "mail.mydomain.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27801
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;mail.mydomain.com.               IN      AAAA

;; AUTHORITY SECTION:
mydomain.com.             86400   IN      SOA     mydomain.com. mail.mydomain.com. 42 172800 14400 3628800 604800

Received 69 bytes from 192.168.220.100#53 in 0 ms
Trying "mail.mydomain.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 827
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;mail.mydomain.com.               IN      MX

;; AUTHORITY SECTION:
mydomain.com.             86400   IN      SOA     mydomain.com. mail.mydomain.com. 42 172800 14400 3628800 604800

Received 69 bytes from 192.168.220.100#53 in 0 ms

-kernelklink