> On Feb 16, 2018, at 4:41 PM, John Hardin wrote:
>
> Not necessarily safe. If your MTA receives a message without a Message-ID, it
> is supposed to generate one. And if it does so, it will probably do so using
> your (recipient) domain...
Wouldn't this also FP on messages internal to the doma
On Fri, 16 Feb 2018, Michael Storz wrote:
Am 2018-02-15 19:27, schrieb David Jones:
We have covered this issue a few times recently on this list but I
don't think anything definitive was ever decided or recommended to
detect and block this sort of spoofing:
https://pastebin.com/juXLD8vr
This
On 2/16/2018 12:57 PM, Alex wrote:
I think it's a mistake to whitelist (or even deduct significant
points) based on a header that can be controlled by a spammer.
We see tons of spam that has properly crafted MIDs. If you're using
procmail, it sounds like this is on a personal account, so perhaps
Hi list
I'm looking for a way in spamassassin to run a full-uri-host rbl lookup
for a specific rule. I do not want to discuss about sense or non-sense
of full-uri-hosts lookups ;-)
lets assume I have two rules which query my own rbl
urirhssub HIT_DOMAINmy.rbl.tld. A 127.0.0.2
bodyHIT
Hi,
On Fri, Feb 16, 2018 at 12:41 PM, Kenneth Porter wrote:
> I just put this into service. I'm white-listing mailing lists. Most go to
> their own folder via procmail filtering, and unrecognized ones go to the
> folder Lists/Unknown until I write a procmail rule. But this rule should
> catch laz
On 02/16/2018 02:40 PM, Michael Storz wrote:
Am 2018-02-15 19:27, schrieb David Jones:
We have covered this issue a few times recently on this list but I
don't think anything definitive was ever decided or recommended to
detect and block this sort of spoofing:
https://pastebin.com/juXLD8vr
Thi
Am 2018-02-15 19:27, schrieb David Jones:
We have covered this issue a few times recently on this list but I
don't think anything definitive was ever decided or recommended to
detect and block this sort of spoofing:
https://pastebin.com/juXLD8vr
This appears to be a spoofed email from a comprom
I just put this into service. I'm white-listing mailing lists. Most go to
their own folder via procmail filtering, and unrecognized ones go to the
folder Lists/Unknown until I write a procmail rule. But this rule should
catch lazy abusers. After a bit more experience I'll crank up the
punishmen
On 2/16/2018 1:24 AM, Gianluca Furnarotto wrote:
Hi Bill,
this is the result of the command you suggested to type:
feb 16 07:21:09.678 [21824] warn: Use of uninitialized value $_[1] in
hash eleme
nt at Mail/SpamAssassin/Conf/Parser.pm line 571, line 717.
Good call, Bill. Sounds like a mis
