From: markus schnalke <meillo@marmaro.de>
  To  : <masqmail@marmaro.de>
  Date: Sun, 24 Apr 2011 18:19:52 +0200

About local_addresses and not_local_addresses

Hoi,

I'm currently redesigning the route concept of masqmail in order to
make it simpler and more general.

The config options local_addresses and not_local_addresses are pretty
mind-twisting.


Example for local_addresses="foo@bbb.com":

That means mail to <foo@bbb.com> goes to <foo@localhost> effectively.
But any other mail to <*@bbb.com> will go to the host bbb.com.


Example for not_local_addresses="bar@aaa.org":

On host aaa.org the address <bar@aaa.org> is not considered local.
That means mail will be sent to somewhere else -- where? ... because
aaa.org is the machine itself.


Both directives are somehow opposed to the basic understanding of
users on hosts -- either some machine is host aaa.org or it is not.


Remind that both options modify what is defined the local host. The
description in the man page, however, has an example talking about the
``LAN''. But the options do not at all affect the border between local
net and the rest; they affect the border between the local host and
some other machine instead. This is an indicator that there is a
problem in the meaning of the options.

The options where introduced in 0.2.3. From NEWS:

- Uli Funcke sent a patch with the new options 'local_addresses' and
'not_local_addresses' for masqmail.conf. With these, you can declare single
email addresses as local, though they normally are not, and vice versa,
declare addresses as not local though normally they are (determined with
local_hosts). These options are not yet documented.


I consider removing those two options, but like to hear comments
before.

Can anyone explain a setup that requires using these options?

Does anyone actually use these options?


meillo