Hello,
we've been using perdition as a pop3/pop3s/imap/imaps proxy for about
four years now, first with Debian Sarge package and now under Etch.
And throughout this time I've seen pop3s (and from the looks of it
the same happens with imaps) processes stuck in connect, like this:
---
16836 ? S 5:31 0 120 32179 2204 0.0 perdition.pop3s
28070 ? S 0:00 0 120 32311 1564 0.0 \_ perdition.pop3s: connect
7782 ? S 0:00 0 120 32311 1564 0.0 \_ perdition.pop3s: connect
24468 ? S 0:00 0 120 32311 1568 0.0 \_ perdition.pop3s: connect
14180 ? S 0:00 0 120 32311 1568 0.0 \_ perdition.pop3s: connect
13503 ? S 0:00 0 120 32311 1564 0.0 \_ perdition.pop3s: connect
---
They never die off, keep the connection open, there is no traffic and the
other end might be long gone. Last trace in the logs is always like this:
---
Feb 5 22:05:16 pp11 perdition[7782]: Connect: hi.mi.ts.u->203.216.5.113
---
It must be something related to the SSL'ness of these service, since I'm
not seeing this happening ever for imap/pop3. Alas a lot of people do use
TLS with those, so it's not a generic SSL issue. Maybe the master process
could kick a child handling connections in the head after "timeout"
seconds in connect state?
If more information is needed I can try to provide it, but note that with a
rate of roughly 35 pops per second I'm a bit weary to turn on
debugging. ^_-
This may or may not be related to another SSL related issue, which will
be for the sake of making searches in the archive more likely to find good
keywords in a separate mail.
Regards,
Christian
--
Christian Balzer Network/Systems Engineer NOC
chibi(a)gol.com Global OnLine Japan/Fusion Network Services
http://www.gol.com/
Hello,
I've been trying to install perdition on a Lab setup using FreeBSD and
configured to use MySQL . Installation went well.
# cd /usr/ports/mail/perdition/ && make "WITH_MYSQL=YES" install clean
But i encounter the following errors when start the services under
perdition. And i notice that GDBM.so.0 is failing, that i don't remember
installing.
#/usr/local/etc/rc.d/perdition.imap4s onestart
Starting perdition_imap4s.
getserver_openlib: dlopen failed: Cannot open
"/usr/local/lib/libperditiondb_gdbm.so.0"
dlopen of "/usr/local/lib/libperditiondb_gdbm.so.0" failed
perdition version 1.17.1 Copyright Horms
/usr/local/etc/rc.d/perdition.imap4s: WARNING: failed to start
perdition_imap4s
Appreciate any help.
Thanks,
Hello,
We've been using Perdition for a few years now with great success. We
have our users split amongst a handful of mailbox users, and Perdition is
configured to use MySQL to get the destination mail server. We have the
full gamut of services installed: IMAP w/TLS, IMAP w/SSL, POP w/TLS, and
POP w/SSL.
We are in the process of moving to Gmail, and want to be able to use
Perdition to proxy specific users to it. However, Gmail doesn't support
TLS (only the SSL ports). This causes a problem since (as far as my
understanding goes) Perdition uses the same port and protocol for the
outgoing connection as the incoming connection.
Is there a way to have Perdition receive a TLS connection, and then proxy
to imap.gmail.com using SSL?
Hello!
I try to set up perdition-1.18 with dbmail-3.0.0.
POP3 works fine. But IMAP fails on authentification. Here it is part of
perdition log:
Jan 17 07:06:22 vps1471 perdition[30213]: Connect: xxx.xxx.xxx.xxx->xxx.xxx.xxx.xxx
Jan 17 07:06:22 vps1471 perdition[30213]: SELF: "* OK IMAP4 Ready xxx.xxx.xxx.xxx 0001e9cc\r\n"
Jan 17 07:06:22 vps1471 perdition[30213]: CLIENT: "1 capability\r\n"
Jan 17 07:06:22 vps1471 perdition[30213]: SELF: "* CAPABILITY IMAP4 IMAP4REV1\r\n"
Jan 17 07:06:22 vps1471 perdition[30213]: SELF: "1 OK CAPABILITY\r\n"
Jan 17 07:06:23 vps1471 perdition[30213]: CLIENT: "3 login \"mbox(a)mydomain.com\" \"PASSWORD\"\r\n"
Jan 17 07:06:23 vps1471 perdition[30213]: username_add_domain: username_add_domain 0 1
Jan 17 07:06:23 vps1471 perdition[30213]: getserver_key_str: "\d"->"mydomain.com"
Jan 17 07:06:23 vps1471 perdition[30213]: username_add_domain: username_add_domain 0 4
Jan 17 07:06:23 vps1471 perdition[30213]: REAL: "* OK [CAPABILITY IMAP4rev1 AUTH=LOGIN AUTH=CRAM-MD5 ID] dbmail 0.9.9 ready.\r\n"
Jan 17 07:06:23 vps1471 perdition[30213]: SELF: "flim07 CAPABILITY\r\n"
Jan 17 07:06:23 vps1471 perdition[30213]: REAL: "* CAPABILITY IMAP4rev1 AUTH=LOGIN AUTH=CRAM-MD5 ID\r\nflim07 OK CAPABILITY completed\r\n"
Jan 17 07:06:23 vps1471 perdition[30213]: SELF: "flim08 LOGIN {18}\r\n"
Jan 17 07:06:23 vps1471 perdition[30213]: REAL: "+ OK gimme that string\r\n"
Jan 17 07:06:23 vps1471 perdition[30213]: SELF: "mbox(a)mydomain.com {7}\r\n"
Jan 17 07:06:23 vps1471 perdition[30213]: REAL: "flim08 BAD missing argument(s) to LOGIN\r\n"
Jan 17 07:06:23 vps1471 perdition[30213]: imap4_out_response: invalid tag from server 1
Jan 17 07:06:23 vps1471 perdition[30213]: imap4_out_authenticate: imap4_out_response name
Jan 17 07:06:23 vps1471 perdition[30213]: SELF: "PASSWORD\r\n"
Jan 17 07:06:23 vps1471 perdition[30213]: REAL: " BAD no valid command\r\n"
Jan 17 07:06:23 vps1471 perdition[30213]: imap4_out_response: invalid tag from server 1
Jan 17 07:06:23 vps1471 perdition[30213]: imap4_out_authenticate: imap4_out_response passwd
Jan 17 07:06:23 vps1471 perdition[30213]: main: protocol->out_authenticate -1
Jan 17 07:06:23 vps1471 perdition[30213]: Fatal error authenticating user. Exiting child.
It seems that error occurs when perdition after LOGIN sends only username part, then wait for something, and only then try to send password, but it's already error.
What I do wrong?
----
Eugene Alexeyev
