On 08/13/2013 12:09 PM, BC wrote:
>
>
> Gulp. Could I be spamming myself?
>
>
> On 8/13/2013 11:00 AM, spamdyke-users-requ...@spamdyke.org wrote:
>> It looks like the originating IP address was 127.0.0.1, which is your
>> server. In other words, this log entry is for a message that was generated
> I suppose the cleverest thing would be for someone to host an RHSBL based on
> results from the script
Sam - that should be no problem, we could do this.
Data should be an ascii file in rhsbl formt.
Feel free to contact me directly..
___
spamdyke-
Gulp. Could I be spamming myself?
On 8/13/2013 11:00 AM, spamdyke-users-requ...@spamdyke.org wrote:
> It looks like the originating IP address was 127.0.0.1, which is your server.
> In other words, this log entry is for a message that was generated by
> something on your server. The reject
I would not blanket whitelist providers by the rDNS names -- those names are
too easy to fake. I can set the rDNS on my servers to anything I want; that's
why SPF and DKIM were created.
-- Sam Clippinger
On Aug 13, 2013, at 10:37 AM, Gary Gendel wrote:
> Sam,
>
> This sounds like a good i
Sam,
This sounds like a good idea. Unfortunately I have limited bandwidth to
offer an RHSBL service on my domain.
I currently have the big providers whitelisted from their RDNS but still
run all emails through spamassassin. Is this a bad idea and should I
have these configured differently?
I don't update mine very often at all; I think I've only added a couple within
the last year. (Some of the original scripts I wrote in 2007 still catch sites
today -- I guess spammers just don't update their websites.) I could post my
current filters somewhere if you'd like to see them, but I
Sam,
I just started playing with your hunter-seeker script. Is there a
repository where the latest hunter-seeker filters can be downloaded? I
don't know how often you and others update them, but new filters would
be a nice thing to share. Also, any unblacklistable domains that have
been coll
