Having one config file per domain support in MailScanner ?

[Hugo van der Kooij]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michael Mansour wrote:
| Hi,
|
| Does MailScanner support having one config per domain?
| ie. instead of putting everything into the one config
| file like:
|
| /etc/MailScanner/rules/someMSoption.rules
| From:   blah at domain1.com   no
| From:   blah at domain2.com   no
| FromOrTo:  default         yes
|
| you can have it like:
|
| /etc/MailScanner/rules/MSoption1.rules
| From:   blah at domain1.com   no
| FromOrTo:  default         yes
|
| /etc/MailScanner/rules/MSoption1.rules
| From:   blah at domain2.com   no
| FromOrTo:  default         yes

But what does one gain this way? (Besides from your duplicate use of the
same file ;-) And how do you expect it to behave? Because you redefined
the default.

I could see some logic in getting the data from SQL instead of fixed
files. Then you can fill the table anyway you like it.

In fact about 5 minutes after I installed MailWatch I started to itch to
add a lot of tables to the database and write up some code to make use
of it. But as MailWatch 2.0 was just under development I decided to sit
it out. I am not sure how much of it is going to be in MailWatch 2.0 but
~ that would be my way to work the issue.

Hugo.

- --
hvdkooij at vanderkooij.org               http://hugo.vanderkooij.org/
PGP/GPG? Use: http://hugo.vanderkooij.org/0x58F19981.asc

	A: Yes.
	>Q: Are you sure?
	>>A: Because it reverses the logical flow of conversation.
	>>>Q: Why is top posting frowned upon?

Bored? Click on http://spamornot.org/ and rate those images.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFHw7gsBvzDRVjxmYERAlywAJ9NpQn9kOl1zuWwsevi7Yl3e+RK3ACgjJ59
y401+swWyJUS39SjZSGbD6w=
=xw77
-----END PGP SIGNATURE-----