Or maybe I should just read the latest documentation...
Include meant you couldn't use the web admin anymore.
g_include
however, just means the web admin
won't let you view or change the entries in that file.
Which, combined
with a little Perl LWP magic and
crontab or some other scheduler for the win32
machines...Should achieve
the same end.
David Camm wrote:
> i'd agree with robert. having the ability to have
netwin drop a file
> in /usr/local/surgemail (or windows equivalent) and to
be able to
> include it - either via web interface or manually by
editing
> surgemail.ini would be perfect.
>
> so we'd have a 'personal' g_deny list followed by
something like
>
> include /usr/local/surgemail/g_deny.txt
>
> and, include should be able to include any file.
include has helped
> immensely managing a large apache config.
>
> david camm
> advanced web systems
> keller, tx
>
>
>
> Robert Fisher wrote:
>> A lot of work to maintain a g_Deny list, but a
rather trivial
>> script to read the drop.lasso file and spit it
back
>> out to a new file with g_Deny CIDR_Block on a line
by line basis.
>> Which is one of the reasons that I
>> wished there was better support for use of the
Include directives in
>> the web ui, since then it would make this
>> sort of changes easier to compartmentalize and
adapt into the setup.
>>
>>
>> webmaster 1usa.com wrote:
>>> Spamhaus.org has a Drop list
>>> http://www.s
pamhaus.org/drop/index.lasso
>>>
>>> They recommend level1 & level2 routers to
drop the packets from
>>> certain IP blocks.
>>> I am wondering if the text list of IP's can be
implemented on a
>>> NetWin server then pushed out to the active
subscriptions... i.e. a
>>> server-side "drop list" ??
>>>
>>> It would be a lot of work for each Admin to
continually update the
>>> list and update their g_Deny list.
>>>
>>> BarryZ
>>>
>>
>>
>>
>
|