Search found 3504 matches

by shawniverson
25 Nov 2021 21:57
Forum: 4.x Bugs
Topic: Detected and have disarmed denialofservice tags in HTML message
Replies: 15
Views: 1818

Re: Detected and have disarmed denialofservice tags in HTML message

Got confirmation that the issue is not resolved. I have refactored and am implementing a fix for eFa-4.0.4-26. I'll post once it is ready.
by shawniverson
25 Nov 2021 21:54
Forum: 4.x Bugs
Topic: Detected and have disarmed denialofservice tags in HTML message
Replies: 15
Views: 1818

Re: Detected and have disarmed denialofservice tags in HTML message

Looks like dl7 is lagging behind, let me force an rsync...
by shawniverson
25 Nov 2021 20:40
Forum: 4.x Bugs
Topic: Detected and have disarmed denialofservice tags in HTML message
Replies: 15
Views: 1818

Re: Detected and have disarmed denialofservice tags in HTML message

Please let me know if you are still seeing this behavior on eFa-4.0.4-25. I stopped closing the pipe in the child to prevent the case of a double close on the pipe (Signal 13 will happen when the pipe no longer exists, which I'm convinced is happening here). If it is still happening, I will need to ...
by shawniverson
22 Nov 2021 12:57
Forum: Discussion
Topic: Could not open file
Replies: 58
Views: 2754

Re: Could not open file

Got the changes in production. Thanks for your help!
by shawniverson
22 Nov 2021 12:17
Forum: Discussion
Topic: Could not open file
Replies: 58
Views: 2754

Re: Could not open file

Glad to hear it! I will release this to the production repos. I'll let you know when that happens so you can switch back, if desired.
by shawniverson
22 Nov 2021 11:54
Forum: Discussion
Topic: Unable to install eFa4 on Centos 7
Replies: 8
Views: 1486

Re: Unable to install eFa4 on Centos 7

Looks like the system didn't initialize completely. You are getting a lot of permission denied. First thing to check is SELinux, set to permissive temporarily and see if it helps any. sudo setenforce 0 Next thing would be to confirm that the password for the custom functions is working for MySQL/Mar...
by shawniverson
22 Nov 2021 02:41
Forum: Discussion
Topic: Could not open file
Replies: 58
Views: 2754

Re: Could not open file

Got the repos updated. Please test when you get a chance. Includes the latest unfold logic and improved relay stat handling for multiple recipients with the same messsage-id.

Code: Select all

sudo yum clean all
sudo yum update
by shawniverson
22 Nov 2021 00:45
Forum: Discussion
Topic: Could not open file
Replies: 58
Views: 2754

Re: Could not open file

Got some sweet patches for MailWatch for testing. I'll get them in the repo. I *think* I have the multiple recipients issue with the relay data resolved as well.
by shawniverson
21 Nov 2021 18:04
Forum: Discussion
Topic: ClamAV Status - Known virus
Replies: 2
Views: 142

Re: ClamAV Status - Known virus

I thought I was the only one that notices these things :lol:

I'm not sure why it is so different and so much smaller, but let me do some digging.
by shawniverson
21 Nov 2021 17:57
Forum: Discussion
Topic: Could not open file
Replies: 58
Views: 2754

Re: Could not open file

Great work on the unfolding, I knew there were problems with the initial logic, I appreciate the help in debugging this. I will get this code into the test repo today and work on a strategy for dealing with multiple, separate recipients with the same message-id.
by shawniverson
21 Nov 2021 17:55
Forum: Discussion
Topic: Could not open file
Replies: 58
Views: 2754

Re: Could not open file

To answer your question about autoupdate, on CentOS7 yum-cron is in use. iirc, there's a setting /etc/yum.conf you can toggle to disable the autoupdate.
by shawniverson
20 Nov 2021 07:03
Forum: 4.x Bugs
Topic: eFa4.repo error
Replies: 1
Views: 121

Re: eFa4.repo error

Yeah looks like that parameter is no longer a thing.
by shawniverson
18 Nov 2021 20:18
Forum: Discussion
Topic: Could not open file
Replies: 58
Views: 2754

Re: Could not open file

I did see a tiny thing I should tweak in the unfolding that may help. I need to use \s instead of a literal space for any unfolding and string matching in the lines, so I will adjust that and update it as well.
by shawniverson
17 Nov 2021 16:31
Forum: Feature Requests
Topic: Rocky Linux 8
Replies: 5
Views: 4084

Re: Rocky Linux 8

Coming right up, I'll make the necessary changes.
by shawniverson
17 Nov 2021 14:55
Forum: 4.x Bugs
Topic: EFA monitor stopped
Replies: 1
Views: 120

Re: EFA monitor stopped

I have fixes in testing for this issue. They'll be released soon.
by shawniverson
17 Nov 2021 13:56
Forum: Discussion
Topic: Could not open file
Replies: 58
Views: 2754

Re: Could not open file

Got the testing repo updated properly. You should be able to test again. Still work to do, but this will have the unfolding logic.

Before you run the update, back up your customizations to /usr/share/MailScanner/perl/custom/MailWatch.pm

Code: Select all

sudo yum clean all
sudo yum update
by shawniverson
16 Nov 2021 14:47
Forum: Discussion
Topic: Could not open file
Replies: 58
Views: 2754

Re: Could not open file

In a wonderful world it would associate each relay info to it's corresponding maillog entry :) I'm not sure I'm explaining the issue well... This is a good explanation, and yes, this is another issue. It appears that in addition to the message-id I am going to need to find a way to capture the reci...
by shawniverson
16 Nov 2021 14:44
Forum: Discussion
Topic: Could not open file
Replies: 58
Views: 2754

Re: Could not open file

r00tsh3ll wrote:
16 Nov 2021 04:00
In which file is the message-id extraction logic so I can check how we're doing it now ?
I must have pushed the update out without the code change. Let me double check. I just noticed the changes weren't present on my host either.
by shawniverson
16 Nov 2021 01:39
Forum: Discussion
Topic: Could not open file
Replies: 58
Views: 2754

Re: Could not open file

Clear your repos and update to get this the fix for the first one:

Code: Select all

sudo yum clean all
sudo yum update
by shawniverson
16 Nov 2021 00:50
Forum: Discussion
Topic: Could not open file
Replies: 58
Views: 2754

Re: Could not open file

Got some time to work on this. Actually both are real issues, so let me study this. The first one I'll get patched first so you can see how it goes.
by shawniverson
15 Nov 2021 18:54
Forum: Discussion
Topic: Could not open file
Replies: 58
Views: 2754

Re: Could not open file

Yes indeed, this will be simple to resolve. Let me get this code updated to support line continuations so we can test it.
by shawniverson
15 Nov 2021 18:00
Forum: Discussion
Topic: Could not open file
Replies: 58
Views: 2754

Re: Could not open file

This is the pattern to match the message-id:

Code: Select all

if ( $_ =~ /^message-id: (\S+)$/i ) {
   $messageid = $1;
Like you, I'm wondering if this pattern isn't matching in all cases.
by shawniverson
15 Nov 2021 15:24
Forum: Discussion
Topic: Could not open file
Replies: 58
Views: 2754

Re: Could not open file

These messages may really not have a message identifier in the header, so I think reworking the code to suppress the notices would be appropriate. The message id is used to correlate the smtp identifiers for relay statistics between postfix and the milter. It is informational only. If you have a sam...
by shawniverson
15 Nov 2021 12:00
Forum: Discussion
Topic: Could not open file
Replies: 58
Views: 2754

Re: Could not open file

What worries me a bit: ERROR 1292 (22007) at line 46: Incorrect datetime value: '1970-01-01 00:00:01' for column ``.``.`lastsent` at row 1 This error is benign, the DMARC schema update tries to set the default datetime. For some reason your database isn't allowing that. I'll check into it, probably...