>I see no way that MIME::Tools could possibly be relevant. Agree, but I found a very old reference where someone had a similar problem and it was apparently fixed by reinstalling MIME::Tools
>Do you see these events if you put that on real disk? I moved the spool directory to a physical drive, and the error still happens. >So: why was that working directory missing mid-scan? Or was it never >created? I have no ideas. Is /var/spool/MIMEDefang writeable by the user >running mimedefang? Could SELinux or AppArmor be interfering? It seems the directory is never created - I will add some code tomorrow to verify this. Remember it works for 99%+ of e-mails. Only some emails fail which disqualifies SELinux, permissions, etc. Just for information sake, the permissions and owner is as follows: drwxr-xr-x 6 defang root 135168 Nov 18 22:44 MIMEDefang Here is a process showing the user is defang. 36414 defang 20 0 301728 63992 6524 S 10.9 0.1 0:01.51 mimedefang.pl On Thu, 18 Nov 2021 at 21:51, Bill Cole via MIMEDefang < [email protected]> wrote: > On 2021-11-18 at 11:28:08 UTC-0500 (Thu, 18 Nov 2021 18:28:08 +0200) > Ernst du Plooy via MIMEDefang <[email protected]> > is rumored to have said: > > > I tried to reinstall MIME::Tools, but the issue remains. > > I see no way that MIME::Tools could possibly be relevant. > > > No space issues > > root@relay2 ~]# df -h |grep MIMEDefang > > tmpfs 4.0G 3.4M 4.0G 1% /var/spool/MIMEDefang/ > > Do you see these events if you put that on real disk? > > > The inital example I've sent is extremely confusing and I can't really > > wrap > > my head around it. To make things easier and to first look at the > > directory problem I extracted another example: > > I do not see more than one queue ID in these log lines. > > > [root@relay2 ~]# cat /var/log/maillog |grep 1AIFm3xE022061 > > Nov 18 17:48:05 relay2 mimedefang.pl[17432]: 1AIFm3xE022061: SPF > > Result: > > *pass*pass*nightsbridge.co.za: 34.193.196.229 is authorized to use ' > > [email protected]' in 'mfrom' identity (mechanism 'mx' > > matched)*34.193.196.229*<[email protected]>* > mail.nightsbridge.com > > Nov 18 17:48:05 relay2 mimedefang.pl[17432]: 1AIFm3xE022061: NOTICE: > > All > > Filter Recipient tests passed > > Nov 18 17:48:06 relay2 sendmail[22061]: 1AIFm3xE022061: from=< > > [email protected]>, size=2719, class=0, nrcpts=1, > > msgid=<172494053.52128.1637250479567@localnode>, proto=ESMTP, > > daemon=MTA, > > relay=mail1.nightsbridge.com [34.193.196.229] > > Nov 18 17:48:06 relay2 mimedefang.pl[17375]: 1AIFm3xE022061: > > MDLOG,1AIFm3xE022061,RECEIVE (sbn),,,<[email protected]>,< > > [email protected]>,Booking for Villa Bali Boutique Hotel (xxx) - > > xxxn%2C > > arriving 15 Dec 2021 > > Nov 18 17:48:06 relay2 mimedefang.pl[17375]: 1AIFm3xE022061: Rules > > Used: > > xxx.co.za > > Nov 18 17:48:06 relay2 mimedefang.pl[17375]: 1AIFm3xE022061: DKIM > > Domain: > > xxx.co.za > > Nov 18 17:48:06 relay2 mimedefang.pl[17375]: 1AIFm3xE022061: Executing > > DMARC for Domain (nightsbridge.co.za) and IP (34.193.196.229). > > Nov 18 17:48:06 relay2 mimedefang.pl[17375]: 1AIFm3xE022061: DKIM pass > > DMARC: v=DMARC1; p=reject; rua=mailto:[email protected]; > > ruf=mailto:[email protected]; adkim=s; aspf=s > > Nov 18 17:48:06 relay2 mimedefang.pl[17375]: 1AIFm3xE022061: Clamd > > returned > > error: File path check failure: No such file or directory. > > Nov 18 17:48:06 relay2 mimedefang.pl[17375]: 1AIFm3xE022061: > > Anti-Virus: > > Running virus scanner > > Nov 18 17:48:06 relay2 mimedefang.pl[17375]: 1AIFm3xE022061: > > Anti-Virus: > > result: From: <[email protected]> | Message: 999 swerr | Action: > > tempfail | Virus-Name: | Complete-Message: > > Nov 18 17:48:06 relay2 mimedefang.pl[17375]: 1AIFm3xE022061: > > Anti-Virus: > > scanner tempfail! > > Nov 18 17:48:06 relay2 mimedefang.pl[17375]: 1AIFm3xE022061: High Load > > Server > > Nov 18 17:48:06 relay2 mimedefang.pl[17375]: 1AIFm3xE022061: NOTICE: > > All > > Filter tests passwd > > Nov 18 17:48:06 relay2 mimedefang.pl[17375]: 1AIFm3xE022061: NOTICE: > > Scan > > complete. > > Nov 18 17:48:06 relay2 mimedefang[10998]: 1AIFm3xE022061: Filter did > > not > > create RESULTS file > > Nov 18 17:48:06 relay2 mimedefang[10998]: 1AIFm3xE022061: > > lstat(/var/spool/MIMEDefang/mdefang-1AIFm3xE022061) failed: No such > > file or > > directory > > Nov 18 17:48:06 relay2 mimedefang[10998]: 1AIFm3xE022061: failed to > > clean > > up /var/spool/MIMEDefang/mdefang-1AIFm3xE022061: No such file or > > directory > > Nov 18 17:48:06 relay2 sendmail[22061]: 1AIFm3xE022061: Milter: data, > > reject=451 4.3.2 Please try again later > > Nov 18 17:48:06 relay2 sendmail[22061]: 1AIFm3xE022061: to=< > > [email protected]>, delay=00:00:01, pri=32719, stat=Please try again > > later > > The only oddity I see here is that something whacked the MD working > directory for 1AIFm3xE022061 while MD was still working with it. > > [...] > > > Maybe we should look at the new example to simplify things for now. > > OK, but it does have the difference of NOT having any issue with > multiple queue IDs. > > So: why was that working directory missing mid-scan? Or was it never > created? I have no ideas. Is /var/spool/MIMEDefang writeable by the user > running mimedefang? Could SELinux or AppArmor be interfering? > > > > > -- > Bill Cole > [email protected] or [email protected] > (AKA @grumpybozo and many *@billmail.scconsult.com addresses) > Not Currently Available For Hire > > _______________________________________________ > NOTE: If there is a disclaimer or other legal boilerplate in the above > message, it is NULL AND VOID. You may ignore it. > > MIMEDefang mailing list [email protected] > > https://lists.mimedefang.org/mailman/listinfo/mimedefang_lists.mimedefang.org >
_______________________________________________ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. MIMEDefang mailing list [email protected] https://lists.mimedefang.org/mailman/listinfo/mimedefang_lists.mimedefang.org
