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: Connect: hi.mi.ts.u->22.214.171.124
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
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.
Christian Balzer Network/Systems Engineer NOC
chibi(a)gol.com Global OnLine Japan/Fusion Network Services
Sorry for this rather basic and more xinetd-oriented question, but does
anyone on this list perhaps have an xinetd.conf snippet for perdition
that they'd be willing to post? I'm having difficulties transferring the
inetd configuration instructions from the man page to xinetd syntax.
TIA and cheers,
I'm using perdition with mysql backend for pop3 proxy, with user:servername:port table schema.
Is it possible to use only the domain part for authentication, instead of user@domain?
I want to fill the database with domains instead of usernames.
So when a user authenticates using someuser@domain, perdition should check the domain part only in the database, and proxy to the real server listed for it in the db.
> We have a similar setup like yours but we use LDAP. Our configuration
> has the following lines:
> add_domain servername_lookup,1
> query_key \\U,+default@\\d
I have tried your configuration, but still no luck in the backend server:
/Oct 11 10:06:10 buzones_externos dovecot: pop3-login: Aborted login
(auth failed, 1 attempts): user=<prueba>, method=PLAIN,
I need perdition to send @domain to backend-server
Thank you very much Haw
> Hope this helps.
> Perdition-users mailing list
This is my setup
INTERNET<--->perdition<---> multiple mail servers; each one with
I use popmap.re for domain routing. In my setup each mail server
has only one domain, so popmap.re is rather easy.
My problem: A new mailserver has MULTIPLE domains (@domain1,
@domain2, @domain3). Mi popmap.re redirects connections to this host,
but I need to redirect user1@domain1 and user2(a)domain2.com, not only
"user1" and "user2" to the back-end hosts. In few words: i do NOT want
to strip the domain part to the backend server
Mi perdition.conf file:
I IMAP4 IMAP4REV1
I don't know if this issue has already been discussed but I didn't see
it after a quick search. I installed perdition 1.18 and set it up.
Everything worked fantastic including ssl etc... Then I started seeing
some errors like in the subject line above. After turning on debugging
I saw a mention of a temporary failure in dns before the connection
failed. I tested it myself by putting my ipad in an ip block that did
not have a dns server resolving the reverse lookup. It failed. I added
the block to a dns server where it was expected and it worked fine.
Since I don't have access to everyone's reverse ip I tried adding one
client to the hosts file on the server running perdition and it seemed
to fix the issue as well. I have an older version, 1.17, that does not
seem to have a problem with ips that do not have a proper dns server set
up. Is there anyway to stop this from happening?