On Wed, Nov 10, 2021 at 03:23:25PM -0700, Philip Prindeville via MIMEDefang wrote: > Hi, > > I just updated my mail server from Fedora 33 to Fedora 34, and I noticed > right away seeing these messages: > > Nov 10 14:37:17 localhost mimedefang.pl[9141]: 1AALbHB8009400: relay: > vger.kernel.org (23.128.96.18:56344 => 192.168.4.3:25) > Nov 10 14:37:22 localhost mimedefang.pl[7873]: 1AALbHB8009400: helo: > vger.kernel.org (23.128.96.18:56344) said "helo vger.kernel.org" > Nov 10 14:37:22 localhost sendmail[9400]: 1AALbHB8009400: > from=<[email protected]>, size=400289, class=-60, nrcpts=1, > msgid=<20211110063928.GB30217@xsang-OptiPlex-9020>, bodytype=8BITMIME, > proto=ESMTP, daemon=MTA-v4, relay=vger.kernel.org [23.128.96.18] > Nov 10 14:39:22 localhost sendmail[9400]: 1AALbHB8009400: Milter > (mimedefang): timeout before data read, where=eom > Nov 10 14:39:22 localhost sendmail[9400]: 1AALbHB8009400: Milter > (mimedefang): to error state > Nov 10 14:39:22 localhost sendmail[9400]: 1AALbHB8009400: Milter: data, > reject=451 4.3.2 Please try again later > Nov 10 14:39:22 localhost sendmail[9400]: 1AALbHB8009400: to=<[email protected]>, > delay=00:02:00, pri=538289, stat=Please try again later > Nov 10 14:43:38 localhost mimedefang.pl[8384]: 1AALbHB8009400: > MDLOG,1AALbHB8009400,mail_in,,,<[email protected]>,<[email protected]>,[af_unix] > 95e381b609: WARNING:possible_recursive_locking_detected > Nov 10 14:43:38 localhost mimedefang[1258]: 1AALbHB8009400: smfi_addheader > returned MI_FAILURE > > Looking through the logs, this happens over and over, and only with the > delivery of this one message. Since it can't be delivered for some reason, I > looked it up on MARC: > > https://marc.info/?l=linux-netdev&m=163652637632433&w=2 > > Anyone have an idea what's going on? Is there a timeout I need to increase? > you are hitting R=2m timeout while milter is sending data to mimedefang, this may happen when some code inside mimedefang.pl times out for a reason (antispam, antivirus ?). The code that triggers the problem may be near a call to action_add_header or action_change_header in your mimedefang-filter.
> Looking at: > > Xmimedefang, S=unix:/var/spool/MIMEDefang/mimedefang.sock, F=T, > T=S:2m;R:2m;E:10m > > That looks like plenty... > > Other than that, everything seems to be working fine (well, I did have to > change the $qid variable to filter_relay() and filter_helo() as that changed, > but that was relatively minor). > > BTW: who now owns the direction of development of MimeDefang? Who is the > designer-in-chief? > MIMEDefang development now happens on https://github.com/The-McGrail-Foundation/MIMEDefang You can find some info about MIMEDefang project management at https://mimedefang.org/mimedefang-project-charter/ Giovanni
signature.asc
Description: PGP signature
_______________________________________________ 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
