Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Administrators
Reload this Page Email sometimes goes first time, other times it doesn't

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
Page 1 of 4 1 23
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 06-22-2010, 01:16 AM
Senior Member
  
Posts: 66
Default Email sometimes goes first time, other times it doesn't
Hi All

This is a desperate plea just in case someone else has found a fix for this..

I have just updated to 6.0.7 hoping it would have eliminated my problem but it hasn't.

For a few days now, using the web client, I get this when trying to send a message to either an internal or external recipient..

Code:
method:	SendMsgRequest
msg:	Invalid address: Paul Roberts . com.zimbra.cs.mailbox.MailSender$SafeSendFailedException: Invalid Addresses; chained exception is: com.sun.mail.smtp.SMTPAddressFailedException: 550 5.7.1 Unable to relay for paul.roberts@anheddau.co.uk
code:	mail.SEND_ABORTED_ADDRESS_FAILURE
detail:	soap:Sender
trace:	com.zimbra.cs.mailbox.MailServiceException: Invalid address: Paul Roberts . com.zimbra.cs.mailbox.MailSender$SafeSendFailedException: Invalid Addresses; chained exception is: com.sun.mail.smtp.SMTPAddressFailedException: 550 5.7.1 Unable to relay for paul.roberts@anheddau.co.uk ExceptionId:btpool0-17://smtp.anheddau.co.uk/service/soap/SendMsgRequest:1277193146761:a7037a84334a3cec Code:mail.SEND_ABORTED_ADDRESS_FAILURE Arg:(invalid, STR, "Paul Roberts ") at com.zimbra.cs.mailbox.MailServiceException.internal_SEND_FAILURE(MailServiceException.java:455) at com.zimbra.cs.mailbox.MailServiceException.SEND_ABORTED_ADDRESS_FAILURE(MailServiceException.java:459) at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:462) at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:309) at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:266) at com.zimbra.cs.service.mail.SendMsg.doSendMessage(SendMsg.java:189) at com.zimbra.cs.service.mail.SendMsg.handle(SendMsg.java:150) at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:420) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:274) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:158) at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:291) at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:212) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:181) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166) at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(SetHeaderFilter.java:79) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81) at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:132) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.handler.DebugHandler.handle(DebugHandler.java:77) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:543) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:939) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451) Caused by: com.zimbra.cs.mailbox.MailSender$SafeSendFailedException: Invalid Addresses; chained exception is: com.sun.mail.smtp.SMTPAddressFailedException: 550 5.7.1 Unable to relay for paul.roberts@anheddau.co.uk at com.sun.mail.smtp.SMTPTransport.rcptTo(SMTPTransport.java:1446) at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:736) at com.zimbra.cs.mailbox.MailSender.sendMessageToHost(MailSender.java:780) at com.zimbra.cs.mailbox.MailSender.sendMessage(MailSender.java:700) at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:412) ... 39 more
request:	

