Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Wiki Markup
    I dont't like the idea at all, but \[http://loaf.cantbedone.org/ LOAF\] might be worth looking into, too.
  • JustinMason: big problem in my opinion is that the LOAF files are attached to each mail sent. bulky and messy!
  • MalteStretz: ACK, thats what I dont like about it, too.

Geo info

  • Wiki Markup
    \[http://www.corante.com/many/archives/2004/03/19/loaf_social_email_filtering.php This\] posting about LOAF made me think that it might be possible to use a website's published Geo information (how near am I geographically to the sender).
  • JustinMason: several spammers live near me!
  • MalteStretz: but they probably won't publish Geo records (smile) and if they start to do (probably not targeted ones but ones from high density urban areas), this rule won't work for you but maybe for people living at uncommon places

Querying Addressbooks

  • Wiki Markup
    I already implemented a \[http://msquadrat.de/archive/04/03/22/01 quick hack\] for to query my KAddressbook from KMail for whitelisting.  What about querying LDAP servers?
  • JustinMason: see also 'Using From For Whitelisting Problems' below

...

  • use IP address info from the Received headers or the last untrusted relay, and combine that with the address to come up with a combined email-and-ip address, similar to how the AutoWhitelist does it.
  • require that any whitelisted address be on a domain that publishes SPF records.
  • MalteStretz: cross-checking against SPF for entries for which no routing information is avaliable (ie. addressbook entries etc) is a good idea. another possibility to avoid some FPs could be to exclude all domains which are equal to the recipient's one