Re: [Exim] Can noforward-user skip .forward?

On 2000-08-25 at 15:09 -0400, Dave C. gifted us with:
> > Add 'no_expn' to the aliasfile director(s).
>
> Actually, he probably wants it in the forwardfile director, since that
> is the bit he doesnt want to see when doing EXPN - he does want to see
> the aliases..

Excuse me?

Although that's the _usual_ behaviour desired, that's not what was
requested here.

See:
> My mailing list server has to enforce the usage of primarylogin@domain for
> subscriptions instead of some_random_alias@domain (domain being hosted on
> our mail server)

This, and the mention of wanting to check this remotely, led to my
suggestion of putting no_expn on "the aliasfile director(s)" (which
should have the word 'relevant' in there somewhere) and allowing the
appropriate hosts to do so via smtp_expn_hosts.

In what way is expansion of aliases ('some_random_alias@') prevented by
use of a forwardfile director, which typically works on a basis of a
per-user level.

> One question I might have is what if the aliasfile points at an
> off-site address? Or are you simply going to reject anything where
> <user@localdomain> doesnt expand to the exact same <user@localdomain>
> (w/o checking .forward top elsewhere, which you want to permit), to
> detect any case where any anything other than a local account's primary
> address is used?

Surely this is a testing matter for the client which does the EXPN -
only doing it for those where the MX points to one of their domains. If
the address is offsite, they don't check their own systems for it.
--
"We've got a patent on the conquering of a country through the use of force.
We believe in world peace through extortionate license fees." -Bluemeat