Page 3 of 3 FirstFirst 123
Results 21 to 24 of 24

Thread: Delivery Failure Notification

  1. #21
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  2. #22
    Join Date
    Dec 2011
    Posts
    30
    Rep Power
    3

    Default

    Thanks, I've already read that and know where the log files are, I was specifically referring to which logs should I be looking at?
    For every expert, there is an equal and opposite expert - Arthur C Clarke's Fourth Law

  3. #23
    Join Date
    Nov 2008
    Location
    Grand Rapids, MI
    Posts
    123
    Rep Power
    7

    Default

    /var/log/zimbra.log is most likely to have information about email delivery problems. /opt/zimbra/log/mailbox.log might, also, depending at what point in the chain the error occurs.

  4. #24
    Join Date
    Dec 2011
    Posts
    30
    Rep Power
    3

    Default

    Quote Originally Posted by justdave View Post
    /var/log/zimbra.log is most likely to have information about email delivery problems. /opt/zimbra/log/mailbox.log might, also, depending at what point in the chain the error occurs.
    Thanks Dave, that helps.

    I'll have to wait for it to happen again. It happened on 5/11 at 6:09am then again at 6:10. I have the mailbox.log from then that shows the failure, I'll paste that below, hopefully one of you that knows Zimbra better can find something that makes sense in it.

    The zimbra.log from the same time frame doesn't appear to be there. The log archives show zimbra.log.4.gz belonging to 5/10 and zimbra.log.3.gz belonging to 5/12, but nothing for 5/11. Not sure what that's about. I pulled both of those and zimbra.log.4.gz goes from 5/9 at 6:46 to 5/10 at 6:53, and zimbra.log.3.gz starts 5/11 at 6:43 (about 1/2 hr after the failure). I'll make it a point to grab both of these logs next time it happens.

    Wait a sec, I think I may have found something, I'm not sure why it did it though. This Zimbra server actually hosts 4 domains, and it looks like it sent to the wrong MTA. Why would it send to the wrong MTA? The other failure was similar in that in also went to the wrong MTA, it just went to a different/wrong MTA that is also hosted on this server. What's up with that?

    Here's what I saw in the mailbox.log, note that I got two failures before it sent, this is the first of the two. The other shows the same thing, just with the other MTA name there.
    Code:
    2012-05-11 06:09:13,043 INFO  [btpool0-2351://mail.mydomain.com/service/upload?fmt=raw] [name=me@mydomain.com;mid=4;ip=192.168.2.201;ua=Jakarta Commons-HttpClient/3.1;] FileUploadServlet - Received plain: Upload: { accountId=40315ff5-b225-4458-b934-645f12c53cc0, time=Fri May 11 06:09:13 PDT 2012, size=2424, uploadId=81fa415c-752b-4daf-957b-e4340381323a:1223b494-8b47-4f3e-a074-05ee2fae88ce, name=msg-1073742347, path=null }
    2012-05-11 06:09:13,059 INFO  [btpool0-2351://mail.mydomain.com/service/soap/SendMsgRequest] [name=me@mydomain.com;mid=4;ip=192.168.2.201;ua=Zimbra Desktop/7.1.4_11299_Windows;] soap - SendMsgRequest
    2012-05-11 06:09:13,072 INFO  [btpool0-2351://mail.mydomain.com/service/soap/SendMsgRequest] [name=me@mydomain.com;mid=4;ip=192.168.2.201;ua=Zimbra Desktop/7.1.4_11299_Windows;] mailop - Adding Message: id=34256, Message-ID=<7390836.414.1336741781882.JavaMail.mycomputerusername@mycomputermachinename>, parentId=-1, folderId=5, folderName=Sent.
    2012-05-11 06:09:13,102 INFO  [btpool0-2351://mail.mydomain.com/service/soap/SendMsgRequest] [name=me@mydomain.com;mid=4;ip=192.168.2.201;ua=Zimbra Desktop/7.1.4_11299_Windows;] smtp - Sending message to MTA at mail.myotherdomain1.com: Message-ID=<7390836.414.1336741781882.JavaMail.mycomputerusername@mycomputermachinename>, origMsgId=40315ff5-b225-4458-b934-645f12c53cc0:34113, uploads=[Upload: { accountId=40315ff5-b225-4458-b934-645f12c53cc0, time=Fri May 11 06:09:13 PDT 2012, size=2424, uploadId=81fa415c-752b-4daf-957b-e4340381323a:1223b494-8b47-4f3e-a074-05ee2fae88ce, name=msg-1073742347, path=null }], replyType=r
    2012-05-11 06:09:13,133 WARN  [btpool0-2351://mail.mydomain.com/service/soap/SendMsgRequest] [name=me@mydomain.com;mid=4;ip=192.168.2.201;ua=Zimbra Desktop/7.1.4_11299_Windows;] smtp - Failed to send message
    com.zimbra.cs.mailclient.smtp.InvalidRecipientException: RCPT failed: Invalid recipient myparents@theirdomain.net: 554 5.7.1 <myparents@theirdomain.net>: Relay access denied
    	at com.zimbra.cs.mailclient.smtp.SmtpConnection.rcpt(SmtpConnection.java:622)
    	at com.zimbra.cs.mailclient.smtp.SmtpConnection.sendInternal(SmtpConnection.java:515)
    	at com.zimbra.cs.mailclient.smtp.SmtpConnection.sendMessage(SmtpConnection.java:481)
    	at com.zimbra.cs.mailclient.smtp.SmtpConnection.sendMessage(SmtpConnection.java:464)
    	at com.zimbra.cs.mailclient.smtp.SmtpTransport.sendMessage(SmtpTransport.java:212)
    	at com.zimbra.cs.mailbox.MailSender.sendMessageToHost(MailSender.java:899)
    	at com.zimbra.cs.mailbox.MailSender.sendMessage(MailSender.java:831)
    	at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:565)
    	at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:425)
    	at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:385)
    	at com.zimbra.cs.service.mail.SendMsg.doSendMessage(SendMsg.java:193)
    	at com.zimbra.cs.service.mail.SendMsg.handle(SendMsg.java:154)
    	at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:412)
    	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:287)
    	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:158)
    	at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:294)
    	at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:215)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
    	at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:208)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:814)
    	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:155)
    	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:218)
    	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:422)
    	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:946)
    	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756)
    	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:410)
    	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
    For every expert, there is an equal and opposite expert - Arthur C Clarke's Fourth Law

Similar Threads

  1. Receiving failure delivery messages.
    By pradip in forum Administrators
    Replies: 3
    Last Post: 12-10-2011, 03:32 AM
  2. Replies: 1
    Last Post: 04-22-2011, 05:44 AM
  3. Replies: 0
    Last Post: 02-25-2011, 04:05 AM
  4. No notification of mail failure
    By Marc Wilson in forum Administrators
    Replies: 6
    Last Post: 02-04-2011, 07:01 AM
  5. Temporary message delivery failure
    By goetzi in forum Administrators
    Replies: 40
    Last Post: 06-25-2007, 11:41 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •