Hi Scott,
Your question is timely. When you posted that, I wasn't aware of
problems with t/spamd_client.t, but now I have enough examples that it
is the next failure case I'm tracking down. Can you email me directly
(don't have to do the detailed back and forth to the entire mailing
list)
Hi,
Any updates on this ?
Tnx, Tuc
On Tue, Apr 9, 2024 at 6:24 PM Scott Ellentuch wrote:
> Hi,
>
> Yes, as ec2-user running the make and then make test ends up failing.
> There are no issues with the port as a previous tcpdump has shown, it
> transfers data back and forth. It gets through
Hi,
Yes, as ec2-user running the make and then make test ends up failing. There
are no issues with the port as a previous tcpdump has shown, it transfers
data back and forth. It gets through some of the tests and then it sends a
RST. Amazon only goes as far as spamassassin-3.4.3 in Amazon Linux 2
Scott Ellentuch wrote on 10/04/24 5:15 am:
Apologies, but I don't understand.
I am running "make test" as the AWS user "ec2-user" when getting these
errors. Are you saying that its an acceptable error right now, and I can
just do the "sudo make install"?
If you ran "make test" as user
Apologies, but I don't understand.
I am running "make test" as the AWS user "ec2-user" when getting these
errors. Are you saying that its an acceptable error right now, and I can
just do the "sudo make install"?
Thanks, Tuc
On Fri, Apr 5, 2024 at 9:58 PM Sidney Markowitz wrote:
> Scott
Scott Ellentuch wrote on 4/04/24 9:43 am:
File attached. However, I don't see any smoking gun.
I've verified the problem. I ran sudo make test in a directory tree in
/tmp with world r-x access, and got the error in t/spamd_client.t as
well as in t/spamc_optL.t. I don't know why you didn't
Loren Wilton wrote on 4/04/24 9:26 pm:
Would it be worth adding some sort of test for this kind of thing
I started to look at where in SATest.pm it ought to go, and I found
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=5529
I think from the comments I left there 17 years ago that is is
I haven't had a chance yet to read this thread carefully, but spamd when
run as root in tests will, at least in some cases, set itself to run as
user "nobody". If you do that in a subdirectory of your non-nobody user's
HOME, the usual permission configuration will not provide read access to
I haven't had a chance yet to read this thread carefully, but spamd when
run as root in tests will, at least in some cases, set itself to run as
user "nobody". If you do that in a subdirectory of your non-nobody
user's HOME, the usual permission configuration will not provide read
access to
File attached. However, I don't see any smoking gun.
Nothing in t/log
[ec2-user@ip-172-31-131-251 Mail-SpamAssassin-4.0.1]$ ls -lR t/log
t/log:
total 0
Nothing big in iptables
[ec2-user@ip-172-31-131-251 Mail-SpamAssassin-4.0.1]$ sudo iptables -L
Chain INPUT (policy ACCEPT)
target prot opt
On 2024-04-03 at 14:01:44 UTC-0400 (Wed, 3 Apr 2024 14:01:44 -0400)
Scott Ellentuch
is rumored to have said:
Hi,
Ok, deleted the directory and started again.
Test Summary Report
---
t/spamd_client.t(Wstat: 26624 Tests: 4 Failed: 0)
Non-zero exit status: 104
Hi,
Ok, deleted the directory and started again.
Test Summary Report
---
t/spamd_client.t(Wstat: 26624 Tests: 4 Failed: 0)
Non-zero exit status: 104
Parse errors: Bad plan. You planned 52 tests but ran 4.
Files=217, Tests=3765, 890 wallclock secs ( 1.21 usr
On 2024-04-02 at 18:18:09 UTC-0400 (Tue, 2 Apr 2024 18:18:09 -0400)
Scott Ellentuch
is rumored to have said:
Hi,
Trying to install SA 4.0.1 from scratch. Tried via CPAN, that didn't
go
well, so trying from tarball. (Enabled SSL when doing Makefile.PL)
NEVER run 'make' as root except when
Hi,
Trying to install SA 4.0.1 from scratch. Tried via CPAN, that didn't go
well, so trying from tarball. (Enabled SSL when doing Makefile.PL)
I'm on Amazon Linux 2 , 4.0.1 SA, and not sure what other info I can give.
I installed every perl module it wanted.
The final summary is -
Test Summary
14 matches
Mail list logo
