> On Jun 2, 2017, at 1:20 AM, Roelof Wobben wrote:
>
> oke, you mean this config file :
>
> /etc/sasl/smtpd.conf
>
> pwcheck_method: auxprop
> auxprop_plugin: sasldb
> mech_list: PLAIN LOGIN CRAM-MD5 DIGEST-MD5 NTLM
If your Postfix build supports Cyrus SASL, and that's the
configured SASL d
Op 2-6-2017 om 01:49 schreef Wietse
Venema:
Roelof Wobben:
Thanks,
Changed it but the error stays even after restarting postfix.
I suppose the contents of the file are incorrect. However, the Cyrus
SASL library is not a Postfix projec
Hi Wietse,
Okay - I think I've worked out the answer to my second question if I use the
sendmail command line, with the -N option.
> /usr/sbin/sendmail.postfix -f t...@dev.kamar.kiwi.nz -N 'success, delay,
> failure' k...@kamar.nz < tmp
Reading through documentation / mailing lists, it looks
Hi Wietse,
Thanks - I'll stop trying to attempt to do it this way then.
The SMTP approach does have the advantage of realtime feedback on the 'rcpt
to:' being accepted and I can spread the load across multiple threads /
connections.
Next question: Is there a way to get a 'delivered' notificat
Kent:
> Hi All,
>
> I have a MongoDB with a set of e-mails that I want to send. I want to be
> able to track their delivery / bounce / delayed status - plus link any
> replies back to the original e-mail.
>
> I have already written a c++ service to handle incoming e-mails (by piping
> the i
Roelof Wobben:
> Thanks,
>
> Changed it but the error stays even after restarting postfix.
I suppose the contents of the file are incorrect. However, the Cyrus
SASL library is not a Postfix project. Cyrus SASL has its own mailing
list.
Wietse
Hi All,
I have a MongoDB with a set of e-mails that I want to send. I want to be able
to track their delivery / bounce / delayed status - plus link any replies back
to the original e-mail.
I have already written a c++ service to handle incoming e-mails (by piping the
incoming e-mails to my
Thanks,
Changed it but the error stays even after restarting postfix.
Roelof
Op 1-6-2017 om 20:54 schreef Wietse Venema:
Roelof Wobben:
Jun 1 18:08:12 localhost postfix/smtpd[9652]: warning: SASL per-process
initialization failed: error when parsing configuration file
Jun 1 18:08:12 local
Roelof Wobben:
> Jun 1 18:08:12 localhost postfix/smtpd[9652]: warning: SASL per-process
> initialization failed: error when parsing configuration file
> Jun 1 18:08:12 localhost postfix/smtpd[9652]: fatal: SASL per-process
> initialization failed
You need to fix your SASL configuration file.
I could reproduce the error on another
machine so here the logs :
errors from maillog :
Jun 1 18:07:11 localhost postfix/smtpd[9650]: warning: SASL per-process initialization failed: error when parsing configuration file
Jun 1 18:07:11 localhost postfi
Both thanks,
I will make the logs as soon as I work with that server.
I think it will be on Tuesday.
Regards,
Roelof
Op 1-6-2017 om 15:27 schreef Wietse Venema:
Roelof Wobben:
Hello,
I have this in my main.cf :
smtpd_sasl_path = smtpd
smtpd_sasl_auth_enable = yes
in my sasl2 config file
Roelof Wobben:
> Hello,
>
> I have this in my main.cf :
>
> smtpd_sasl_path = smtpd
> smtpd_sasl_auth_enable = yes
>
> in my sasl2 config file I have this :
>
> pwcheck_method = auxprop
> auxprop_plugin = sasldb
> mech_list = plain login cram-md5 digest-md5 ntlm
>
> but when I do telnet
Hi,
it's rather less information. Please provide information described under
http://www.postfix.org/DEBUG_README.html#mail
Willi
Am 01.06.2017 um 11:36 schrieb Roelof Wobben:
> Hello,
>
> I have this in my main.cf :
>
> smtpd_sasl_path = smtpd
> smtpd_sasl_auth_enable = yes
>
> in my s
Hello,
I have this in my main.cf :
smtpd_sasl_path = smtpd
smtpd_sasl_auth_enable = yes
in my sasl2 config file I have this :
pwcheck_method = auxprop
auxprop_plugin = sasldb
mech_list = plain login cram-md5 digest-md5 ntlm
but when I do telnet 127.0.0.1 25 and I do then ehlo locahost I
14 matches
Mail list logo
