Configuration of postfix 2.8.1 + ezmlm 1.2.17
Mark Alan
In order to have postfix 2.8.1 feeding email to a ezmlm 1.2.17 mailing
list manager (under Debian/Ubuntu) we have a tentative setup that
goes like described bellow.
I have 2 questions:
1. is there a way to do the same without (the rather expensive)
regexp:/ lists?
2. in case of not being possible to do without regexp (or just in case
the regexp happens to be the right solution) is this the right regex
syntax to serve this setup?
# about the mailing list manager
mailing list manager:
mlmmj (which is a MTA agnostic ezmlm clone)
list address:
lis...@example.org
control commands:
list01+s...@example.org
list01+un...@example.org
list0...@example.org
# VERP Return-Path:
list01+bounces-12-john.doe=domai...@example.org
# the tentative configuration:
virtual_alias_maps = cdb:/etc/postfix/virtual-alias-maps,
regexp:/etc/postfix/mlmmj-virtual-alias-maps /etc/postfix/mlmmj-virtual-alias-maps
/^(list01.*)@example\.com$/ ${1}
mlmmj_destination_recipient_limit = 1
transport_maps = regexp:/etc/postfix/mlmmj-transport
/etc/postfix/mlmmj-transport
/^(list01).*$/ mlmmj:$1
/etc/postfix/master.cf:
# transport for the mlmmj mailing list
mlmmj unix - n n - - pipe flags=DORhu user=nobody
argv=/usr/local/bin/mlmmj-receive -F -L /var/spool/mlmmj/$nexthop/
postconf |grep default_privs => default_privs = nobody
Thanks,
M.
Wietse Venema
If you follow the mlmmj website's instructions, then it should
work. I prefer not to review alternative variations.
By the way, the mlmmj setup can now be simplified, and no longer
needs the kludge with the mlmmj/pipe transport. postfix-2.9-20110228
fixes a problem where the local delivery agent ignored the ownership
of regexp-based alias tables.
Why was this fixed 20110228? Because I recently stumbled upon this
problem when I visited the mlmmj/postfix webpage.
Wietse
Mark Alan
<wie...@porcupine.org> wrote:
> > In order to have postfix 2.8.1 feeding email to a ezmlm 1.2.17
> If you follow the mlmmj website's instructions, then it should
> work.
Do you mean the README.Postfix at
http://mlmmj.org/archive/mlmmj/att-0511/README.postfix ?
> I prefer not to review alternative variations.
I can understand that.
But in this case, as this is rather generic regarding MLM proper
interfacing with Postfix, it sure would be welcome to have your
view about the proper way to setup a generic interface between Postfix
and a generic MLM.
> By the way, the mlmmj setup can now be simplified, and no longer
> needs the kludge with the mlmmj/pipe transport.
I know that it also consumes time but... could you give a tiny
example/usage case?
> postfix-2.9-20110228
> fixes a problem where the local delivery agent ignored the ownership
> of regexp-based alias tables.
Will this bug fix be backported into 2.8.x ?
> Why was this fixed 20110228? Because I recently stumbled upon this
> problem when I visited the mlmmj/postfix webpage.
That page is marked Nov 12th 2005 but in fact, as it is clear from the
change log, it just appeared in the latest (1.2.17.1, Nov 2010) release.
M.
Wietse Venema
> But in this case, as this is rather generic regarding MLM proper
> interfacing with Postfix, it sure would be welcome to have your
> view about the proper way to setup a generic interface between Postfix
> and a generic MLM.
Sorry, I don't have time to review all the instructions on the web
that describe how to plug some program into Postfix. That's what
I have to leave to the people who use that program with Postfix.
> > By the way, the mlmmj setup can now be simplified, and no longer
> > needs the kludge with the mlmmj/pipe transport.
>
> I know that it also consumes time but... could you give a tiny
> example/usage case?
Consider this your opportunity to become a hero, with help from
the mailing list :-) The basic idea is that with a local aliases
file, file ownership determines the execution privileges for
"|command" and /file/name destinations, and the envelope sender
address for non-delivery notifications.
In other words, alias ownership of regexp/pcre files now works as
documented. Just give the file the right owner, and "|command"
will execute as the owner of the aliases file, instead of nobody.
> > postfix-2.9-20110228
> > fixes a problem where the local delivery agent ignored the ownership
> > of regexp-based alias tables.
>
> Will this bug fix be backported into 2.8.x ?
Never. This was an invasive code change that affected 25 different
source code files. I will be proofreading and testing that code
several times over the course of this year before it becomes part
of the next stable release.
Wietse
Mark Alan
<wie...@porcupine.org> wrote:
> The basic idea is that with a local aliases
> file, file ownership determines the execution privileges for
> "|command" and /file/name destinations, and the envelope sender
> address for non-delivery notifications.
Meaning that (keeping with the example lis...@example.org mailing list)
the following would simply work as expected:
/etc/postfix/virtual-alias-maps
lis...@example.org list01@localhost
/etc/aliases
list01: "|/usr/bin/mlmmj-recieve -L /var/spool/mlmmj/list01/
> In other words, alias ownership of regexp/pcre files now works as
> documented.
If not for anything else, at least this was good to fix that bug.
... and, by the way, the subject of this thread should have been
"Configuration of postfix 2.8.1 + mlmmj 1.2.17", not ezmlm... but it
seems that old habits don't die easily.
Thank you Wietse and keep up this great work
M.