phl_exempt updates

[William Kronert]

Hello All,

I thought it was time for an update to this phl exempt filter.  There is a 
significant amount of false positives being generated in the microsoft.* 
hierarchy from these posting hosts:

   36 NNTP-Posting-Host: tide016.microsoft.com 207.46.89.16
1158 NNTP-Posting-Host: tk2msftppapi01.phx.gbl 10.40.27.33
1819 NNTP-Posting-Host: 207.46.197.57
2085 NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
4685 NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148

More then 10000 Message-IDs rejected by EMP/phl for microsoft.* on an 
average day.

So the updated cleanfeed local might look something like:

     %config_append = (
(...)
         phl_exempt =>
(....)
'|207\.46.\89.\16' .
'|207\.46\.197\.57' .
'|10\.40\.27\.33' .
'|10\.40\.244\.148' .
'|10\.48\.132\.46' .
'|10\.40\.2\.49' .
'|10\.40\.2\.47' .
'|10\.40\.2\.250' .
'|10\.40\.12\.61' .
'|10\.40\.12\.62' .
'|127\.0\.0\.1' .
(....)

I wonder if there is a better way to keep track of these phl's for microsoft.*?

Best regards.

Bill


At 05:23 AM 7/30/2005, Christoph Biedl wrote:
>Hi,
>
>those who carry microsoft.* should be aware that there are some gateways
>that create a lot of traffic and subsequently false positives in the
>EMP-phl (posting-host, lines) filter. I suggest to update your
>cleanfeed.local accordingly. "10.40.2.49" started yesterday. My current
>setting is:
>
>     %config_append = (
>(...)
>         phl_exempt =>
>(...)   # some private thingies stripped
>             '|10\.48\.132\.46' .
>             '|10\.40\.2\.49' .
>             '|10\.40\.2\.47' .
>             '|10\.40\.2\.250' .
>             '|10\.40\.12\.61' .
>             '|10\.40\.12\.62' .
>(...)
>             '|127\.0\.0\.1' .
>(...)
>
>I've added 127.0.0.1 for another reason: "localhost" is already in the
>list of exemptions but some servers do not resolve the IP and have
>caused false positives.
>
>     Christoph
>
>--
>Mailing list info: http://lists.bofh.it/listinfo/cleaners