Sure, let's try to understand what happens. Can you supply more information (stacktrace, anonimized configuration files, environment, etc...) ?
Best regards, Benoit On 01/06/2020 15:57, Matt Pryor wrote: > Hi Benoit > > Thanks for the reply. I'm not too worried about the delivery errors as we > expect those, we are trying to get the owner of the domain to correct the > dns / spf record but they are slow. I'm more worried about how the delivery > thread appears to stop after a while until the server is rebooted and how > we can go about working out the cause of this. > > Matt > > > > > On Mon, 1 Jun 2020 at 03:59, Tellier Benoit <btell...@apache.org> wrote: > >> Hello Matt, >> >> Looking at the error messages you encounter: >> >> - 554 Response code from the target server. >> >> 554 error code means that the receiving server sees something in the >> From or To Headers of the message, that it doesn't like. This can be >> caused by a spam filter identifying your machine as a relay, or as a >> machine not trusted to send emails from your domain. >> >> - 550 Response code from the target server. >> >> The SMTP error code 550 means that the recipient of the email could not >> be reached. This code can come up for many reasons, including an >> incorrect email address. The 550 error "Relay Denied" means that the >> SMTP server did not recognize you as a valid sender. >> >> Coming from here: >> >> - Are you the one sending emails from securemessag...@quantrax.com ? >> - Have you been correctly doing the SMTP sending configuration? >> (reverse DNS, DKIM, SPF)? >> >> Then, your configuration is likely configured to perform 24 retires. >> >> After a reboot, do the Mail name (here >> Mail1589376585109-317cd0b6-3039-4ffd-95bf-329d1853537c-to-icloud.com, >> Mail1589376705624-d644f995-3323-40b0-a2da-db544fc91e69-to-comcast.net) >> are the same? >> >> Best regard, >> >> Benoit >> >> On 29/05/2020 19:11, Matt Pryor wrote: >>> Thanks Benoid. >>> Meanwhile, with regards to my other issue, having applied the log4j >> changes >>> suggested by David Matthews, I can see that after a period of time the >>> MailDelivrer stops running: >>> >>> DEBUG 11:34:43,410 | >>> org.apache.james.transport.mailets.remote.delivery.MailDelivrer | >> Exception >>> delivering message >>> (Mail1589376585109-317cd0b6-3039-4ffd-95bf-329d1853537c-to-icloud.com) - >>> Could not connect to SMTP host: 17.57.154.6, port: 25, response: 550 >>> DEBUG 11:34:43,410 | >>> org.apache.james.transport.mailets.remote.delivery.MailDelivrer | >> Temporary >>> exception delivering mail >>> (Mail1589376585109-317cd0b6-3039-4ffd-95bf-329d1853537c-to-icloud.com): >>> DEBUG 11:34:43,410 | >>> org.apache.james.transport.mailets.remote.delivery.DeliveryRunnable | >>> Storing message >>> Mail1589376585109-317cd0b6-3039-4ffd-95bf-329d1853537c-to-icloud.com >> into >>> outgoing after 24 retries >>> DEBUG 11:34:43,426 | >>> org.apache.james.transport.mailets.remote.delivery.DeliveryRunnable | >> will >>> process mail >>> Mail1589376705624-d644f995-3323-40b0-a2da-db544fc91e69-to-comcast.net >>> DEBUG 11:34:43,426 | >>> org.apache.james.transport.mailets.remote.delivery.MailDelivrerToHost | >>> Attempting delivery of >>> Mail1589376705624-d644f995-3323-40b0-a2da-db544fc91e69-to-comcast.net to >>> host mx1.comcast.net. at 96.114.157.80 from securemessag...@quantrax.com >>> DEBUG 11:34:43,535 | >>> org.apache.james.transport.mailets.remote.delivery.MailDelivrer | >> Exception >>> delivering message >>> (Mail1589376705624-d644f995-3323-40b0-a2da-db544fc91e69-to-comcast.net) >> - >>> Could not connect to SMTP host: 96.114.157.80, port: 25, response: 554 >>> DEBUG 11:34:43,535 | >>> org.apache.james.transport.mailets.remote.delivery.MailDelivrer | >> Temporary >>> exception delivering mail >>> (Mail1589376705624-d644f995-3323-40b0-a2da-db544fc91e69-to-comcast.net): >>> DEBUG 11:34:43,535 | >>> org.apache.james.transport.mailets.remote.delivery.DeliveryRunnable | >>> Storing message >>> Mail1589376705624-d644f995-3323-40b0-a2da-db544fc91e69-to-comcast.net >> into >>> outgoing after 24 retries >>> >>> 11:34 is the last line referencing that class, now 40 minutes later. I >>> don't know how to tell if the thread is still alive or if it's stuck >> doing >>> something. After a restart of the service it picks up again for a while >>> before stopping again. >>> >>> Any clues? >>> >>> Thanks >>> Matt >>> >>> >>> >>> >>> >>> >>> >>> >>> On Fri, 29 May 2020 at 03:26, Tellier Benoit <btell...@apache.org> >> wrote: >>> >>>> Hello Matt, >>>> >>>> On 28/05/2020 17:47, Matt Pryor wrote: >>>>> [...] >>>>> Is there a compiled >>>>> jar I could download with the fix or will I have to build it all myself >>>>> from source? >>>> >>>> If you are patient (~2 weeks) I can include this log enhancement in >>>> upcoming 3.5.0 release. >>>> >>>> Otherwise, you will have to compile it. >>>> >>>> Regards, >>>> >>>> Benoit >>>> >>>>> >>>>> Matt >>>>> >>>>> >>>>> On Thu, 28 May 2020 at 04:01, Tellier Benoit <btell...@apache.org> >>>> wrote: >>>>> >>>>>> >>>>>> >>>>>> On 27/05/2020 20:03, Matt Pryor wrote: >>>>>>> Hi there >>>>>>> >>>>>>> I am seeing this a lot in our wrapper log, we are using James 3.4.0. >>>>>>> >>>>>>> 0/05/27 12:50:43 | WARN 12:50:43,694 | >>>>>>> org.apache.james.queue.activemq.ActiveMQMailQueueItem | Unable to >>>> delete >>>>>>> blob message file for mail >>>>>>> Mail1590076890427-f333aa04-fd52-4fff-8538-de51963d52b7-to-gmail.com >>>>>>> INFO | jvm 1 | 202 >>>>>>> >>>>>>> It seems to continue to attempt to send the email as also getting >>>>>> recurring >>>>>>> DNS errors for invalid domains. >>>>>>> >>>>>>> Any suggestions on how to solve this? >>>>>>> >>>>>> >>>>>> I opened https://issues.apache.org/jira/browse/JAMES-3195 related to >>>>>> your issue. >>>>>> >>>>>> The first thing is that the stacktrace is lost, thus we miss this >>>>>> valuable debugging information. >>>>>> >>>>>> https://github.com/linagora/james-project/pull/3401 is an attempt to >>>>>> solve it. >>>>>> >>>>>> Now what could happen: >>>>>> >>>>>> - The URL attached to your messages is malformed >>>>>> - The given files do not exist, are already deleted. >>>>>> >>>>>> From there: >>>>>> >>>>>> - Do you notice some functional problems? (are some mails dropped) >>>>>> - What is the file usage of the mailqueue in /var ? (du -h -d 2 >>>>>> $james/var ?) >>>>>> >>>>>> Best regards, >>>>>> >>>>>> Benoit >>>>>> >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org >>>>>> For additional commands, e-mail: server-user-h...@james.apache.org >>>>>> >>>>>> >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org >>>> For additional commands, e-mail: server-user-h...@james.apache.org >>>> >>>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org >> For additional commands, e-mail: server-user-h...@james.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
