Fetchmail Problems

[Norman Maurer <no...@apache.org>]

Hi all,

I just finished my first install of JAMES with using fetchmail and have
some problems. Here are the problems:

1. We tried to fetch emails via POP3 from a Exchange 2003 server which
are sent from one local exchange account to an other local exchange
account. Fetchmail stopped parsing the message because the ip is missing
in the received header of the emails. Even if i use -1 as index the same
happen. That seems to be a bug for me .. Should it not just use
"127.0.0.1" and not try to parse it ? After adding a workarround which
catch the UnknownHostexception and add "127.0.0.1" this is solved.

2. We have an email in the remote POP3 server which seems to not be RFC
conform ( who wonder ..its microsoft :-P).. But james just stop
processing after that message is found.. Thats not acceptable for me.
James should just "ignore" this message and proccess. I just see this in
the error:

"A MessagingException has terminated fetching messages for this folder",

For me it seems that the exception get thrown when try to get the
Message of the folder (FolderProcessor.java:90) :

                for (int i = 1; i <= messageCount; i++)
                {
                    MimeMessage message =
                        (MimeMessage) getFolder().getMessage(i);

Whould it not make more sense to catch this in the for loop and process ?

bye
Norman


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

Re: Fetchmail Problems

[Norman Maurer <no...@apache.org>]

Danny Angus schrieb:
> On 4/17/07, Norman Maurer <no...@apache.org> wrote:
>
>
>> 1. We tried to fetch emails via POP3 from a Exchange 2003 server which
>> Should it not just use
>> "127.0.0.1" and not try to parse it ?
>
> Depends upon whether or not doing that would provide a "cloak" for
> spam. I suppose you could.

Maybe we should make it configurable ? But for me its not clear from the
config explaination that it will fail on such messages.
BTW, non RFC-conform messages are unfortanally not  only created by 
spammers. Often its created by well known commercial products. So why
not just fetch it and take care about this in the mailet chain ?

>
>> 2.
> ... Thats not acceptable for me.
>> James should just "ignore" this message and proccess.
>
> I agree 100% I think I put (and fixed) this bug in the original fetchpop.

Can you check if the fix is aviable in fetchmail too ? Maybe you can
point me to the original bug ?


>
> d.

bye
Norman


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

Re: Fetchmail Problems

[Danny Angus <da...@apache.org>]

On 4/17/07, Norman Maurer <no...@apache.org> wrote:


> 1. We tried to fetch emails via POP3 from a Exchange 2003 server which
> Should it not just use
> "127.0.0.1" and not try to parse it ?

Depends upon whether or not doing that would provide a "cloak" for
spam. I suppose you could.

> 2.
... Thats not acceptable for me.
> James should just "ignore" this message and proccess.

I agree 100% I think I put (and fixed) this bug in the original fetchpop.

d.

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org