Body: {
  SendMsgRequest: {
    _jsns: "urn:zimbraMail",
    m: {
      e: [
        0: {
          a: "paul.roberts@anheddau.co.uk",
          p: "Paul Roberts",
          t: "t"
         },
        1: {
          a: "ifan@anheddau.co.uk",
          p: "Ifan Jones",
          t: "f"
         }
       ],
      idnt: "fbc1c8c7-22de-47df-85f8-4842690ef1e6",
      mp: [
        0: {
          ct: "multipart/alternative",
          mp: [
            0: {
              content: {
                _content: "

-- 
Ifan Jones 
Assistant Head of Employee Resourcing - Office Manager 

Ffôn / Telephone - 01248 675 910 
Symudol / Mobile - 07799 603779 
Ffacs / Fax - 01248 670 280 
E-Bost / E-Mail - ifan@anheddau.co.uk 
Wefán / Website - www.anheddau.co.uk 
Cyfeiriad post / Postal address - Anheddau Cyf, 6 Llys Britannia, Parc Menai, Bangor, Gwynedd, LL57 4BN 
Mae Anheddau Cyf yn gwmni Cyfyngedig dan Warant rhif 2380151 ac yn Elusen Gofrestredig rhif 701697 
Anheddau Cyf. is a Company Limited by Guarantee number 2380151 and a Registered Charity number 701697 

Nodyn Diarddel / Disclaimer - http://www.anheddau.co.uk/disclaimer.htm 
"
               },
              ct: "text/plain"
             },
            1: {
              content: {
                _content: "<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Arial; font-size: 12pt; color: #000000'><span><br><br>-- <br><span name="x"></span>Ifan Jones<br>Assistant Head of Employee Resourcing - Office Manager<br><br>Ffôn / Telephone - 01248 675 910<br>Symudol / Mobile - 07799 603779<br>Ffacs / Fax - 01248 670 280<br>E-Bost / E-Mail - ifan@anheddau.co.uk<br>Wefán / Website - www.anheddau.co.uk<br>Cyfeiriad post / Postal address - Anheddau Cyf, 6 Llys Britannia, Parc Menai, Bangor, Gwynedd, LL57 4BN<br>Mae Anheddau Cyf yn gwmni Cyfyngedig dan Warant rhif 2380151 ac yn Elusen Gofrestredig rhif 701697<br>Anheddau Cyf. is a Company Limited by Guarantee number 2380151 and a Registered Charity number 701697<br><br>Nodyn Diarddel / Disclaimer - http://www.anheddau.co.uk/disclaimer.htm<span name="x"></span><br></span></div></body></html>"
               },
              ct: "text/html"
             }
           ]
         }
       ],
      su: {
        _content: "asdfasdf"
       }
     },
    suid: 1277194067858
   }
 },
Header: {
  context: {
    _jsns: "urn:zimbra",
    account: {
      _content: "ifan@anheddau.co.uk",
      by: "name"
     },
    authToken: "(removed)",
    notify: {
      seq: 6
     },
    session: {
      _content: 1176,
      id: 1176
     },
    userAgent: {
      name: "ZimbraWebClient - FF3.0 (Win)",
      version: "6.0.7_GA_2473.RHEL5"
     }
   }
 }
Now if we click OK and then click Send again, the message goes and is delivered as expected.

While tailing /var/log/zimbra.log when this happens, postfix hasn't even complained.

A few days before this started happening I upgraded our firewall from Endian 2.3 to Endian 2.4

I do suspect something with DNS but this box has been fine for over twelve montsh now.

I'm just hoping someone else has the same setup and issues so we can share information and hopefully a fix!

Or if anyone here can decipher that SOAP message and point me in the irght direction it would be greatly appreciated :-)
Reply With Quote
  #2 (permalink)  
Old 06-22-2010, 01:25 AM
Zimbra Consultant & Moderator
  
Posts: 20,313
Default
Is the DNS server on the Zimbra server or elsewhere in your LAN and is this a single server or what? My inclination would be an intermittent problem with either DNS or perhaps your NIC. What has EFW got to do with this? Aren't your Zimbra & DNS servers behind EFW?

Just for confirmation you might as well post the output of the following commands:
Code:
cat /etc/resolv.conf
cat /etc/hosts
dig yourdomain.com mx
dig yourdomain.com any
host `hostname` <- use that exact command with backticks not single quotes
__________________
Regards


Bill
Reply With Quote
  #3 (permalink)  
Old 06-22-2010, 01:42 AM
Senior Member
  
Posts: 66
Default
The EFW box handles our DNS

EFW IP 192.168.14.5
Zimbra IP 192.168.14.11

Zimbra box setup with Split DNS

This problem does not happen when using a client such as Thuderbird or Outlook, or it looks like it doesn't happen. It appears more like an issue with the web client - but I am now clutching at straws!

Code:
cat /etc/resolv.conf
search anheddau.co.uk
nameserver 192.168.14.11
Code:
[zimbra@smtp ~]$ dig anheddau.co.uk mx

; <<>> DiG 9.3.4-P1 <<>> anheddau.co.uk mx
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39481
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3

;; QUESTION SECTION:
;anheddau.co.uk.                        IN      MX

;; ANSWER SECTION:
anheddau.co.uk.         31418   IN      MX      10 smtp.anheddau.co.uk.

