Image 01
profile-image

drbytes

Dr bytes , Netherlands
ImapQuickCheck

Email by tonypizza 42 comments

Seems i was premature with my comments. It was not the euro sign in the message wich caused the problem. I thought it was because that was the only char in the email subject i could see but in fact it was a control char (char 128) which caused the error. I now use this code in the function htmlentities:
if ord(c) in codepoint2name:
result.append('&%s;' % codepoint2name[ord(c)])

(left out the else part from my previous comment) so no 'strange' chars get included.

I'm not sure now if the code really should be changed since the email seemed to be malformed. It also had no date in the header and that caused problems aswell in the python code (I changed that also to return 01-01-1970 if there is no date). But simply marking the message as 'read' solved all problems in the unmodified ImapQuickCheck.

Sorry for any trouble i may have caused.....

Tom - Dec 01 2010
ImapQuickCheck

Email by tonypizza 42 comments

Compiled it from the source now too with the new python code:) - Nov 30 2010
ImapQuickCheck

Email by tonypizza 42 comments

Ok, found the python file and also found the bug:

in one of my mails the subject includes the Euro sign "€". This gets translated to an HTML entity with codepoint2name in the htmlentities function. For the Euro sign there is no translation and a key exeception occurs in codepoint2name[ord(c)]
The "Fetch" error message gets displayed because that is the only error message in the " RETRIEVE UNSEEN MESSAGES DETAILS " code but the retreiving is actualy ok.

A solution is to replace this line (in htmlentities):
result.append('&%s;' % codepoint2name[ord(c)])
with this code:
if ord(c) in codepoint2name:
result.append('&%s;' % codepoint2name[ord(c)])
else:
result.append(c)

This works for me. I tried all this from the console by just executing the edited pyhon file. I did not try to recompile ImapQuickCheck with this file since i dont know how to do that. Have to find that out yet.

Regards,

Tom
- Nov 30 2010
ImapQuickCheck

Email by tonypizza 42 comments

Thanks for your quick reply:)

I am using a local (on my wired network) imap server with Dovecot v1.2.9 and i am accessing the accounts through SSL. The server does seem to be working ok since i can access the mail on the server with my mailreader (also through ssl) and my other ImapQuickCheck account accessing the same server is also working as expected.

In the imap-server logs i can see that indeed the login and logout is working but i do not get any errors or warnings about accessing the mail. The logs look the same for the working account and the account with the error message.

Is the pythoncode you are using open source? Maybe i can look into it and see what is going on. I will try some other settings to see if it helps. If i find the solution (or it starts working again magicly :) ) i'll post a message.

Regards, Tom - Nov 30 2010
ImapQuickCheck

Email by tonypizza 42 comments

Hi,

Thanks for this wonderfull mailchecker. I'm using it over 6 months now and it does the job quite well. However since yesterday i see this error message: "communication problem [fetch]" with one of my accounts in imapQuickCheck. I did not change anything and also i can still access the account with my mailreader and read my mail. Only ImapQuickCheck seems to have a problem accessing the mail. I tried cleaning up the mailbox but that did not help and i also tried making a new account in ImapQuickCheck which also did not help. I do have another account in ImapQuickCheck on the same imap-server with same settings (except accountname and password) and that one is working like a charm, i do not see the error there.

my version of imapQuickCheck: v1.3

Do you have any idea how i solve this?

Thank you,

Tom - Nov 30 2010
5.7
Nov 30 2010