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 Gary Jarrel <ga...@gmail.com> on 2007/04/19 05:06:26 UTC
Mail Queues & Exceptions
Hi All
I'm quite new to James, and need to find a way to clear mail queues.
I.e. I've sent an email to James where the from address is part of a
non existent domain. The to address of this email was to a user who
did not exist on the James server but James was aware the the domain
of the to address was managed locally.
Now James is trying to bounce an email, using the from address, but is
of course getting DNS resolution problems.
So I need to remove this email from the queue and stop James from
retrying to deliver the email to an address which does not and will
never exist.
Another thing I've noted, is that if an exception is thrown from one
of my mailets, then it does not appear in the mailet logs, the
exception is silently swallowed with no hints to why the mailet
failed. Is this the expected behavior?
Thank you!
- gary
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: Mail Queues & Exceptions
Posted by Norman Maurer <no...@apache.org>.
Hi Gary,
Gary Jarrel schrieb:
> Hi All
>
> I'm quite new to James, and need to find a way to clear mail queues.
>
> I.e. I've sent an email to James where the from address is part of a
> non existent domain. The to address of this email was to a user who
> did not exist on the James server but James was aware the the domain
> of the to address was managed locally.
>
> Now James is trying to bounce an email, using the from address, but is
> of course getting DNS resolution problems.
>
> So I need to remove this email from the queue and stop James from
> retrying to deliver the email to an address which does not and will
> never exist.
If you use a DB as spool backend you can just connect to it and remove
the mail from spool table.
In james-trunk version we add jmx and remotemanager commands for such
purposes for every spool backend.
>
> Another thing I've noted, is that if an exception is thrown from one
> of my mailets, then it does not appear in the mailet logs, the
> exception is silently swallowed with no hints to why the mailet
> failed. Is this the expected behavior?
The mailet exception is logged in the spoolmanager-*.log. If you want to
log it in a the mailet log you have to catch the exception and "rethrow"
it.
Maybe this is usefull for you too:
http://wiki.apache.org/james/HandlingExceptions
>
> Thank you!
>
> - gary
bye
Norman
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org