Search found 30 matches
- 22 Nov 2021 03:46
- Forum: Discussion
- Topic: Could not open file
- Replies: 58
- Views: 23507
Re: Could not open file
Hey, thanks. I've updated the system and took a look at the changes and did some tests. It seems to handle multiple recipients flawlessly now. Great job :) It seems eFa now also includes my pull requests for the disable backup thing, thanks! I've checked a bit the maillog for Message-ID not extracte...
- 21 Nov 2021 18:19
- Forum: Discussion
- Topic: Could not open file
- Replies: 58
- Views: 23507
Re: Could not open file
Hey Shawn,
No problem. Thanks to you for all the work!
No problem. Thanks to you for all the work!
- 21 Nov 2021 05:47
- Forum: Discussion
- Topic: Could not open file
- Replies: 58
- Views: 23507
Re: Could not open file
Doesn't work if the Message-Id header is the last header (exits loop) Hello Shawnn, I finally had some time to debug a bit the message-id extraction logic. The first issue is that with the actual code, it will return an empty message-id if the Message-ID header is the last header. This happens more ...
- 20 Nov 2021 19:46
- Forum: Discussion
- Topic: Could not open file
- Replies: 58
- Views: 23507
Re: Could not open file
Hello shawn, a bit out of topic question but, how do we disable auto-update ? IIRC there was an option in the admin menu but it seems to be gone. I don't mind auto updates when using the production repo, but as we are currently on the testing repo while we sort some things out, I prefer to be around...
- 18 Nov 2021 17:02
- Forum: Discussion
- Topic: Could not open file
- Replies: 58
- Views: 23507
Re: Could not open file
Hello Shawn, Thank you for the repo update. I can see the unfolding logic in MailWatch.pm but unfortunately it doesn't seems to catch the folded message-id. I had not much time past days to take a deeper look but I'll add some debug output to it tomorrow to understand why it's not working. Kind rega...
- 16 Nov 2021 04:35
- Forum: Discussion
- Topic: Could not open file
- Replies: 58
- Views: 23507
Re: Could not open file
While we're at it, let me share another "issue" that I thihnk I've discovered with mailwatch_milter_relay.php. I'll try to explain it the best I can: Let's say an external mail is received and that mail has multiple recipients. I.E. user1@domainone.com, user2@domainone.com, user@domaintwo....
- 16 Nov 2021 04:00
- Forum: Discussion
- Topic: Could not open file
- Replies: 58
- Views: 23507
Re: Could not open file
Hmm after the update and restart, the issue still persists. MariaDB [mailscanner]> select messageid from maillog where id = '4HtXLp6B7jzVj4M6'; +-----------+ | messageid | +-----------+ | | +-----------+ That's a post-update processed message. In which file is the message-id extraction logic so I ca...
- 16 Nov 2021 03:50
- Forum: Discussion
- Topic: Could not open file
- Replies: 58
- Views: 23507
Re: Could not open file
Hey. Thanks. Update done. I'll let you know how it's going now with the multiline headers. For the 2nd case on my side, i've patched a bit the php file to skip processing the log entry if the message-id contains our e.f.a server name (myorigin). I noticed that the probes/bounces were using locally g...
- 15 Nov 2021 19:20
- Forum: Discussion
- Topic: Could not open file
- Replies: 58
- Views: 23507
Re: Could not open file
Okay, so for the messageid lookup "problem" by mailwatch_milter_relay.php: The first case seems when the message id is not identified from the headers (because of the line feeds) like discussed previously. The other case I have is because we enabled address verification in postfix: http://...
- 15 Nov 2021 18:58
- Forum: Discussion
- Topic: Could not open file
- Replies: 58
- Views: 23507
Re: Could not open file
Okay
By the way we are a bit out of topic of this thread that was about "Cannot open" issue, which seems to be fixed by the way. No new traces of it since the update to the test repo.
Maybe we should move all other stuff to another topic ?
By the way we are a bit out of topic of this thread that was about "Cannot open" issue, which seems to be fixed by the way. No new traces of it since the update to the test repo.
Maybe we should move all other stuff to another topic ?
- 15 Nov 2021 18:54
- Forum: Discussion
- Topic: Could not open file
- Replies: 58
- Views: 23507
Re: Could not open file
https://metacpan.org/pod/MIME::Head#Man ... d-contents
maybe using unfold function on the headers...
maybe using unfold function on the headers...
- 15 Nov 2021 18:35
- Forum: Discussion
- Topic: Could not open file
- Replies: 58
- Views: 23507
Re: Could not open file
Interresting, in the headers of the message where the message id is not extracted: Message-ID: <GVAP278MB0310DE2FC290B07EFC17D9BF9F989@GVAP278MB0310.CHEP278.PROD.OUTLOOK.COM> References: <0107017d233b1df7-ece4d4e1-fb2a-4ca4-9e69-c40aa4de4510-000000@eu-central-1.amazonses.com> <ZRAP278MB0173D46E2C469...
- 15 Nov 2021 15:35
- Forum: Discussion
- Topic: Could not open file
- Replies: 58
- Views: 23507
Re: Could not open file
If you received my PM you'll see that from postfix point of view it has a message ID. I noticed this often happens with messages from outlook.com though. The problem is that even if we silence the notice, it will keep retrying the same message for 1 minute (60x1 second loop). So it could delay a lot...
- 15 Nov 2021 15:27
- Forum: Discussion
- Topic: Could not open file
- Replies: 58
- Views: 23507
Re: Could not open file
I temporarily 'silenced' the PHP notices by adding @'s in front of the "offending" line @$smtpd_id = $result->fetch_row()[0]; and added some debug output (echoing the message_id and loop count). I send you a private message with the results for a message that is not found. I don't want to ...
- 15 Nov 2021 14:56
- Forum: Discussion
- Topic: Could not open file
- Replies: 58
- Views: 23507
Re: Could not open file
Hello Shawn, okay for the DMARC thing. For the /var/log/messages mailwatch_milter_relay.php PHP notices, I think this is only for specific cases when the messageid of a message stays blank, but I guess I need to understand why. There are a relatively a lot of entries with blank messageid and it's ra...
- 15 Nov 2021 06:51
- Forum: Discussion
- Topic: Could not open file
- Replies: 58
- Views: 23507
Re: Could not open file
For the PHP Notice, it seems it tries to lookup a message into table maillog using messageid column, but for some of the messages in the table, messageid is empty.
I can manually find the message in the table using the from_address, and for this message, messageid is blank.
I can manually find the message in the table using the from_address, and for this message, messageid is blank.
- 15 Nov 2021 06:12
- Forum: Discussion
- Topic: Could not open file
- Replies: 58
- Views: 23507
Re: Could not open file
However, /var/log/messages is filling with Nov 15 07:11:16 mx1 php: PHP Notice: Trying to access array offset on value of type null in /usr/bin/mailwatch/tools/Postfix_relay/mailwatch_milter_relay.php on line 120 Nov 15 07:11:16 mx1 php: Notice: Trying to access array offset on value of type null in...
- 15 Nov 2021 06:10
- Forum: Discussion
- Topic: Could not open file
- Replies: 58
- Views: 23507
Re: Could not open file
What worries me a bit:
Code: Select all
ERROR 1292 (22007) at line 46: Incorrect datetime value: '1970-01-01 00:00:01' for column ``.``.`lastsent` at row 1
- 15 Nov 2021 05:28
- Forum: Discussion
- Topic: Could not open file
- Replies: 58
- Views: 23507
Re: Could not open file
Okay, no problem. Thanks
- 15 Nov 2021 05:14
- Forum: Discussion
- Topic: Could not open file
- Replies: 58
- Views: 23507
Re: Could not open file
Hello, Thank you for the instruction. I have a question though. It seems our install is based on Centos 7 and the url to the testing repo mention Centos8. [root@mx1 yum.repos.d]# cat /etc/redhat-release CentOS Linux release 7.9.2009 (Core) Is that possible that when we first installed eFa 4 it was o...
- 14 Nov 2021 20:43
- Forum: Discussion
- Topic: Could not open file
- Replies: 58
- Views: 23507
Re: Could not open file
Yes no problem.
I just need to be sure we don't lose any incoming mails while testing. Now it's a good time to do the tests (late sunday evening).
I'll do a snapshot of the VM before applying the patches.
Let me know what I should try.
I just need to be sure we don't lose any incoming mails while testing. Now it's a good time to do the tests (late sunday evening).
I'll do a snapshot of the VM before applying the patches.
Let me know what I should try.
- 14 Nov 2021 19:08
- Forum: Discussion
- Topic: Could not open file
- Replies: 58
- Views: 23507
Re: Could not open file
Hello shawn, Sorry for the late reply. I thought I would receive notifications when there are replies to the topic, but it seems I don't, I have to check the notifications settings :) About the audit.log, there are some entries but they are related to our custom postfix transport databases: type=SYS...
- 10 Nov 2021 18:54
- Forum: Discussion
- Topic: Could not open file
- Replies: 58
- Views: 23507
Re: Could not open file
Sorry for the flood, but I want also to add that looking at /var/log/messages we have also a lot of: Nov 10 19:41:51 mx1 msmilter-init: '/var/spool/MailScanner/milterin/temp-' and '/var/spool/MailScanner/milterin/temp-' are identical (not copied) at /usr/sbin/MSMilter line 533. Nov 10 19:41:51 mx1 m...
- 10 Nov 2021 17:02
- Forum: Discussion
- Topic: Could not open file
- Replies: 58
- Views: 23507
Re: Could not open file
Also something else I discovered. On of the mail that is unable to open is present in the mailout folder. [root@mx1 log]# ls -la /var/spool/MailScanner/milterout/4HT88q4kNYzlsmd -rw-------. 1 postfix postfix 216727 Oct 12 10:34 /var/spool/MailScanner/milterout/4HT88q4kNYzlsmd This one has Unable to ...
- 10 Nov 2021 16:31
- Forum: Discussion
- Topic: Could not open file
- Replies: 58
- Views: 23507
Re: Could not open file
I forgot to mention that in the log of the mail that I traced I can see: "MailWatch: Logging message 4HfPky015wzMqYwP to SQL" But when looking up for this mail ID in mailwatch interface : "Message ID '4HfPky015wzMqYwP' not found!" Checking the db manually: MariaDB [mailscanner]> ...