Lee Hanxue wrote:
I have searched through the archive of the mailing list, but I could
not find the answer I need.
Basically, this is my fetchpop configuration:
mail.server.net
myusername
mypa
> -Original Message-
> From: Noel J. Bergman [mailto:[EMAIL PROTECTED]
> Sent: 18 August 2003 21:38
> To: James Users List
> Subject: RE: Using fetchmail
>
>
> > I downloaded the 2.2a9 release but it did not include the fetchmail.
>
> Steve Brewin is working on it now.
>
> --- Noel
P
> I downloaded the 2.2a9 release but it did not include the fetchmail.
Steve Brewin is working on it now.
--- Noel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
True, I realised this soon after posting. I have managed to create a
solution using the method I described earlier. Apart from standardising the
error message text, your suggestion is the only way I can see to improve on
it.
Craig
- Original Message -
From: "Noel J. Bergman" <[EMAIL PROT
Noel,
I downloaded the 2.2a9 release but it did not include the fetchmail.
When do you expect to have a first version wich does include fetchmail ?
Kind regards,
Herman
> Is it possible to use/implement fetchmail in the current james 2.1.3
environment ?
> If not, which version should I use to
I have searched through the archive of the mailing list, but I could not
find the answer I need.
Basically, this is my fetchpop configuration:
mail.server.net
myusername
mypassword
> I notice that the last line in service() on RemoteDelivery ghosts every
mail.
Think about it, Craig. RemoteDelivery doesn't do any synchronous
processing. Everything is queued, and may go through multiple attempted
deliveries. There is no information to attach during the service() method.
Wh
The "onMatchException" and "onMailetException" parameters have already been
implemented in v2.2. See
http://nagoya.apache.org/wiki/apachewiki.cgi?James/HandlingExceptions.
The causing exception is not available to other mailets. It could be easily attached
to the mail as a mail attribute, and m
Noel,
Thanks for your response. As a quickfix, I am going to try method 2 in my
original email, since it should be fairly easy to implement.
I will study RFC 1894 this week and see how it can be integrated.
On thinking about this again, I notice that the last line in service() on
RemoteDelivery
tobe,
Thanks for your ideas. Unfortunately, all the relevant methods in
RemoteDelivery are private, so I would have to reproduce virtually the
entire mailet. Your exception handling suggestion is possible, but as I see
it would require some pretty broad changes.
Not all mails end up in the error
10 matches
Mail list logo
