On 6/8/2017 9:06 AM, Bill Cole wrote:
This sample does not produce the error for me using a patched SA 3.4.1
Concur. I believe the issue at hand is duplicated bugs that confuse
thing but I've considered this patched for a decently long time.
On 7 Jun 2017, at 22:52, Philip Prindeville wrote:
I’m still seeing this now.
And yes, for spamhaus. And yes, $ip is being passed in as ‘(‘.
It should be possible to get a stack trace and figure out why it’s
being passed in as that value...
Are we any closer to having a fix for this?
I’m still seeing this now.
And yes, for spamhaus. And yes, $ip is being passed in as ‘(‘. It should be
possible to get a stack trace and figure out why it’s being passed in as that
value...
Are we any closer to having a fix for this?
I’m leaving a file here:
Hello Kevin,
Thanks for your hint.
Yes it seemed to be caused by the DNS cache.
Resetting it solved the problem for the user.
However wouldn’t it be better to give a proper warning in such a case?
It’s really strange that a content like “(” is passed to “lookup_dnsbl_for_ip”.
Shoudn’t that be
Hello Kevin,
Yes, all occurrences we know are related to spamhaus.
And it does not happen for all messages. It only triggered by some messages.
One user gets the warnings for one kind of newsletter:
Here are the headers:
Return-Path: i...@xxx.yy
Delivered-To: a...@.cc
X-Spam-Checker-Version:
Is it only happening with spamhaus?
Regards,
KAM
On March 23, 2016 5:26:20 AM EDT, Support SpamAssassin
wrote:
>Hi,
>since we released our new SpamAssassin for Windows we get some reports
>of users having these warnings in their spamd log:
>
>Thu Mar 17 11:31:21
Hi,
since we released our new SpamAssassin for Windows we get some reports of users
having these warnings in their spamd log:
Thu Mar 17 11:31:21 2016 [-2876] warn: Use of uninitialized value $4 in
concatenation (.) or string at Mail/SpamAssassin/Plugin/URIDNSBL.pm line 1042.
Thu Mar 17