[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Savannah, Pop3 (Was: Re: subject decoding)

From: Sergey Poznyakoff
Subject: Re: Savannah, Pop3 (Was: Re: subject decoding)
Date: Tue, 12 Nov 2002 18:04:33 +0200

> Pure fluke I happened to read this message. =) Sure.  I just need to
> know the savannah user name. =)


> Also - FYI: I may have a contract soon to add virtual hosting to our
> pop3 server.  Has anyone thought about what this would take? I'm
> guessing that there's two or three pieces:
> 1) Parsing out the login name in some way that gives a domain, so like
> jbailey/nisa.net or something like that.

Hmmm.... But pop3d already has virtual domain support. Just start it

        pop3d --authentication generic --authorization virtdomain \

It understands domain separators '!' and '@', i.e. both
address@hidden' and `jbailey!nisa.net' would do. 

> 2) Per domain config files *or* an LDAP record with a field for
> "Mailspool".

Per domain config files are named VIRTDIR/DOMAIN, where VIRTDIR is
the virtual domain configuration directory (set at configure time
with --with-virtual-pwddir option, overriden at runtime with
--virtual-passwd-dir option), and DOMAIN is the user's domain name.
The format of config files is that of usual unix passwd file.
The name of the user's mailbox is built as follows: PW_DIR/INBOX,
where PW_DIR stands for user home directory, retrieved from the
virtual domain file, INBOX is that string literally.

The same applies to imap4d, by the way. The testsuites for both
imap4d and pop3d use this authentication method.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]