https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8046
--- Comment #2 from RvdH ---
And not only when send through localhost, especially with 4.x using geodb both
X-Spam-ASN and X-Spam-Relay-Country can return null or empty values using the:
Lite (free) MaxMind mmdb versions (GeoLite2-ASN.mmdb,
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8046
--- Comment #4 from RvdH ---
returning a empty string should be better (in my opinion) then returning _ASN_
_ASNCIDR_, as it may look like something is broken, eg: like
X-Spam-Relay-Country
Might be i am, or you think i am nitpicking here
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #11 from Sidney Markowitz ---
Created attachment 5819
--> https://bz.apache.org/SpamAssassin/attachment.cgi?id=5819=edit
patch to make default for pyzor_fork and razor_fork 0 on Windows. Mention in
perldoc
Here's a proposed
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8046
--- Comment #7 from RvdH ---
To bad...as ASN_EXISTS seems to return the proper value, eg: true or false
exists:X-ASN is false for a message send through localhost for example
--
You are receiving this mail because:
You are the assignee
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8046
--- Comment #5 from RvdH ---
I think something like this should/could work... check on X-ASN metadata
for 4.x
header ASN_EXISTS exists:X-ASN
if (can(Mail::SpamAssassin::Plugin::ASN::has_check_asn) && ASN_EXISTS)
add_header all
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8043
--- Comment #10 from Sidney Markowitz ---
Created attachment 5818
--> https://bz.apache.org/SpamAssassin/attachment.cgi?id=5818=edit
patch to handle spamd launched with gid of supplemental group instead of
primary group
In deciding
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #13 from RvdH ---
Perl 5.03 (as that was what the orginal JAM Windows version was build with)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8046
Henrik Krohns changed:
What|Removed |Added
CC||apa...@hege.li
--- Comment #3 from
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #10 from RvdH ---
Got another error just now
Thu Sep 15 14:45:40 2022 [-4780] info: spamd: connection from server.com
[127.0.0.1]:50699 to port 783, fd 6
Thu Sep 15 14:45:40 2022 [-4780] info: spamd: processing message
for
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #12 from Sidney Markowitz ---
(In reply to RvdH from comment #10)
> Your vendor has not defined Socket macro MSG_DONTWAIT
Which version of perl are you running?
--
You are receiving this mail because:
You are the assignee for
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #9 from Henrik Krohns ---
(In reply to Sidney Markowitz from comment #7)
> (In reply to Henrik Krohns from comment #5)
> > The fork() limitations are well documented for Windows:
> > https://perldoc.perl.org/perlfork
> >
> > As
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #14 from RvdH ---
Hold on, think i might be responsible for that error, was testing some things
Henrik says are impossible to do, see
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8046
--
You are receiving this mail
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8043
--- Comment #11 from Marcel ---
Sidney I've confirmed that the patch fixes the warnings I was seeing when
restarting Amavis with SpamAssassin 4. Thanks!
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #15 from RvdH ---
(In reply to RvdH from comment #10)
> Got another error just now
>
> Thu Sep 15 14:45:40 2022 [-4780] info: spamd: connection from server.com
> [127.0.0.1]:50699 to port 783, fd 6
> Thu Sep 15 14:45:40
Hello wiki admins,
I saw a link to defunct project OpenProtect in the wiki and wanted to
remove it. I made an account but don’t see an edit button.
Is editing the wiki not allowed? Do you want to remove the references to
OpenProtect?
Cheers,
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
Sidney Markowitz changed:
What|Removed |Added
CC||sid...@sidney.com
--- Comment
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #16 from RvdH ---
Appears Windows don't have MSG_DONTWAIT, so looks like a need to switch socket
into non-blocking mode, example:
https://github.com/p5-RedisDB/RedisDB/blob/master/lib/RedisDB.pm#L423-L442
--
You are receiving
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #17 from RvdH ---
I'm not much of a perl coder, so if anyone can update/patch 4.0.0rc2
DnsResolver.pm (which introduced MSG_DONTWAIT, as this is not in 3.4.x) to
include the workaround suggested in the RedisDB example posted
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #19 from Sidney Markowitz ---
(In reply to RvdH from comment #17)
>I am more than happy to test it
Ruud, could you update the wiki instructions on building spamd on Windows to
include whatever you did to build it? That way I
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #18 from Sidney Markowitz ---
Henrik, flush_responses in DnsResolver.pm is your code and I'm not that
familiar with socket stuff. I have confirmed that MSG_DONTWAIT doesn't exist in
Windows perl versions. As a macro, it looks
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #8 from Sidney Markowitz ---
(In reply to RvdH from comment #6)
> FYI, I tried to build my own Windows version, but build instructions for
> Windows all seem outdated, and couldn't make it work so i gave up on that.
We haven't
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8046
--- Comment #6 from Henrik Krohns ---
(In reply to RvdH from comment #5)
> I think something like this should/could work... check on X-ASN metadata
>
> for 4.x
>
> headerASN_EXISTS exists:X-ASN
> if
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
Sidney Markowitz changed:
What|Removed |Added
Severity|normal |blocker
Target
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
Sidney Markowitz changed:
What|Removed |Added
Attachment #5820|0 |1
is obsolete|
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #20 from Sidney Markowitz ---
Created attachment 5820
--> https://bz.apache.org/SpamAssassin/attachment.cgi?id=5820=edit
MSG_DONTWAIT workaround for Windows in DnsResolver
Henrik, I decided to take a shot at it anyway, but
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
Sidney Markowitz changed:
What|Removed |Added
Attachment #5821|0 |1
is obsolete|
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #23 from Sidney Markowitz ---
And, even more mistakes... I ran tests on Windows that I thought exercised the
code, then discovered that it only did enough to fid compilation errors. v3
coming up after I complete real tests on
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #6 from RvdH ---
(In reply to Henrik Krohns from comment #5)
> The fork() limitations are well documented for Windows:
> https://perldoc.perl.org/perlfork
>
> As we now have a real tester with results, it might be prudent to
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=5615
Sidney Markowitz changed:
What|Removed |Added
Resolution|--- |WORKSFORME
CC|
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8046
Bug ID: 8046
Summary: X-Spam-ASN header added without successful ASN lookup
Product: Spamassassin
Version: 4.0.0
Hardware: PC
OS: Windows 10
Status: NEW
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8046
RvdH changed:
What|Removed |Added
CC||ruud.vd.h...@gmail.com
--- Comment #1 from
31 matches
Mail list logo
