Path: ...!weretis.net!feeder6.news.weretis.net!i2pn.org!i2pn2.org!.POSTED!not-for-mail
From: hquest@hquest.pro.br (HQuest)
Newsgroups: comp.mail.sendmail
Subject: Re: Fastest way to inject a lot of =?UTF-8?B?bWFpbD8=?=
Date: Fri, 8 Mar 2024 00:59:38 +0000
Organization: novaBBS
Message-ID: <99e62c2b98ba555ae362b54fff8ff3c4@www.novabbs.com>
References: <us8204$2viu$1@gal.iecc.com> <us9eba$aiki$1@dont-email.me> <usalen$1a5$1@gal.iecc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Info: i2pn2.org;
	logging-data="1235822"; mail-complaints-to="usenet@i2pn2.org";
	posting-account="t+lO0yBNO1zGxasPvGSZV1BRu71QKx+JE37DnW+83jQ";
User-Agent: Rocksolid Light
X-Spam-Checker-Version: SpamAssassin 4.0.0
X-Rslight-Posting-User: 3d3517e5dd24387fdf8da64199401ea731577ab2
X-Rslight-Site: $2y$10$S21ijB2uAQbIp2ckE6FGYeEt/vDlVaHoHwchE8CN.O2KPN.fkhQSO
Bytes: 2087
Lines: 7

Aside of the recommended "Tuning" by Claus, your workflow the way I read felt inefficient. You prep the mail, fire up a sendmail MSA instance (just to wrap the message with proper mail headers), handle to another sendmail MTA or whatever (to add DKIM headers) and move it forward... if you already have a trusted MTA elsewhere, why don't you just deliver the message right into that MTA via the application itself?

If you are lazy (as I am), a rudimentary, poorly written, very insecure and extremely lazy bash script can do the job:
echo ${mail_message_complete_with_envelope_headers_and_ehlo} > /dev/tcp/$smtpsrv/$smtpport

Assuming you trust it enough to cut the authentication and StartTLS pieces to save precious CPU cycles. The DKIM header will still be added by the MTA, but by not spinning multiple MSAs which, combined with its dynamic libraries, you save quite some time to get messages moving.

Or if you really want to use sendmail as MSA because authentication/TLS/reasons, keep one running, and deliver the email message to it via TCP/IP. A fork() is always much faster than a full load.