i have recently moved from Qualcomm's Qpopper to Qmail's qmail-pop3d, and have two problems i badly need some help on: first, connecting to port 110 takes about 4 to 5 seconds because i am using TCP Wrappers and /etc/hosts.allow ... removing the TCP Wrappers in /etc/inetd.conf will enable me to connect instantly to port 110, but somehow, will not open the user's Maildir ... i have looked at permissions of both qmail-pop3d and inetd, but with no luck... any ideas..? second, after moving to qmail-pop3d, i can no longer log POP'ing activity of my users.. i can only log qmail-popup connections in /var/log/messages .. my tries with /etc/syslog.conf have proven fruitless.... all help will be appreciated.. thanks.. AKNIT __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com
On Wednesday 20 February 2002 10:30 pm, Mark Tinka wrote:
i have recently moved from Qualcomm's Qpopper to Qmail's qmail-pop3d, and have two problems i badly need some help on:
first, connecting to port 110 takes about 4 to 5 seconds because i am using TCP Wrappers and /etc/hosts.allow ... removing the TCP Wrappers in /etc/inetd.conf will enable me to connect instantly to port 110, but somehow, will not open the user's Maildir ... i have looked at permissions of both qmail-pop3d and inetd, but with no luck... any ideas..?
second, after moving to qmail-pop3d, i can no longer log POP'ing activity of my users.. i can only log qmail-popup connections in /var/log/messages .. my tries with /etc/syslog.conf have proven fruitless....
Haven't seen that package, but I gotta ask.... If the qpopper did all that for you, why switch? Qpopper has been utterly reliable for me. -- _________________________________ John Andersen / Juneau Alaska
Qpopper uses the standard UNIX mail box format, or
mbox for that matter, which retrieves e-mail from a
single file.. while this is not a problem, it creates
a problem if a user is downloading e-mail, and for
some reason, say a power cut, telephone line
instability or sthing like that, he gets disconnected,
he may not be able to re-download his mail because of
a pop-lock file that was created for his initial
session.... that means a UNIX admin would have to
manually copy all temp e-mail back to the mbox file,
then delete the lock file.. which can be tedious if u
have a large network using your mail server as their
primary mail hub....
Qmail, is an MTA, but also has a POP3 server called
qmail-pop3d, which uses a system called Maildir, where
mail is stored in the user's home directory, in a
directory called Maildir, each as a separate file...
similar to the way Eudora stores download e-mail...
here, each file is downloaded separately, without need
for a pop lock sessions, and if a user gets
disconnected, he may return and continue where he left
off.... which is more reliable i think....
of course, Maildir can only be used with MTA's that
support Maildir delivery, which i think, at the
moment, are Postfix and Qmail...
i still need some ideas on qmail-pop3d logging and TCP
Wrapper behaviour, though...thanks..
AKNIT
--- John Andersen
wrote:
i have recently moved from Qualcomm's Qpopper to Qmail's qmail-pop3d, and have two problems i badly need some help on:
first, connecting to port 110 takes about 4 to 5 seconds because i am using TCP Wrappers and /etc/hosts.allow ... removing the TCP Wrappers in /etc/inetd.conf will enable me to connect instantly to port 110, but somehow, will not open the user's Maildir ... i have looked at permissions of both qmail-pop3d and inetd, but with no luck... any ideas..?
second, after moving to qmail-pop3d, i can no longer log POP'ing activity of my users.. i can only log qmail-popup connections in /var/log/messages .. my tries with /etc/syslog.conf have proven fruitless....
Haven't seen that package, but I gotta ask.... If the qpopper did all that for you, why switch?
Qpopper has been utterly reliable for me.
-- _________________________________ John Andersen / Juneau Alaska
__________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com
Hi, I've forwarded the mail to the qmail-list. Possible someone there have some good ideas asked in your last mail. On 21-Feb-02 Mark Tinka wrote:
Qpopper uses the standard UNIX mail box format, or ...
Regards,
Ruprecht
----------------------------------
E-Mail: Ruprecht Helms
thanks Ruprecht...
AKNIT
--- Ruprecht Helms
I've forwarded the mail to the qmail-list. Possible someone there have some good ideas asked in your last mail.
On 21-Feb-02 Mark Tinka wrote:
Qpopper uses the standard UNIX mail box format, or ...
Regards, Ruprecht
---------------------------------- E-Mail: Ruprecht Helms
Date: 21-Feb-02 Time: 09:56:43 This message was sent by XFMail ----------------------------------
__________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com
On Thu, Feb 21, 2002 at 08:11 +0000, Mark Tinka wrote:
[ Maildir discussin snipped ]
of course, Maildir can only be used with MTA's that support Maildir delivery, which i think, at the moment, are Postfix and Qmail...
Yes, qmail introduced the Maildir format to escape the deficiencies in the traditional mbox format (especially when used over NFS). But there are quite a few programs supporting Maildir (admittedly not all of them are MTAs or POP servers): the qmail suite (of course), mutt, procmail, cclient (a library used by pine, imap-uw, postilion, tkrat, and maybe others plus a Perl module p5-CClient is available), courier-imap (see www.inter7.com) are the ones I could come up with after one minute of searching. Looking at the benefits (the description used to live at http://cr.yp.to/proto/maildir.html) and remembering the fact that libraries are available mail software authors should head for supporting this format. Since users should require this feature once they learn that mbox is not a given. :)
i still need some ideas on qmail-pop3d logging and TCP Wrapper behaviour, though...thanks..
You talk about the delay when using tcpd? I would shoot into the dark by pointing to some kind of reverse DNS mapping or ident lookup. But since you didn't give a single detail about your setup it's rather hard to help here. But why don't you use the tools from the ucspi-tcp suite when you already have DJBware running? Since tcpserver won't scan and parse text files every time a connection is made it should serve somewhat faster. Plus updating the ruleset only succeeds when the description is syntactically correct (unlike a text editor where the user is free to save broken configs at any time he pleases) and will be done atomically. Rate limiting is available, too. What do you need inetd and tcpd for? Regarding the qmail-pop3d logging you don't specify your setup either. But you definitely should read the doc for the software you run (not only the qmail doc but administering a UNIX machine you should have a general idea of what *every* component of your system does and how it gets configured plus which logs to look at and which tools to use for diagnosis should problems bubble up). You don't seem to have figured yet which tool serves what purpose in your setup, but I assume you run the service under supervise's control which logs into the multilog program (both of which are part of the daemontools suite). That's when fiddling with syslog's config won't help you much ... Again, go to the cr.yp.to site and look at the doc for the programs you use!
[ fullquote at the message bottom (urgh!) snipped ]
Feel free to do your homework and solve your problem with the help of people who know qmail or by using the resources I pointed you to in the above paragraphs. But please don't reply to the list on this topic since "my network is slow", "I cannot find my services' logs", and the like are _not_ appropriate for a list like suse-security. Please use a forum which better (not to say "at all") fits your problem. I'm sorry myself for contributing to this OT thread but I hope to help its immediate death this way. Thank you for not cluttering the security list with "how do I setup my mail system?" questions in the future. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you.
Qpopper uses the standard UNIX mail box format, or
mbox for that matter, which retrieves e-mail from a
single file.. while this is not a problem, it creates
a problem if a user is downloading e-mail, and for
some reason, say a power cut, telephone line
instability or sthing like that, he gets disconnected,
he may not be able to re-download his mail because of
a pop-lock file that was created for his initial
session.... that means a UNIX admin would have to
manually copy all temp e-mail back to the mbox file,
then delete the lock file.. which can be tedious if u
have a large network using your mail server as their
primary mail hub....
Qmail, is an MTA, but also has a POP3 server called
qmail-pop3d, which uses a system called Maildir, where
mail is stored in the user's home directory, in a
directory called Maildir, each as a separate file...
similar to the way Eudora stores download e-mail...
here, each file is downloaded separately, without need
for a pop lock sessions, and if a user gets
disconnected, he may return and continue where he left
off.... which is more reliable i think....
of course, Maildir can only be used with MTA's that
support Maildir delivery, which i think, at the
moment, are Postfix and Qmail...
i still need some ideas on qmail-pop3d logging and TCP
Wrapper behaviour, though...thanks..
AKNIT
--- John Andersen
wrote:
i have recently moved from Qualcomm's Qpopper to Qmail's qmail-pop3d, and have two problems i badly need some help on:
first, connecting to port 110 takes about 4 to 5 seconds because i am using TCP Wrappers and /etc/hosts.allow ... removing the TCP Wrappers in /etc/inetd.conf will enable me to connect instantly to port 110, but somehow, will not open the user's Maildir ... i have looked at permissions of both qmail-pop3d and inetd, but with no luck... any ideas..?
second, after moving to qmail-pop3d, i can no longer log POP'ing activity of my users.. i can only log qmail-popup connections in /var/log/messages .. my tries with /etc/syslog.conf have proven fruitless....
Haven't seen that package, but I gotta ask.... If the qpopper did all that for you, why switch?
Qpopper has been utterly reliable for me.
-- _________________________________ John Andersen / Juneau Alaska
__________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com
participants (4)
-
Gerhard Sittig
-
John Andersen
-
Mark Tinka
-
Ruprecht Helms