Re: pop3s to gmail connection problem

On Tue, May 17, 2011 at 07:35:26PM +0200, singodiwirjo, hermantino wrote:
> Hi,
> 
> I need to deploy perdition to allow a user to get pop3 access to his Gmail account.
> 
> >From the machine that hosts perdition I can connect to Gmail server without problems :
> 
> # openssl s_client -connect pop.gmail.com:995
> [..]
> +OK Gpop ready for requests from 80.169.130.254 s9pf17928550wby.23
> user my_user
> +OK send PASS
> pass my_pass
> +OK Welcome.
> 
> LIST works etc ..
> 
> Then here are my perdition config files :
> 
> /etc/sysconfig/perdition:
> RUN_PERDITION=yes
> POP3=no
> POP3S=yes
> IMAP4=no
> IMAP4S=no
> MANAGESIEVE=yes
> 
> /etc/perdition/perdition.conf :
> protocol POP3S
> outgoing_port 995
> outgoing_server pop.gmail.com
> ssl_mode ssl_listen
> 
> #managesieve_capability \
> "\"IMPLEMENTATION\" \"perdition\"  "\
> "\"SIEVE\" \"comparator-i;octet "\
> "comparator-i;ascii-casemap "\
> "fileinto "\
> "reject "\
> "envelope "\
> "encoded-character "\
> "vacation "\
> "subaddress "\
> "comparator-i;ascii-numeric "\
> "relational "\
> "regex "\
> "imap4flags "\
> "copy i"\
> "nclude "\
> "variables "\
> "body "\
> "enotify "\
> "environment "\
> "mailbox "\
> "date\"  "\
> "\"SASL\" \"PLAIN\"  "\
> "\"NOTIFY\" \"mailto\"  "\
> "\"VERSION\" \"1.18\""
> 
> To get maximum debug info I launch :
> #perdition.pop3s --debug --connection_logging
> 
> When trying to connect localhost :
> # openssl s_client -connect pop.gmail.com:995
> 
> I can send the user and pass, in my logs I got:
> [..]
> May 17 17:00:03 vk2-prx01 perdition.pop3s[21176]: Connect:  127.0.0.1:56037->127.0.0.1:995
> May 17 17:00:03 vk2-prx01 perdition.pop3s[21176]: SSL connection using AES256-SHA
> May 17 17:00:03 vk2-prx01 perdition.pop3s[21176]: SELF:   "+OK POP3 perditon ready on localhost 0002914b\r\n"
> May 17 17:00:33 vk2-prx01 perdition.pop3s[21176]: CLIENT: "user my_user\n"
> May 17 17:00:33 vk2-prx01 perdition.pop3s[21176]: SELF:   "+OK USER my_user set, mate\r\n"
> May 17 17:00:44 vk2-prx01 perdition.pop3s[21176]: CLIENT: "pass my_pass\n"
> May 17 17:00:44 vk2-prx01 perdition.pop3s[21176]: username_add_domain: username_add_domain 0 1
> May 17 17:00:47 vk2-prx01 perdition.pop3s[21176]: username_add_domain: username_add_domain 0 4
> May 17 17:01:49 vk2-prx01 perdition.pop3s[21176]: REAL:   ""
> May 17 17:01:49 vk2-prx01 perdition.pop3s[21176]: token_read: token_fill_buffer
> May 17 17:01:49 vk2-prx01 perdition.pop3s[21176]: read_line: token_read
> May 17 17:01:49 vk2-prx01 perdition.pop3s[21176]: pop3_out_response: read_line
> May 17 17:01:49 vk2-prx01 perdition.pop3s[21176]: pop3_out_setup: pop3_out_response 1
> May 17 17:01:49 vk2-prx01 perdition.pop3s[21176]: main: protocol->out_setup -1
> May 17 17:01:49 vk2-prx01 perdition.pop3s[21176]: Fatal error negotiating setup. Exiting child.
> 
> 
> I can't really get where the problem is, it looks like I don't get any response from the server ?

Yes, that does seem to be the case, its a bit puzzling.

I have two suggestions:

1) Try tracing the encrypted connection using ssldump

2) Try using the latest perdition code from the mercurial tree.

git clone http://hg.vergenet.net/perdition/perdition/rev/6544c58ec144

______________________________________________
Perdition-users mailing list
[email protected]
http://lists.vergenet.net/listinfo/perdition-users