;; AUTHORITY SECTION:
anheddau.co.uk.         5867    IN      NS      ns1.wiss.co.uk.
anheddau.co.uk.         5867    IN      NS      ns0.wiss.co.uk.

;; ADDITIONAL SECTION:
smtp.anheddau.co.uk.    2592000 IN      A       192.168.14.11
ns0.wiss.co.uk.         31423   IN      A       213.210.8.50
ns1.wiss.co.uk.         31423   IN      A       217.33.230.74

;; Query time: 21 msec
;; SERVER: 192.168.14.11#53(192.168.14.11)
;; WHEN: Tue Jun 22 09:21:18 2010
;; MSG SIZE  rcvd: 142
Code:
[zimbra@smtp ~]$ dig anheddau.co.uk any

; <<>> DiG 9.3.4-P1 <<>> anheddau.co.uk any
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53869
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 2, ADDITIONAL: 3

;; QUESTION SECTION:
;anheddau.co.uk.                        IN      ANY

;; ANSWER SECTION:
anheddau.co.uk.         31119   IN      MX      10 smtp.anheddau.co.uk.
anheddau.co.uk.         5568    IN      NS      ns0.wiss.co.uk.
anheddau.co.uk.         5568    IN      NS      ns1.wiss.co.uk.
anheddau.co.uk.         38443   IN      A       213.210.8.60

;; AUTHORITY SECTION:
anheddau.co.uk.         5568    IN      NS      ns1.wiss.co.uk.
anheddau.co.uk.         5568    IN      NS      ns0.wiss.co.uk.

;; ADDITIONAL SECTION:
smtp.anheddau.co.uk.    2592000 IN      A       192.168.14.11
ns0.wiss.co.uk.         31124   IN      A       213.210.8.50
ns1.wiss.co.uk.         31124   IN      A       217.33.230.74

;; Query time: 1 msec
;; SERVER: 192.168.14.11#53(192.168.14.11)
;; WHEN: Tue Jun 22 09:26:17 2010
;; MSG SIZE  rcvd: 186
Code:
[zimbra@smtp ~]$ host `hostname`
smtp.anheddau.co.uk has address 192.168.14.11
smtp.anheddau.co.uk mail is handled by 10 smtp.anheddau.co.uk.
Reply With Quote
  #4 (permalink)  
Old 06-22-2010, 01:53 AM
Zimbra Consultant & Moderator
  
Posts: 20,313
Default
Quote:
Originally Posted by RevDarkman View Post
The EFW box handles our DNS
Do you mean it's acting as a DNS relay for your LAN?

The other information you've posted seems OK but you missed the hosts file, could you post that as well? Is there anything else running on this server? Is it a single server? How much RAM does it have? Have you monitored the server performance during the period you've had this problem? Have you done any updates to CentOS recently that might have caused any problems? Is Zimbra on a HD that's local to the server or and a SAN or network mount?
__________________
Regards


Bill
Reply With Quote
  #5 (permalink)  
Old 06-22-2010, 02:08 AM
Senior Member
  
Posts: 66
Default
Yes the EFW relays DNS for the LAN

Code:
[zimbra@smtp ~]$ cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1               localhost.localdomain localhost
::1             localhost6.localdomain6 localhost6
192.168.14.11   smtp.anheddau.co.uk smtp
The Zimbra box also handles Samba, there's no integration between that and Zimbra.

The server itself has 2GB RAM and is a Dell Poweredge T605

There's two SATA disks in there with a single logical 280GB drive with 106GB available.

When monitoring cpu/memory usage with 'top' cpu% reaches 10% when an email is sent (amavisd) and java hits 21% memory. When the error sending appears, there's nothing out of the ordinary there. It's as if the web client can't 'see' the rest of the system.

There have been no updates to CentOS (if it ain't broke don't fix it!)
Reply With Quote
  #6 (permalink)  
Old 06-22-2010, 02:14 AM
Zimbra Consultant & Moderator
  
Posts: 20,313
Default
Quote:
Originally Posted by RevDarkman View Post
The Zimbra box also handles Samba, there's no integration between that and Zimbra.
Do you mean it's a file server?

