https://bugs.exim.org/show_bug.cgi?id=3037
--- Comment #2 from Zakaria <[email protected]> --- Hi Jeremy, Thanks for getting back to me. --Please don't tell me --it hacks on Exim's spool file; this is not a public interface for Exim --and you should not do that. A transport filter should operate stdin=to-stdout --as a stream processor. I'm afraid to tell you, with all due trying my bestest to abide by the rules and reading this notice https://github.com/Exim/exim/wiki/Q1601, this is just what I'm doing. Since it's only my personal email server and testing on some features but if there is any official mail server which requires some legal notices and warning, please rest assured I'm going to address it all lawfully. Yet, I couldn't access message body nor headers from bash script? and I had to fetch it from spool files while I don't edit spool files at all but I found calling echo with concatenated headers and body does the job, as transport filter, takes this and replace it with existing one. I read the documentation, here https://www.exim.org/exim-html-current/doc/html/spec_html/ch-generic_options_for_transports.html, it claimed message body and headers it's present somewhere in the stdin but couldn't figure out which argument? would it be passed to modifyemail bash script and under which name? Also, just to be accurate, it seems as you stated true has nothing to do with ARG_MAX, but I noticed any small email sent without attachment and pass through my modifyemail.sh in transport filter, works just fine and doesn't throw broken pipe? Any feedback would be very much appreciated. Looking forward, with thanks. -- You are receiving this mail because: You are on the CC list for the bug. -- ## subscription configuration (requires account): ## https://lists.exim.org/mailman3/postorius/lists/exim-dev.lists.exim.org/ ## unsubscribe (doesn't require an account): ## [email protected] ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
