Re: POP3 TLS AUTH too long

Janne Pikkarainen <[email protected]>
Newsgroups gmane.mail.perdition.user
Message-ID <[email protected]>
Hello,

On 12/22/2009 05:41 PM, Dominique Marant wrote:
> Hi,
>
> With POP3 TLS, the time to retrieve mail is too long.
>
> In debugging and connection logging, I see that perdition is waiting 3
> seconds to send the response to AUTH request :

Three seconds sounds like a DNS timeout for me. Is DNS working properly? :)

Best regards,

Janne Pikkarainen


>
> Dec 22 15:54:06 logua2 perdition[23793]: SELF:
> "UIDL\r\nUSER\r\nSTLS\r\n.\r\n"
> Dec 22 15:54:06 logua2 perdition[23793]: CLIENT: "STLS\r\n"
> Dec 22 15:54:06 logua2 perdition[23793]: SELF: "+OK Begin TLS
> negotiation, mate\r\n"
> Dec 22 15:54:07 logua2 perdition[23793]: SSL connection using AES256-SHA
> Dec 22 *15:54:07* logua2 perdition[23793]: CLIENT: "AUTH\r\n"
> Dec 22 *15:54:10* logua2 perdition[23793]: SELF: "-ERR Mate, the command
> must be one of CAPA, USER, PASS or QUIT\r\n"
> Dec 22 15:54:10 logua2 perdition[23793]: CLIENT: "CAPA\r\n"
> Dec 22 15:54:10 logua2 perdition[23793]: SELF: "+OK Capability list
> follows, mate\r\n"
> Dec 22 15:54:10 logua2 perdition[23793]: SELF: "UIDL\r\nUSER\r\n.\r\n"
>
> 3 secondes between CLIENT AUTH and the -ERR response of perdition...
> It's too long for the users (for example, Thunderbird with TLS).
>
> I'm tracing the process (strace) and I see a nanosleep 3 for a child
> process.
>
> In the source and include perdition, I see :
> #define PERDITION_AUTH_FAIL_SLEEP 3
> sleep(PERDITION_AUTH_FAIL_SLEEP);
>
> Is there a bad effect to put 0 value to this define ?
>
> Thanks
> Dominique
>
>
>
>
>
>
>
> ______________________________________________
> Perdition-users mailing list
> [email protected]
> http://lists.vergenet.net/listinfo/perdition-users

______________________________________________
Perdition-users mailing list
[email protected]
http://lists.vergenet.net/listinfo/perdition-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.