Re: Sharing DB over multiple MX

Hello,


In the selective filters the filter:

/^[^.]*[0-9].[^.]*[0-9].[^.]+..+./

Matches up with:

bay0-omc1-s1.bay0.hotmail.com[65.54.246.73]


Since we know that hotmail will always resend the emails
eventually,
hotmail should be excluded from this filter. Any ideas on
what should be
done?

Thanks,

David


On Fri, January 5, 2007 3:24 am, SATOH Kiyoshi wrote:
> On Tue, 2 Jan 2007 19:19:41 +0100
> Steven Moix <steven.moixaxianet.ch> wrote:
> Subject: [postgrey] Re: Sharing DB over multiple MX
>
>
>> Btw, with your idea what would happen if the server
hosting the
>> postgrey database would crash? Seems dangerous to
me as you already say
>> 
>>
>
> I think the damage of the server becomes a minimum if
the server use
> selective greylisting (Rgrey). Because almost all
legitimate mail servers
> are not greylisted.
>
> See:
> [postgrey] Hostname-based Selective Greylisting
> http:/
/lists.ee.ethz.ch/postgrey/msg01214.html
>
>
> ---- main.cf ----
> smtpd_restriction_classes = check_greylist
>
> check_greylist = check_policy_service
inet:127.0.0.1:10023
>
> smtpd_recipient_restrictions = permit_mynetworks
reject_unauth_destination
> ...
> check_client_access
regexp:$config_directory/check_client_fqdn ...
> permit ---
>
>
> ---- check_client_fqdn ----
> /^unknown$/                                 
check_greylist
> /^[^.]*[0-9][^0-9.]+[0-9]/                
check_greylist
> /^[^.]*[0-9]/                           
check_greylist
> /^([^.]+.)?[0-9][^.]*.[^.]+..+.[a-z]/
check_greylist
> /^[^.]*[0-9].[^.]*[0-9]-[0-9]/           
check_greylist
> /^[^.]*[0-9].[^.]*[0-9].[^.]+..+./   
check_greylist
> /^(dhcp|dialup|ppp|adsl)[^.]*[0-9]/        
check_greylist
> ---
>
>
> or
>
> ---- main.cf ----
> smtpd_recipient_restrictions = permit_mynetworks
reject_unauth_destination
> ...
> check_client_access
regexp:$config_directory/permit_client_nots25r
> check_policy_service   inet:127.0.0.1:10023 ...
> permit ---
>
>
> --- permit_client_nots25r ---
> /.dip.t-dialin.net$/       WARN
> /.dyn.optonline.net$/      WARN
> ...(other dynamic IP FQDN pattern(not match S25R
pattern))
> !/(^unknown$)|(^[^.]*[0-9][^0-9.]+[0-9])|
>
(^[^.]*[0-9])|(^([^.]+.)?[0-9][^.]*.[^.]+..+.[a-z
])|
> (^[^.]*[0-9].[^.]*[0-9]-[0-9])|
> (^[^.]*[0-9].[^.]*[0-9].[^.]+..+.)|
> (^(dhcp|dialup|ppp|adsl)[^.]*[0-9])/ OK  ...(This
regexp is one line)
> /./                           WARN
> ---
>
>
> --
> SATOH Kiyoshi <satohhakuba.jp> http://d.hatena.ne.
jp/stealthinu/
>
>
> --
> Unsubscribe mailto:postgrey-requestlist.ee.ethz.ch?subject=unsubscribe
> Archive     http://lists.ee.ethz
.ch/postgrey
> WebAdmin    http://lists.ee.ethz
.ch/lsg2.cgi
>
>
>



-- 
Unsubscribe mailto:postgrey-requestlist.ee.ethz.ch?subject=unsubscribe
Archive     http://lists.ee.ethz
.ch/postgrey
WebAdmin    http://lists.ee.ethz
.ch/lsg2.cgi

No that's exactly the kind of hostname these regexes are
intended to hit -
the .adsl. indicates it's... the kind of host more likely to
be a window
zombie owned by a spammer than a legit mail server.

On 01/22, David wrote:
> Hello,
> 
> I have another issue with selective filtering:
> 
> from boi103.neoplus.adsl.tpnet.pl
(boi103.neoplus.adsl.tpnet.pl
> [83.29.24.103])	by a.mx.omnity.biz (Postfix) with ESMTP
id AB1FF497	for
> 
> This is not caught by :
> 
> /^(dhcp|dialup|ppp|adsl|dsl)[^.]*[0-9]/    
check_greylist
> 
> Perhaps the 0-9 could be removed?
> 
> David

-- 
"The reasonable man adapts himself to the world; the
unreasonable one
persists in trying to adapt the world to himself.  Therefore
all progress
depends on the unreasonable man." - George Bernard
Shaw
http://www.ChaosReigns.com


-- 
Unsubscribe mailto:postgrey-requestlist.ee.ethz.ch?subject=unsubscribe
Archive     http://lists.ee.ethz
.ch/postgrey
WebAdmin    http://lists.ee.ethz
.ch/lsg2.cgi