-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John Kelly writes:
>I'm still confused after following this thread and reading the manuals.
>
>I also get some of these FPs.  Should my local.cf have these entries:
>
>trusted_networks    192.168.200/24   <--  internal
>trusted_networks    81.6.xxx.xxx/29  <--  my public IPs
>
>or have I thoroughly misunderstood this?
>
>I assume that the checks start at the most recent hop (ie here), go back 
>until they can find a "trusted IP" and then check whether the next is in 
>dynablock.easynet.nl.  If a "trusted IP" cannot be found every IP is 
>checked in dynablock?

Nearly ;) 

it will go back through the Received hop list to the originator, and if
the IP listed is *not* trusted, then that hop, and everything after it, is
untrusted.

Adding those lines to local.cf would be a good idea.

- --j.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Exmh CVS

iD8DBQE/pvKbQTcbUG5Y7woRAriGAJ4+z5jCfYjVYP39NRGM2y9aqZQgRwCgk9lw
LG4mztOPcsuS3oJvllrlA0g=
=q89N
-----END PGP SIGNATURE-----



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to