> > SM> The problem here is that having a .qmail-default file
> isn't enough.
> >
> > That's odd. The qmail support was contributed and has
> worked fine for
> > other folks for some time now. Patches are of course
> welcome, but I don't
> > have the means to test them.
>
> The problem is that there are two different ways to glue qmail into
> majordomo. The simpler but less flexible is to use a
> .qmail-default file, which tells qmail to hand all mail to any otherwise
unknown
> address to MJ, at which point MJ figures out what the address means and
how to
> handle the mail. This works fine if the domain isn't used for much else.
It
> doesn't work at all if, for example, the other addresses in the domain are
> looked up in a database, because the database lookup also needs to use a
> -default to catch its addresses.
Exit codes are used in .qmail-default (and other qmail commands):
>
> The other approach, which I've used for MJ 1, is to create all of the
> explicit aliases that each mailing list needs. That works,
> but it's a lot of
> qmail files. It's also possible to put multiple commands in
> a -default file,
> so that in principle MJ2 could sniff the address and do its
> thing if it's an
> address it recognizes, otherwise fall through to another program.
>
> Having done all sorts of things like that, I can report that
> it's too fragile
> -- if both programs are expecting the same address, one will
> win and the
> other will lose. My suggestion in most cases is to use a
> separate domain for
> mailing lists, lists.whatever.com, and only put mailing list
> addresses there.
> For that, the current -default technique works fine.
>
> Regards,
> John Levine, johnl@iecc.com, Primary Perpetrator of "The
> Internet for Dummies",
> Information Superhighwayman wanna-be, http://iecc.com/johnl,
> Sewer Commissioner
> Finger for PGP key, f'print = 3A 5B D0 3F D9 A0 6A A4 2D AC
> 1E 9E A6 36 A3 47
>
>
|
|
