Re: [Mimedefang] delete part best practice
On 12 Dec 2017, at 19:03 (-0500), Amit Gupta wrote: Given a parent entity and child entity, what's the best way to delete the child entity? I see code that clears all parts for an entity and then selectively adds them back in. I would like to scan through and selectively remove instead. See the man page for mimedefang-filter, specifically the description of "action_drop" which you would call from your filter() implementation when you deem a part worthy of dropping. -- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Currently Seeking Steady Work: https://linkedin.com/in/billcole ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
[Mimedefang] delete part best practice
Given a parent entity and child entity, what's the best way to delete the child entity? I see code that clears all parts for an entity and then selectively adds them back in. I would like to scan through and selectively remove instead. ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] utf-8 issue?
On 12 Dec 2017, at 8:43 (-0500), Mark Coetser wrote: Hi I have 4 different mail hubs, all running latest debian ii perl 5.24.1-3+deb9u2i386 Larry Wall's Practical Extraction and Report Language ii mimedefang 2.79-2 i386 e-mail filter program for sendmail [...] stderr: open body: Invalid argument at /usr/share/perl5/MIME/Entity.pm line 1878. A google search shows this topic https://lists.roaringpenguin.com/pipermail/mimedefang/2013-February/036880.html I doubt that's related. But I am not doing anything with MIME::Entity; Not explicitly, but MD uses it (and the rest of MIME-Tools) extensively. I'd bet this is the same as this bug: https://rt.cpan.org/Public/Bug/Display.html?id=105377 Which remains open but maybe not unfixed. and the filter is pretty much the stock microsoft mimedefang-filter and this does seem to be related from the upgrade from Debian Jessie to Stretch, does anyone have any pointers? It couldn't hurt to update MIME-Tools and it is certain that you're not up-to-date with it, since line 1878 of the current Entity.pm is blank. That error message would only be generated by line 1892 in the current version. My bet is that the typo fix cited in the Changelog for 5.507 also fixed this... -- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Currently Seeking Steady Work: https://linkedin.com/in/billcole ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] utf-8 issue?
On Tue, 12 Dec 2017 15:43:14 +0200 Mark Coetserwrote: > Error from multiplexor: ERR No response from slave > Reap: slave 1 (pid 15022) exited normally with status 22 (SLAVE DIED > UNEXPECTEDLY) I've never seen this before. I'm also not convinced it's related to the UTF-8 issue. Could you post the exact filter you are using? I'm also running on Stretch, btw. Regards, Dianne. ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
[Mimedefang] utf-8 issue?
Hi I have 4 different mail hubs, all running latest debian ii perl 5.24.1-3+deb9u2i386 Larry Wall's Practical Extraction and Report Language ii mimedefang 2.79-2 i386 e-mail filter program for sendmail Recently I am seeing alot of the following errors Error from multiplexor: ERR No response from slave Reap: slave 1 (pid 15022) exited normally with status 22 (SLAVE DIED UNEXPECTEDLY) The above are logged in mail.err and are related to the following in mail.log which rejects the email with a "try again later" message until the email eveentually bounces after 5 days. stderr: open body: Invalid argument at /usr/share/perl5/MIME/Entity.pm line 1878. A google search shows this topic https://lists.roaringpenguin.com/pipermail/mimedefang/2013-February/036880.html But I am not doing anything with MIME::Entity; and the filter is pretty much the stock microsoft mimedefang-filter and this does seem to be related from the upgrade from Debian Jessie to Stretch, does anyone have any pointers? -- Thank you, Mark Adrian Coetser ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang