Robert Burrell Donkin ha scritto:
> On 8/1/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
>> Never seen this error before in fetchmail.
>> What about that CRLF you have after the
>> "<[EMAIL PROTECTED]" ? Is it a copy and paste artifact or
>> is it really there?
>
> cut'n'paste
>
> the correct be
On 8/1/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
> Never seen this error before in fetchmail.
> What about that CRLF you have after the
> "<[EMAIL PROTECTED]" ? Is it a copy and paste artifact or
> is it really there?
cut'n'paste
the correct behaviour when fetchmail encounters a non-RFC822 m
Never seen this error before in fetchmail.
What about that CRLF you have after the
"<[EMAIL PROTECTED]" ? Is it a copy and paste artifact or
is it really there?
Stefano
Robert Burrell Donkin ha scritto:
> i'm seeing the same stack trace a few times a day (see bottom of
> message). from examining
i'm seeing the same stack trace a few times a day (see bottom of
message). from examining the code, i think that the input to the
mailaddress comes from a mimemessage.
am i mistaken in thinking that this really shouldn't fail?
- robert
01/08/07 08:55:34 WARN fetchmail.blueyonder.co.uk: Message
