Hello,

my pop3 server won't work. Or rather, I'm unable to log in as any user.
Given my degree of understanding this could have dozens of causes.
My efforts to track down the error could be helped a lot if output was a
little more verbose. All I can get so far is LOGIN FAILED, which is not
much to draw conclusions from.
If there is an option to increase the verbosity of logging, I failed to
see it.


That was the short form. Now I'll describe the behaviour I want to get,
and what I did to set it up. Maybe someone spots the weak point...

I've got a domain mailbox. Everything adressed at [EMAIL PROTECTED]
eventually winds up there. I want to fetch the mail from there, pipe it
through spamassasin, and sort it into several pop3 mailboxes on the
local (micro-)server.
The getmail/maildrop part seems to work so far, so I'll skip that. As
far as I can tell, all my troubles lie with the pop3 server.


I created a 'vmail' user; all maildirs have been created under
/home/vmail.

I created a /etc/courier/userdb; as you may guess, uid/gid belong to the
vmail user.

> pop3schnobs     
> uid=1002|gid=1002|home=/home/vmail|mail=/home/vmail/pop3schnobs|pop3pw=secret
> pop3babylon     
> uid=1002|gid=1002|home=/home/vmail|mail=/home/vmail/pop3babylon|pop3pwd=secret1
> pop3malin       
> uid=1002|gid=1002|home=/home/vmail|mail=/home/vmail/pop3malin|pop3pwd=secret2
[...]


The I ran 'makeuserdb'

Next I edited /etc/courier/pop3d to have the line "POP3AUTH="LOGIN
PLAIN" -- side note: how do I get pop3d to listen only on the local
subnet? "ADDRESS=192.168.30.0/24" did not work.

Finally, I changed the authdaemonrc file: authmodulelist="authuserdb"


I think that's all I did, and obviously something went wrong or is
missing.  

> 
> [EMAIL PROTECTED]:~$ telnet zwerg 110
> Trying 192.168.30.1...
> Connected to zwerg.
> Escape character is '^]'.
> +OK Hello there.
> user pop3schnobs
> +OK Password required.
> pass secret
> -ERR Login failed.

/var/log/mail.log:

> Jun 15 19:57:06 zwerg courierpop3login: Connection, ip=[::ffff:192.168.30.2]
> Jun 15 19:57:38 zwerg courierpop3login: LOGIN FAILED, ip=[::ffff:192.168.30.2]
> Jun 15 19:57:53 zwerg courierpop3login: LOGIN FAILED, ip=[::ffff:192.168.30.2]
> Jun 15 19:57:54 zwerg courierpop3login: Disconnected, ip=[::ffff:192.168.30.2]


Hmm. An what now? The only reason I can rule out is a typo in the
password, as I've double- and triple-checked that one. Leaves me with
permission problems or a fundamental misunderstanding how it is supposed
to work. 

The Courier documentation surely makes a good reference, but finding my
way through it took me quite some time. It just assumes far more prior
knowledge than I had (and have). Some overview, "How It Works", would
have been very helpful; as it was, I had to piece together the
information by reading between the lines and drawing conclusions.

For example, my approach with a 'vmail' user and all maildirs sitting in
that user's /home is not the recommended way of doing it; but lacking
any recommendation, I had to come up with something.

My first version of the userdb file merely had username, maildir and
pop3pw entries. I don't know if or when the uid/gid/home entries are
necessary, but just added them when I kept being shut out.

And so on... any help would be appreciated, because I'm utterly stuck.

cu,
Schnobs



-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to