Re: Enabling SASL without any authentication back-end for use with XCLIENT only

2020-03-21 Thread Melvin Vermeeren
Wietse Venema: > Melvin Vermeeren: > > In conclusion I believe "var_smtpd_sasl_enable" can be removed from > > src/smtpd/ smtpd_check.c completely, together with the "if > > (var_smtpd_sasl_enable)" conditionals. Could you post your thoughts on > >

Re: Enabling SASL without any authentication back-end for use with XCLIENT only

2020-03-21 Thread Melvin Vermeeren
Wietse Venema: > Wietse Venema: > > Melvin Vermeeren: > > > To be specific the problem is that it appears impossible to enable SASL > > > without configuring a real, working, authentication back-end, which is > > > not > > > needed if only XCLIENT-styl

Re: Enabling SASL without any authentication back-end for use with XCLIENT only

2020-03-21 Thread Melvin Vermeeren
On Saturday, 21 March 2020 15:59:45 CET Wietse Venema wrote: > Melvin Vermeeren: > > > connect from localhost[127.0.0.1] > > > warning: restriction `reject_authenticated_sender_login_mismatch' > > > ignored: > > > no SASL support > > This means th

Enabling SASL without any authentication back-end for use with XCLIENT only

2020-03-21 Thread Melvin Vermeeren
Hi all, Recent version of dovecot come with a submission server (MSA), which allows for simpler configuration and adds BURL support, avoiding the need for the client to upload the mail twice: once to IMAP, once to the MSA. See also: https://doc.dovecot.org/admin_manual/submission_server/ This m