On Sun, 13 Nov 2005, Tony Finch wrote:
> On Sat, 12 Nov 2005, Leonardo Boselli wrote:
> > I wish however that:
> > a. if the message is sent to name.surname@otherdomain a list of aliases
> > be checked to see if the addresse is in one alis list, so the message is
> > not sent out and then bounced back;
> If both domains are hosted on the same machine then Exim will do this by
> default. If not, you need to configure recipient callout verification on
> the machine hosting otherdomain.
I have the list of aliases on a local file, so i can know if the user is
local or not.
> > b. if the message is sent to any.one@otherdomain if the sender is in the
> > list of aliases the from field be mangled to become
> > name.surname@otherdomain
> Why do you think this is a good ieda?
The manager of the big organization i work for require that any one must
have an address of name.surname@domain .
However some departments (included mine) since many years use departmental
servers with addresses name.surname@??? or more often
nick@??? .
Such departmental servers have a much higher reliability then central
ones, so people prefer to stay there. (and since these are administered by
local staff for any problem an help is also physically near)
However managers reuire that any internal correspondence is sent with the
official name, hence the requirement to rewrite the from address for email
sent inside the organization, while retaining the original one (with
department.domain) for message sent outside (there are a lot of peope
subscribed to list and service, for which changing the address would be
an annoyance, not to say the fact that is lost the departmental identity
...).
