lists-qmail at maexotic
Mar 5, 2008, 8:31 PM
Post #3 of 3
(409 views)
Permalink
|
On Wed, Mar 05, 2008 at 05:03:37PM -0600, Kyle Wheeler wrote:
> EXT is only (somewhat) correct in a virtualdomain setting. For
> example, if a system user (e.g. joe) creates a ~joe/.qmail file to
> forward email, what should NEWSENDER be? EXT is empty! If a system
> user creates a ~joe/.qmail-owner file, with your change NEWSENDER will
> be owner [at] example, which doesn't seem quite right.
Missed that.
Made a ~alias/.qmail-testme file with "|env > /tmp/testme" and found
LOCAL == EXT == "testme" and thought it was ok, but with ~/.qmail-testme
I got LOCAL == "maex-testme" and EXT = "testme".
I'll have to look at this in more detail and probably some more tests
are necessary in the code to decide whether to use "local" or "ext" :(
> If I remember correctly, qmail uses that information to detect mail
> loops. If we start stripping the virtualdomain stuff off, is there a
> way to create a situation that is not a mail loop but that will be
> detected as a mail loop? I'm not sure, I'd have to think about it.
This shouldn't be a problem. Mail loops are detected by Delivered-To
lines (i.e. the recipient) and the modification is only relevant for
setting the NEWSENDER in case that there is a -owner or -owner-default file.
To be sure we're not misunderstanding each other:
qmail has a "feature" that if there is a e.g. .qmail-list and there is
also a .qmail-list-owner qmail will rewrite the sender of outgoing
messages - due to forwards in .qmail-list - to list-owner instead of the
original sender. This is useful for "poor man's mailing lists" to
catch bounces that would otherwise go to the original sender (see
"man dot-qmail"). AFAICS this is broken for virtualdomains.
ezmlm has a workaorund for this with the inlocal configuration file
(as there is no -default in my situation, using ezmlm's DEFAULT hack
is not possible).
\Maex
|
