| View previous topic :: View next topic |
| Author |
Message |
whit
Tux's lil' helper
Joined: 26 Oct 2002
Posts: 121
Location: VT
|
 Posted: Thu Nov 20, 2003 2:49 am Post subject: A minimal tpop3d setup |
 |
|
After a system restart yesterday, ipop3 (actually uw-ipop3, running from xinetd) stopped working. Probably some side-effect of something else I upgraded since the last restart. What the heck, time to try something new.
tpop3d, currently unmasked in portage at version 1.4.2, is a stand-alone daemon that runs really fast (I've found - noticeably faster using fetchmail than ipop3) and is ultra-configurable. However, the ebuild just leaves you with the advice to write an /etc/tpop3d/tpop3d.conf file, without any clues beyond "man tpop3d.conf" about what at minimum needs to be there, or about starting the daemon (there's no init script provided by the ebuild).
So here's, briefly, what I've found out:
On a system using mbox format for incoming mail, this tpop3d.conf file works, at least on my system:
| Code: |
listen-address: 0.0.0.0
auth-pam-enable: yes
auth-pam-facility: pop
auth-pam-mail-group: mail
mailbox: bsd:/var/spool/mail/$(user)
|
If you're using maildir (e.g. qmail), you'll just need to change the "mailbox: ..." line according to how that's set up on your system (see the man page on this).
You'll also need an appropriate /etc/pam.d/pop file. In my case, this was already there from ipop3. If you don't have it, create it:
| Code: | #%PAM-1.0
auth required pam_nologin.so
auth required pam_stack.so service=system-auth
account required pam_stack.so service=system-auth
session required pam_stack.so service=system-auth
|
To start and debug:
| Code: |
tpop3d -f /etc/tpop3d/tpop3d.conf -d -v
|
That will leave it up on your terminal, and you can try poping from another system. Once you're happy with the result you can put
| Code: |
/usr/sbin/tpop3d -f /etc/tpop3d/tpop3d.conf
|
into /etc/conf.d/local.start. That "-f /etc/tpop3d/tpop3d.conf" is necessary since the ebuild, although it creates the empty tpop3d directory, actually looks in /etc for tpop3d.conf by default.
There are many other tricks that can be done with this versatile daemon, apparently. But these are the minimal steps to get a default Gentoo install operational.
If you, like me, already had ipop3 running from xinetd, it's also appropriate to edit /etc/xinetd.d/ipop3 and set "disable = yes" to preclude it trying to grab the connection. |
|
| Back to top |
|
 |
Baer
Tux's lil' helper
Joined: 11 Sep 2003
Posts: 96
Location: Munich, Germany
|
| Posted: Thu Nov 11, 2004 11:24 pm Post subject: |
|
|
Hmm...
doesn't really work here.
For some reason all users trying to get mail get a Lies! Try again! after entering the password with
| Code: | Nov 12 00:22:55 midgard tpop3d[6343]: auth_pam_new_user_pass: pam_authenticate(baer): Authentication failure
Nov 12 00:22:55 midgard tpop3d[6343]: connection_do: client `[6]80.134.72.108/heim10.tu-clausthal.de': username `baer': 1 authentication failures |
entry in syslog. Any ideas?
---
EDIT: Found my mistake. My PAM facility was named pop instead of pop3.
Regs
Rob
_________________
Life is like a roll of toilet paper, when the end is near we panic! |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Documentation, Tips & Tricks
