popa3d-users - Re: Virtual Domains

Openwall Project		/home Owl JtR Pro crypt pam_passwdqc tcb phpass scanlogd popa3d msulogin / Linux BIND / advisories presentations / services donations / wordlists passwords / news community lists wiki CVSweb mirrors signatures
bringing security into open environments

Password Recovery Resources on the Net

[<prev] [next>] [<thread-prev] [thread-next>] [month] [year] [list]

Date: Sat, 18 Oct 2003 22:15:15 +0400
From: Solar Designer <solar@...nwall.com>
To: popa3d-users@...ts.openwall.com
Subject: Re: Virtual Domains

On Sat, Oct 18, 2003 at 07:08:06PM +0200, Tim van Erven wrote:
> On Sat, 18/10/2003 17:48 +0400, Solar Designer wrote:
> >>>> file = VIRTUAL_HOME_PATH/127.0.0.1/mail/${local_part}

> > I don't really like this suggestion.  If you do use popa3d's sample
> > virtual domain support code unmodified, then please also place the
> > domain information where the code expects it, -- in place of the
> > "127.0.0.1".  Yes, it means that you may need to have your MTA or LDA
> > translate the recipient's domain name into the corresponding virtual
> > mail server's IP address.  (OK, perhaps the sample virtual.c should be
> > enhanced to also support name-based virtual domains.)
> 
> What do you mean by a `virtual mail server'? 

In this context, a POP3 (and maybe also SMTP) server that the users of
a domain may treat as if it were a dedicated mail server for just their
domain.  The sample virtual.c implements the POP3 side of it.

-- 
Alexander Peslyak <solar@...nwall.com>
GPG key ID: B35D3598  fp: 6429 0D7E F130 C13E C929  6447 73C3 A290 B35D 3598
http://www.openwall.com - bringing security into open computing environments