Re: qmail-remote crashed.

On 2/18/19 12:26 PM, Rejaine Silveira Monteiro wrote:
> Helo Erwin
> 
> I'm not using TLS and using qmail-1.03-jms1-7.10.patch  (FORCE_TLS=0
> and DENY_TLS=1)

I can't offer much help with specific ideas for a solution but I can 
offer some advice about where not to look.

In John Simpson's patch FORCE_TLS and DENY_TLS are only used by 
qmail-smtpd.  They are not used elsewhere.

> anyway, I created the tlsdestinations file as you indicated, but it
> did not work.
> 
> the only problem is with clients using mail.protection.outlook.com
> 
> in the link below you can read that there may be problems with new
> ips, due to some "policy reputation" stuff  (our mta ip was changed
> last nigth)  and maybe that is why we can not send it there ..
> 
> https://docs.microsoft.com/pt-br/office365/securitycompliance/removing-a-user-domain-or-ip-address-from-a-block-list-after-sending-spam-email

If there is a problem with your IP addresses or domain names being 
acceptable to Microsoft you will be seeing 4yz or 5yz SMTP reply errors 
returned by them to you.  Those errors will be in your qmail-send log 
files.  Those problems wouldn't cause qmail-remote to crash.

> I publish SPF, but not DMARC or DKIM ... so I guess I'll have to wait
> a little longer ..

Any changes with SPF, DKIM, etc will not make a difference with 
qmail-remote crashing.

If you have /var/qmail/control/clientcert.pem you can rename that file 
out of the way so that qmail-remote won't use it.  It will effectively 
disable TLS for qmail-remote.  Just be aware that without TLS you may 
have delivery problems with certain destinations since some will only 
accept mail transferred with TLS.

-
John J.