Having one config file per domain support in MailScanner ?

[Ugo Bellavance]

Scott Silva wrote:
> on 2/27/2008 5:26 AM Ugo Bellavance spake the following:
>> Hugo van der Kooij wrote:
>>> -----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.
>>
>> Wise decision.  MW 2.0 should be out soon.
>>
> I have been hearing that same song for a while now. I'm tired of the 
> single, release the whole album already!  ;-P

Are you willing to do some testing?

Ugo