https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #59 from RvdH ---
(In reply to Bill Cole from comment #58)
> (In reply to RvdH from comment #57)
> > No crash but something i noticed as soon as i turned off --debug logging
> >
> > warn: plugin: eval failed:
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
Bill Cole changed:
What|Removed |Added
CC||billc...@apache.org
--- Comment #58
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #57 from RvdH ---
No crash but something i noticed as soon as i turned off --debug logging
warn: plugin: eval failed: __alarm__ignore__(532/::PerMsgStatus::check/2063)
Fri Sep 23 13:29:23 2022 [-4728] info: spamd: connection
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #56 from Henrik Krohns ---
(In reply to RvdH from comment #55)
> Can i still ask questions when possible issues with 4.0.0-rc2 arise on
> Windows?
>
> When running with --debug is see a line, like:
> Mon Sep 19 11:55:18 2022
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #55 from RvdH ---
Can i still ask questions when possible issues with 4.0.0-rc2 arise on Windows?
When running with --debug is see a line, like:
Mon Sep 19 11:55:18 2022 [4276] dbg: eval: failed to locate the triplets.txt
file
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
Sidney Markowitz changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #53 from Henrik Krohns ---
(In reply to RvdH from comment #52)
> Henrik are going to make a separate bug concerning the global_state_dir on
> Windows?
Bug #8050
--
You are receiving this mail because:
You are the assignee for
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #52 from RvdH ---
(In reply to Henrik Krohns from comment #41)
> (In reply to RvdH from comment #40)
> > For global_state_dir that is :-)
>
> Yes portable_getpwuid should not return home for all users.
>
> There is no
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #51 from Sidney Markowitz ---
(In reply to Loren Wilton from comment #49)
> All of these methods allow passing parameters to spamd, and setting the home
> directory for spamd.
I'll include all these suggestions in the wiki page
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #50 from RvdH ---
(In reply to RvdH from comment #48)
> M, OK
> Although executables are preferred, especially for spamd.exe to be able to
> make it run like a service using something like nssm, https://nssm.cc/usage
>
>
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
Loren Wilton changed:
What|Removed |Added
CC|lwil...@earthlink.net |
--
You are receiving this mail
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
Loren Wilton changed:
What|Removed |Added
CC||lwil...@earthlink.net
--- Comment
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #48 from RvdH ---
M, OK
Although executables are preferred, especially for spamd.exe to be able to make
it run like a service using something like nssm, https://nssm.cc/usage
How did the people at JAM Software create those
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #47 from Sidney Markowitz ---
(In reply to RvdH from comment #46)
And is is it worth to also have sa-compile as executable? (JAM also lacks
> this)
All the executables except spamc are perl scripts, which on Unix and macOS the
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #46 from RvdH ---
Ah, that explains...I tried to build with nmake like the wiki said, I will try
your build instructions tomorrow (if I have the time)
JAM package also has executables for sa-learn and sa-update, how did they
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
Sidney Markowitz changed:
What|Removed |Added
Target Milestone|4.0.0 |Undefined
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #45 from Sidney Markowitz ---
I've created bug 8047 "MSG_DONTWAIT error in DnsResolver on Windows" with v4
corrected patch ready for voting.
And bug 8048 "Make default setting for *_fork config options 0 on Windows" with
the
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #44 from Sidney Markowitz ---
(In reply to Henrik Krohns from comment #38)
> > version 3, now with fewer typos!
>
> I think the logic has bug..
..
> Both should be unless(RECV_FLAGS) so the blocking is correctly unset and set?
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #43 from RvdH ---
(In reply to RvdH from comment #42)
> (In reply to Henrik Krohns from comment #41)
> > (In reply to RvdH from comment #40)
> > > For global_state_dir that is :-)
> >
> > Yes portable_getpwuid should not return
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #42 from RvdH ---
(In reply to Henrik Krohns from comment #41)
> (In reply to RvdH from comment #40)
> > For global_state_dir that is :-)
>
> Yes portable_getpwuid should not return home for all users.
>
> There is no
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #41 from Henrik Krohns ---
(In reply to RvdH from comment #40)
> For global_state_dir that is :-)
Yes portable_getpwuid should not return home for all users.
There is no ALLUSERSAPPDATA set on my Windows.
I do have
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #40 from RvdH ---
(In reply to RvdH from comment #39)
> (In reply to Henrik Krohns from comment #35)
> > I see ArchiveIterator.pm has it's own workarounds
> >
> > # No $HOME set? Try to find it, portably.
> >
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #39 from RvdH ---
(In reply to Henrik Krohns from comment #35)
> I see ArchiveIterator.pm has it's own workarounds
>
> # No $HOME set? Try to find it, portably.
> unless ($home) {
> if
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #38 from Henrik Krohns ---
(In reply to Sidney Markowitz from comment #24)
> Created attachment 5822 [details]
> MSG_DONTWAIT workaround for Windows in DnsResolver, v3
>
> version 3, now with fewer typos!
I think the logic has
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #37 from RvdH ---
(In reply to Henrik Krohns from comment #35)
> Sorry this bug starts to get messy with multiple problems and patches.
> Hopefully Sidney or someone can sort these out to maybe own bugs for easier
> voting.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #36 from RvdH ---
(In reply to RvdH from comment #34)
> default = user home
>
> FYI, when not specified, user home on Windows automatically uses:
> C:\Windows\System32\config\systemprofile
>
> This can problematic with windows
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #35 from Henrik Krohns ---
I see ArchiveIterator.pm has it's own workarounds
# No $HOME set? Try to find it, portably.
unless ($home) {
if (!Mail::SpamAssassin::Util::am_running_on_windows()) {
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #34 from RvdH ---
default = user home
FYI, when not specified, user home on Windows automatically uses:
C:\Windows\System32\config\systemprofile
This can problematic with windows updates (i had this in the past with 3.4.x)
as
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #33 from Henrik Krohns ---
To clarify, global state dir was created to be able to keep state for things at
highest possible shared level across SA processes. Currently it's only used for
dns_block_rule state files (for example
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #32 from Henrik Krohns ---
(In reply to RvdH from comment #31)
> when running spamassassin --lint --debug a folder "C:\.spamassassin" is
> created automatically, eg:
> Sep 14 23:23:52.629 [3804] dbg: config: global_state_dir set
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #31 from RvdH ---
when running spamassassin --lint --debug a folder "C:\.spamassassin" is created
automatically, eg:
Sep 14 23:23:52.629 [3804] dbg: config: global_state_dir set to \\.spamassassin
What is this new
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #30 from RvdH ---
(In reply to RvdH from comment #29)
> (In reply to Sidney Markowitz from comment #27)
> > (In reply to RvdH from comment #25)
> > > patched my way around it using "Jam Software
> > > SpamAssassin for Windows
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #29 from RvdH ---
(In reply to Sidney Markowitz from comment #27)
> (In reply to RvdH from comment #25)
> > patched my way around it using "Jam Software
> > SpamAssassin for Windows 3.4.4" download as base.
>
> Oh, so you just
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #28 from RvdH ---
needed:
- SpamAssassinForWindows-v3.4.4-x64.zip
- strawberry-perl-5.30.0.1-64bit.msi
=
perl -MCPAN -e shell
install Archive::Zip
force install
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #27 from Sidney Markowitz ---
(In reply to RvdH from comment #25)
> patched my way around it using "Jam Software
> SpamAssassin for Windows 3.4.4" download as base.
Oh, so you just use their exe and substituted the current
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #26 from RvdH ---
(In reply to Sidney Markowitz from comment #24)
> Created attachment 5822 [details]
> MSG_DONTWAIT workaround for Windows in DnsResolver, v3
>
> version 3, now with fewer typos!
Have applied the patch and am
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #25 from RvdH ---
@Sidney
As mentioned earlier in this topic i haven't been able to successfully build a
Windows version myself but patched my way around it using "Jam Software
SpamAssassin for Windows 3.4.4" download as base.
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
Sidney Markowitz changed:
What|Removed |Added
Attachment #5820|0 |1
is obsolete|
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
--- 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
--- 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 #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 #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 #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
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=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=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 #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=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 #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 #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=8044
Sidney Markowitz changed:
What|Removed |Added
CC||sid...@sidney.com
--- Comment
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=8044
--- Comment #5 from Henrik Krohns ---
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 set all
*_fork defaults as 0 on Windows.
--
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
Kevin A. McGrail changed:
What|Removed |Added
CC||kmcgr...@apache.org
--- Comment
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
--- Comment #3 from RvdH ---
(In reply to Henrik Krohns from comment #1)
> Perhaps try "razor_fork 0" setting if it makes a difference. Default forks a
> parallel process, maybe something funky there.
razor_fork 0 seems to fix this issue
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
RvdH changed:
What|Removed |Added
CC||ruud.vd.h...@gmail.com
--- Comment #2 from
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8044
Henrik Krohns changed:
What|Removed |Added
CC||apa...@hege.li
--- Comment #1 from
61 matches
Mail list logo
