Its true that James doesn't hang, rather it seems to prematurely abort, possibly because Netscape closes the connection. You can see that there are 594 messages in the queue, but after 'RETR 3' there is a reset and a stop. After further research I also realized that it isn't a specific message. I deleted emails day-by-day until Netscape was able to get through the remaining messages and pretty much had to delete everything until it could pop messages successfully. I may try adding back messages until it gets stuck to see if there is anything specific about the sequence.
What I don't understand is why Netscape was able to pop the same messages from my ISP successfully, but gets stuck popping from James.
I'm using James 2.1.2. It may be worth noting that I'm using the filesystem to store messages not the database.
Thanks
-J
Noel J. Bergman wrote:
Why is James returning "-ERR" after the XSENDER
Because XSENDER is not supported. The command itself is not without some controversy. As far as I know, it is a Netscape-specific command, which Qpopper (Eudora) and even Netscape recommend turning off.
http://www.eudora.com/qpopper/faq.html#netscape.auth http://www.geocrawler.com/mail/thread.php3?subject=xsender&list=126
For those who don't know, XSENDER "[gets] the email address of the sender of the specified message. Client uses this to query whether an individual message has been authenticated. Server returns an empty OK string if no authenticated sender is found."
ref: http://developer.netscape.com/docs/manuals/messaging/msdkj/prorj.htm
It would be possible to support it once we have mail attributes.
why does Netscape issue a UIDL and restart the process
Who knows.
More disturbing is this sequence:
Command received: DELE 1 Sent: +OK Message removed Command received: DELE 2 Sent: +OK Message removed Command received: UIDL Sent: +OK unique-id listing follows Command received: DELE 1 Sent: +OK Message removed Command received: DELE 2 Sent: +OK Message removed
Something is wrong with that sequence because the second set of deletes should have returned an -ERR response saying that the message was deleted. I just tested this using telnet:
RSET +OK LIST +OK 4 8314 1 3491 2 2911 3 956 4 956 . DELE 3 +OK Message removed LIST +OK 3 7358 1 3491 2 2911 4 956 . UIDL +OK unique-id listing follows 1 Mail1057948559166-4377 2 Mail1057948805540-4386 4 Mail1057949404326-4408 . DELE 3 -ERR Message (3) does not exist.
So that is working as expected. What verson of James are you using?
In any event, I don't see from your log extract where something is getting hung-up. James doesn't hang. Is Netscape misbehaving?
--- Noel
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
