You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by Adam Raszkiewicz <ar...@medallies.com> on 2020/02/05 20:09:27 UTC
James and the queue problem
For some reason often I experience queue release issue when delivered message is always one behind actually sent.
Any thoughts on that?
Thanks,
~Adam
Re: James and the queue problem
Posted by Adam Raszkiewicz <ar...@medallies.com>.
I have set a mailet which sends matched messages (based on recipient domain) to the gateway (specified in the mailetcontainer).
That works fine till some point when it getting "stuck" to be delivered to the gateway. In the James logs it shows as `Successfully spooled mail` from the sender and then it shows as
[TID=83] INFO 11:04:54,858 | james.smtpserver | Id='1510412390' User='' Successfully spooled mail Mail1581005094857-978ba32f-74e6-4ca1-b903-7994637a9873 from <ad...@remote> on <remote sender IP> for [<ad...@local>]
...
[TID=734] INFO 11:04:55,290 | james.mailetcontext | Remotely delivering mail Mail1581005094857-978ba32f-74e6-4ca1-b903-7994637a9873
[TID=34] INFO 11:04:55,290 | james.mailetcontext | Remote delivery thread (0) will process mail Mail1581005072858-90055113-03cf-4bc0-84d7-d47d176feef2
[TID=34] INFO 11:04:55,290 | james.mailetcontext | Attempting to deliver Mail1581005072858-90055113-03cf-4bc0-84d7-d47d176feef2
[TID=734] INFO 11:04:55,312 | james.mailetcontext | Adding SMTP gateway: <gateway address>
[TID=734] INFO 11:04:55,312 | james.mailetcontext | Sending mail to [<ad...@local>] via [<gateway address>]
[TID=34] INFO 11:04:55,312 | james.mailetcontext | Adding SMTP gateway: <gateway adrdress>
[TID=34] INFO 11:04:55,312 | james.mailetcontext | Attempting delivery of Mail1581005072858-90055113-03cf-4bc0-84d7-d47d176feef2 to host <gateway adrdress> at <gateway adrdress> from <ad...@remote> for addresses [<ad...@local>]]
but I don't see that Mail was sent successful to the gateway.
To get it "unstuck" I need to have another incoming message to be send to the James which will hit the same mailet to push previous message to be spooled which got stuck before. Then in the James logs it will appear as
[TID=35] INFO 11:22:14,443 | james.mailetcontext | Mail (Mail1581005094857-978ba32f-74e6-4ca1-b903-7994637a9873) sent successfully to <gateway adrdress> at <gateway adrdress> from <ad...@remote> for [[<ad...@local>]]
All looks like if the relay host changes, the related queue can begin to behave differently, acting like a paper towel tube with ping pong balls pushed into one end. Only when enough balls have been pushed into get one out the other end.
Any thought on that?
On 2/6/20, 1:35 AM, "Tellier Benoit" <bt...@apache.org> wrote:
Sorry I don't understand your issue.
Can you better describe it?
On 06/02/2020 03:09, Adam Raszkiewicz wrote:
> For some reason often I experience queue release issue when delivered message is always one behind actually sent.
>
> Any thoughts on that?
>
> Thanks,
> ~Adam
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James and the queue problem
Posted by Tellier Benoit <bt...@apache.org>.
Sorry I don't understand your issue.
Can you better describe it?
On 06/02/2020 03:09, Adam Raszkiewicz wrote:
> For some reason often I experience queue release issue when delivered message is always one behind actually sent.
>
> Any thoughts on that?
>
> Thanks,
> ~Adam
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org