Again, there's nothing out of the ordinary in your replies that would lead me to think anything is wrong with ZImbra.
__________________
Regards


Bill
Reply With Quote
  #7 (permalink)  
Old 06-22-2010, 02:20 AM
Senior Member
  
Posts: 66
Default
Yes Samba is the fileserver/domain controller.

I too am at a loss, but I may check out the NIC and cables later today - as I also need to install an additional switch.

I have to admit I suspect it's the EFW box rather than Zimbra, I just can't figure it out yet.

Thanks for your help :-)
Reply With Quote
  #8 (permalink)  
Old 06-22-2010, 02:24 AM
Senior Member
  
Posts: 66
Default
Just to add a different error.

Sometimes when sending a read recipt we get this....

Code:
method:	SendDeliveryReportRequest
msg:	system failure: error while sending read receipt
code:	service.FAILURE
detail:	soap:Receiver
trace:	com.zimbra.common.service.ServiceException: system failure: error while sending read receipt ExceptionId:btpool0-48://smtp.anheddau.co.uk/service/soap/SendDeliveryReportRequest:1277197703136:a7037a84334a3cec Code:service.FAILURE at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:248) at com.zimbra.cs.service.mail.SendDeliveryReport.sendReport(SendDeliveryReport.java:136) at com.zimbra.cs.service.mail.SendDeliveryReport.handle(SendDeliveryReport.java:70) at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:420) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:274) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:158) at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:291) at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:212) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:181) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166) at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(SetHeaderFilter.java:79) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81) at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:132) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.handler.DebugHandler.handle(DebugHandler.java:77) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:543) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:939) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451) Caused by: javax.mail.SendFailedException: Invalid Addresses; nested exception is: com.sun.mail.smtp.SMTPAddressFailedException: 550 5.7.1 Unable to relay for nia@anheddau.co.uk at com.sun.mail.smtp.SMTPTransport.rcptTo(SMTPTransport.java:1446) at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:736) at javax.mail.Transport.send0(Transport.java:191) at javax.mail.Transport.send(Transport.java:120) at com.zimbra.cs.service.mail.SendDeliveryReport.sendReport(SendDeliveryReport.java:134) ... 36 more Caused by: com.sun.mail.smtp.SMTPAddressFailedException: 550 5.7.1 Unable to relay for nia@anheddau.co.uk at com.sun.mail.smtp.SMTPTransport.rcptTo(SMTPTransport.java:1297) ... 40 more
request:	

Body: {
  SendDeliveryReportRequest: {
    _jsns: "urn:zimbraMail",
    mid: "26337"
   }
 },
Header: {
  context: {
    _jsns: "urn:zimbra",
    account: {
      _content: "ifan@anheddau.co.uk",
      by: "name"
     },
    authToken: "(removed)",
    notify: {
      seq: 33
     },
    session: {
      _content: 1176,
      id: 1176
     },
    userAgent: {
      name: "ZimbraWebClient - FF3.0 (Win)",
      version: "6.0.7_GA_2473.RHEL5"
     }
   }
 }
may shed some more light on the matter....
Reply With Quote
  #9 (permalink)  
Old 06-22-2010, 02:26 AM
Zimbra Consultant & Moderator
  
Posts: 20,313
Default
Quote:
Originally Posted by RevDarkman View Post
Yes Samba is the fileserver/domain controller.
Is it likely that the server is overloaded at the time you get the sending problem? There have been some recent updates (on CentOS 5.5) to Samba but I haven't had a chance to check out what they are.

Obviously this problem isn't reproducible but is it frequent and is it for one specific user? Is it possible the problem is at the user end?

As your EFW is just a DNS proxy I can't imagine why that would be a problem for the Zimbra server.
__________________
Regards


Bill
Last edited by phoenix; 06-22-2010 at 02:39 AM..
Reply With Quote
  #10 (permalink)  
Old 06-22-2010, 02:33 AM
Senior Member
  
Posts: 66
Default
There's no obvious overload but will monitor further today.

I have tested with IE and Firefox, even Chrome and it is all quite random.

I'll update here with any findings....
Reply With Quote
Reply
Page 1 of 4 1 23

« 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.