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: > 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

__________________________________________________ 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

thanks Ruprecht... AKNIT --- Ruprecht Helms wrote: > 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 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

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: > 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

__________________________________________________ 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