OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Subject: Re: LMTP hackings
From: Amos Gouaux (amos+lists.postfixutdallas.edu)
Date: Wed Feb 02 2000 - 09:46:34 CST

Okay, my latest effort now does this, or at least attempts to. It
can be fetched from the following URL:

ftp://ftp.utdallas.edu/pub/staff/amos/postfix/alpha-lmtp.tar.gz

which is a sym link to:

ftp://ftp.utdallas.edu/pub/staff/amos/postfix/lmtp-20000131.tar.gz

I dropped the "rev" suffix since this is starting to depart some from
the original experimental patch. Also, I just had to get a Y2K stamp
in there. ;-)

The makefile-patch has been updated for postfix-19991231-pl03, but
should also work for postfix-19991231-pl04.

After you apply the makefile-patch and the global-patch, you should
be able to compile as usual, then do the make install bit. You may
have to manually copy libspawn in the top-level Postfix source
directory into the run-time lib directory with the other Postfix
binaries (as "spawn").

To set up for local delivery, you'll want your master.cf to look
something like this:

lmtp unix - - n - - lmtp
    serv=unix:private/lmtpd
lmtpd unix - n n - - spawn
    user=cyrus:cyrus argv=/usr/local/cyrus/bin/deliver -e -l

One question that has been presented to me previously is how to get
this to work so that all the recipients of a message are included at
once, instead of each recipient getting a copy as usual for local
delivery. The issue is that when deliver is run in LMTP mode, and if
all the recipients are on the same Cyrus partition, each recipient
will get a hard link of the message instead of a copy.

Well, that's a good question. The only thing I could think of so far
is to not do

mailbox_transport = lmtp

But instead simply have a transport map entry for that host as
follows:

this.host.domain lmtp:

One possible problem I see with this is that aliases will never be
expanded, which may or may not be an issue. Maybe there's a better
way to deal with this?

Amos

On Fri, 7 Jan 2000, Wietse Venema wrote:

> Note that the 19991231 release has a little "spawn" daemon for
> testing that can run the LMTP server off a UNIX-domain socket or
> off an internet socket, whatever you specify in master.cf.
>
> Wietse
>
> Amos Gouaux:
> > For those that might be interested, I've tared up another "rev" of
> > the lmtp-19990427 patch. The URL is:
> >
> > http://ftp.utdallas.edu/pub/staff/amos/postfix/lmtp-19990427-05.tar.gz
> >
> > My previous hackings dropped the cached connections support as I was
> > learning how stuff works. I've added the cached connections back
> > in, and we've been using it on our systems for a couple of weeks.
> >
> > You may want to fiddle with the number of instances of lmtp you have
> > as well as the max_use setting in main.cf. While I suspect it would
> > not be wise to pump up max_use too high, I've been running with it
> > at 200 and it seems to be okay. I've also got the number of lmtp
> > sessions currently set at 3.
> >
> > To install, cd into the Postfix source dir and untar the file above,
> > then apply the following two patches:
> >
> > patch -p0 < lmtp/makefile-patch
> > patch -p0 < lmtp/global-patch
> >
> > These diffs were done against postfix-19991231-pl02.
> >
> > Currently, this version of lmtp supports both pipes and inet
> > connections. This will very likely change in some subsequent
> > rendition. Instead, it will only use either UNIX domain sockets or
> > inet sockets. An additional process will be responsible for running
> > deliver in LMTP mode. This is so that things are better
> > compartmentalized into the appropriate pieces for the respective
> > task. The current offering is simply made as an interim solution.
> > So if you use this, realize that the configuration of the various
> > pieces will be changing.
> >
> > Amos
> >
> >
> >
> >
> >
>
>
>