Re: Unable to run qmail-remote

Erwin Hoffmann <[email protected]> Sat, 23 Dec 2017 14:55:19 +0100
Newsgroups	gmane.mail.qmail.general
Message-ID	<[email protected]>
Hi Niamh,

some of the Auth packages for qmail are buggy; some calculate the wrong MD5 hashsums given a 64 bit OS.

You can try to use mine:

	http://www.fehcom.de/qmail/smtpauth.html

A little bit outdated considering my s/qmail

	http://www.fehcom.de/sqmail/sqmail.html

but still ok.

Regards.
--eh.

BTW: DKIM support will come with aQmail.


> Am 23.12.2017 um 09:21 schrieb Niamh Holding <[email protected]>:
> 
> 
> Hello Charles,
> 
> Saturday, December 23, 2017, 4:11:07 AM, you wrote:
> 
> CC> Finding out which patch or combination of patches causes the bug will not be
> CC> simple.
> 
> I think I know and it's probably not handliny the garbage EHLO response...
> 
> From https://qmail.jms1.net/patches/combined-details.shtml
> 
> Tom Clegg's qmail-remote-auth.patch allows qmail-remote to use AUTH when
> connecting to certain remote mail servers. The userids and passwords are
> set in the "smtproutes" file, after the IP[:PORT] value, separated by
> spaces. For example...
> 
> domain1.xyz:1.2.3.4
> domain2.xyz:2.3.4.5 user pass
> domain3.xyz:3.4.5.6:26 user pass
> 
> In the process of tracking down what I thought was a bug, I ended up
> adding support for the AUTH PLAIN method. With this patch, qmail-remote
> checks the list of AUTH methods advertised in the EHLO response, and can
> work with either AUTH PLAIN or AUTH LOGIN (with AUTH PLAIN being used if
> both are available.) This was made possible by the regex function from
> above, because using regular expressions makes it so much easier to scan
> the server's output for authentication methods.
> 
> I also found something else which may be a bug or may have been by design,
> but it doesn't seem right to me so I changed it. When it sends the "MAIL
> FROM:<...> AUTH=<...>" line (after successfully AUTH'ing to the remote
> server) it was repeating the sender address in the AUTH= argument, rather
> than putting the actual AUTH information in this argument. It now puts the
> userid from the AUTH information into the AUTH= argument. If this is
> somehow wrong, please explain to me why and I'll change it back.
> 
> --
> Best regards,
> Niamh                            mailto:[email protected]

Dr. Erwin Hoffmann | FEHCom | http://www.fehcom.de | PGP Key-Id: EE00CF65
signature.asc (application/pgp-signature, 833 B)