[Vmail-discuss] POP-and-SEND with vmail

[Marcin Pacyna]

That's exactly what I meant by POP-and-SEND.

Currently I'm redirecting the log output from my POP3 daemon into a named
pipe (via syslog) which in turn gets parsed by a perl script (which I found
somewhere on a sendmail site) which puts authenticated IPs as files into a
spool directory which then gets compiled into a table which is read by
exim... etc.  That same script checks the creation time of each file and
removes the appropriate files from the spool after a specified time.

I could use the same method with tpop3d however the log output from tpop3d
is quite different - my current pop3 daemon spits out easily parsable lines
such as:

Jul 17 12:54:27 mail ipop3d[16983]: Login user=someuser
host=somehost.domain.com [10.10.10.10] nmsgs=0/0

so all I need to look for is a line that has a "Login" and I grab the IP
from it.

tpop3d has slightly more verbose output usually spanning multiple lines
which isn't as easy to parse.

Maybe it'd be useful to add an option to have a more compact logging in
tpop3d? (if there isn't one in place already)

Regards,

Marcin Pacyna
System Administrator
Nexvision Interactive

-----Original Message-----
From: vmail-discuss-admin@lists.beasts.org
[mailto:vmail-discuss-admin@lists.beasts.org]On Behalf Of Chris
Lightfoot
Sent: Tuesday, July 17, 2001 12:36 PM
To: Marcin Pacyna
Cc: vmail-discuss@lists.beasts.org
Subject: Re: [Vmail-discuss] POP-and-SEND with vmail


On Tue, Jul 17, 2001 at 12:24:56PM -0400, Marcin Pacyna wrote:
> Hey,
>
> I'm wondering what others are doing for POP-and-SEND when using vmail
> (w/tpop3d) setup.  I'm thinking of switching to vmail but that's one of
the
> reasons that I haven't done it yet.

I guess you mean what I think of as `POP-before-SMTP
relaying'? AFAIAA, there are two basic approaches:

    1. have some long-running process which watches the
       log files, and then writes into a table of hosts
       allowed to relay when it sees an incoming
       connection to tpop3d get authenticated;

    2. some sort of event-driven scheme; this can be done
       (for instance) by modifying the code in tpop3d's
       main.c to authorise relaying immediately before the
       daemon forks and drops privileges; or use auth_perl
       or auth_other to do the same thing. In the latter
       case you'd (obviously) need to write an
       authenticator.

A number of people have asked me about things of this
sort, and I suspect I will introduce a way to hook the
functionality in to tpop3d in a neat way. Meanwhile, I
believe that previous posters have had success with the
first (ugly) approach above.

Out of interest, how do you set up permission to relay?
How does it get revoked (presumably a little while after
it is granted)?

(If I've missed the point completely, well, I hope this
email has been informative anyway....)

--
Chris Lightfoot -- www.ex-parrot.com/~chris/
 ``What men are poets who can speak of Jupiter as if he were a man, but if
   he is an immense spinning sphere of methane and ammonia must be silent?''
   (Richard Feynman)

_______________________________________________
vmail-discuss mailing list
vmail-discuss@lists.beasts.org
http://lists.beasts.org/mailman/listinfo/vmail-discuss