On Fri, 24 Oct 1997, Daniel Ryde wrote:
> Hum, it is the same if they are separate aliases in any aliasfile:
> foo1: foo
> foo2: foo
Indeed. That is quite deliberate and the same way that smail works; I
don't know about other MTAs. Exim doesn't do duplicate deliveries to
identical addresses, except in the very special case that the "address"
is a pipe command. (This is so that if two different recipients are both
piping their mail to, say, /usr/bin/vacation, it gets run for each of
them.)
What do people feel about this? If, say, hostmaster and postmaster point
to the same address and somebody mails to "hostmaster,postmaster", do
you expect to get one or two copies of the message?
> Ok, heres another thing: I tried to add a header
> add_headers = "X-rcptto: $recipients"
>
> and that gave an error:
> appendfile transport process returned a non-zero status (0x0100)
Presumably because the expansion failed.
> And the mail got frozen, and the mailbox lockfile was remainig, which
> prevented further mail delivery/reading to that mailbox.
>
> Using other variables works fine, but not the $recipients.
> The manual says "is recognized only in the system filter file, to prevent
> exposure of Bcc recipients to ordinary users", but why is it prevented in
> the transport configuration?
It's not so much prevented as not enabled. I can't off the top of my
head think of any reason why it shouldn't be enabled, since the
configuration is under the control of the administrator. I have added
the requirement to the list.
But is it really going to help you? Surely what you want is a list of
*those recipients that have resolved to this transport* rather than all
recipients of the message?
A number of people seem to have this requirement, for packing up a
message and doing other things with it, for a number of recipients, and
without using BSMTP. I am not entirely convinced that using an alias is
the right way to handle this, because it is really a mail routing
problem, but I can see the attraction of having the information for a
virtual domain all there in a single file.
Hmm. I wonder if a scheme could be worked out whereby you specified that
if an address did not match an alias file, it was sent to a specific
transport. Then several different ones would not get merged. This should
be easy to do; at present if there is a transport setting on aliasfile,
it ignores the data and sends anything that matches the file to the
transport. A new option such as "no_match_transport" could be added to
handle non-matching addresses. Of course, you would want to turn off the
wildcard in this case.
--
Philip Hazel University Computing Service,
ph10@??? New Museums Site, Cambridge CB2 3QG,
P.Hazel@??? England. Phone: +44 1223 334714
--
* This is sent by the exim-users mailing list. To unsubscribe send a
mail with subject "unsubscribe" to exim-users-request@???
* Exim information can be found at http://www.exim.org/
