Hmm, I think maybe there shouuld be options for delaying to be just that 
and no more. For instance even if some ip spams me but they do retry, 
there is no point in greylisting them but I might still want the full 
spam checks...



On 10/23/2009 11:45 AM, Thomas Eckardt/eck wrote:
> If 'nodelay' than
>
> - nodamping
> - SMTPdomainIP
> - DoFrequencyIP
> - no MessageID check
> - no RBL check
> - no PBExtreme
> - no add to PB (black or whire)
>
>
> The whitebox entry was there before !
>
> nodelay  acts in some subs like a 'seems to be white'
>
> Thomas
>
>
>
>
>
>
> "GrayHat"<gray...@gmx.net>
> 23.10.2009 10:18
> Bitte antworten an
> GrayHat<gray...@gmx.net>; Bitte antworten an
> ASSP development mailing list<assp-test@lists.sourceforge.net>
>
>
> An
> <assp-test@lists.sourceforge.net>
> Kopie
>
> Thema
> [Assp-test] Delaying question
>
>
>
>
>
>
>
> I added the IP of some "clustered mailservers"
> to the "noDelay" list thinking that it would ONLY
> act on the delay behaviour, but it turns out that
> it's probably doing more than just that, at least
> judging from a *spam* message which got
> through and contained the following headers
>
> X-OriginalArrivalTime: 22 Oct 2009 19:24:35.0970 (UTC)
> FILETIME=[4A6C9E20:01CA534D]
> X-Assp-Delay: not delayed (85.37.16.7 in whitebox ); 22 Oct 2009
>   21:24:46 +0200
> X-Assp-Message-Score: -15 (In Penalty White Box)
> X-Assp-Received-SPF: neutral ip=85.37.16.7 mailfrom=happyisl...@email.it
>   helo=smtpout09.attiva.biz
> X-Assp-Message/IP-Score: 5 (SPF neutral)
> X-Assp-Envelope-From: happyisl...@email.it
>
> now... why it's telling me that the IP is in "whitebox"
> while it should just be a "nodelay" ? Or is the "nodelay"
> list ALSO working as some kind of whitebox ? That
> sounds crazy to me, I thought the nodelay was just
> a mean to avoid delaying messages from known
> email servers not to tell ASSP that those servers
> are somewhat "whitelisted"
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Assp-test mailing list
> Assp-test@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/assp-test
>
>
>
>
> DISCLAIMER:
> *******************************************************
> This email and any files transmitted with it may be confidential, legally
> privileged and protected in law and are intended solely for the use of the
>
> individual to whom it is addressed.
> This email was multiple times scanned for viruses. There should be no
> known virus in this email!
> *******************************************************
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Assp-test mailing list
> Assp-test@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/assp-test
>
>
>    


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to