That change to the file does seem to prevent the error, and I appreciate
the help with my immediate problem. I'm still wondering if having the
program crash as it did without generating a very useful error message
is desirable behavior.
--
You received this bug notification because you are a mem
** Tags removed: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940603
Title:
postfix/smtpd: fatal: no SASL authentication
To manage notifications about this bug go to:
https://bugs.lau
I finally got around to take another look, sorry for the delay. The
problem is the "noplaintext" in smtpd_sasl_security_options Here's a
small config diff that fixes the problem:
# diff -Naur main.cf.bug main.cf
--- main.cf.bug 2021-09-15 19:14:02.919982259 +
+++ main.cf 2021-09-15 19:18:0
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940603
Title:
postfix/smtpd: fatal: no SASL authentication
To manage notifications about this bug go to:
https://bugs.launc
Any more info you need? I was trying to follow the official Ubuntu
server guide ( https://ubuntu.com/server/docs/mail-postfix ) with only a
few deviations for things like a different location for SSL files. Are
there more problems with that guide? Earlier in this item, you
suggested moving authe
** Attachment added: "main.cf"
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1940603/+attachment/5520588/+files/main.cf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940603
Title:
post
** Attachment added: "master.cf"
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1940603/+attachment/5520589/+files/master.cf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940603
Title:
I don't see a 220 message with the nc command either.
State Recv-QSend-Q Local Address:PortPeer Address:Port
Process
LISTEN0 1127.0.0.1:246970.0.0.0:*
@Todd, I somehow had missed you were already using the
smtpd_sasl_tls_security_options config, sorry about that. I don't
understand why telnet didn't display the 220 banner as the logs suggest
it was sent:
Aug 17 04:07:21 kangaroo postfix/smtpd[46495]: >
kangaroo.unclet.net[127.0.0.1]: 220 kanga
I didn't think the sasl2-bin package was needed, but someone else
suggested I try adding it.
Even with the settings that I had, shouldn't I have seen some messages
from the server on the telnet connection? (e.g. remote mail server
connecting to send mail to an address where this system is the fin
Thank you Simon,
marking the bug incomplete until clarification of your configuration hints in
regard to the case.
** Changed in: postfix (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
With postfix using "smtpd_sasl_type = dovecot", you shouldn't need
sasl2-bin.
I think your test with telnet on port 25 will not work because you have
"smtpd_sasl_security_options = noanonymous,noplaintext" which disables
"plaintext" type of auth and both LOGIN and PLAIN are in the clear.
It's gen
12 matches
Mail list logo