Dnia 3.11.2023 o godz. 08:00:43 Wietse Venema via Postfix-users pisze:
> Nick Lockheart via Postfix-users:
> > What are the Postfix settings for TLS between Postfix and Dovecot SASL?
>
> This is not documented, therefore not implemented. What is your
> threat model: am attac
Nick Lockheart via Postfix-users:
>
> If I have Postfix configured to use Dovecot SASL via TCP, and Dovecot
> is running on a remote server, can I set up Postfix to use TLS for its
> connection to Dovecot SASL?
>
> Postfix main.cf:
>
> smtpd_sasl_path = inet:d
If I have Postfix configured to use Dovecot SASL via TCP, and Dovecot
is running on a remote server, can I set up Postfix to use TLS for its
connection to Dovecot SASL?
Postfix main.cf:
smtpd_sasl_path = inet:dovecot.example.com:12345
smtpd_sasl_type = dovecot
Dovecot:
service auth
Podskubka, Stefan:
> Wietse Venema:
> > The error happened because the hostname "dovecot" did not resolve.
> >
> > This may be affected by how compatibility_level is set, because
> > compatibility_level is processed before Postfix's chroot feature makes some
> > files inaccessible.
>
> Wow, I
Wietse Venema:
> The error happened because the hostname "dovecot" did not resolve.
>
> This may be affected by how compatibility_level is set, because
> compatibility_level is processed before Postfix's chroot feature makes some
> files inaccessible.
Wow, I was completely thrown off the right
Podskubka, Stefan:
> Aug 10 19:39:14 4097ff109d16 postfix/smtpd[112]:
> xsasl_dovecot_server_connect: Connecting
> Aug 10 19:39:14 4097ff109d16 postfix/smtpd[112]: fatal: host/service
> dovecot/666 not found: Device or resource busy
This error message is from inet_connect():
if ((parse_err
Dear Postfix experts!
Although I have found a solution/workaround for the problem mentioned here, for
what it's worth, I still wanted to make the effort to report it as a possible
bug.
Summary
===
I have a test setup on my local machine where I am running Postfix and Dovecot,
each in a
I've set up dovecot to provide SASL for postfix and as far as I can
tell everything is working correctly. However, when I do a ehlo
localhost
I don't see it announcing anything about AUTH :
Connected to localhost.
Escape character is '^]'.
220 xxx.yyy.QueensU.CA ESMTP Postfix
ehlo
On Fri, May 24, 2013 at 09:14:14AM -0400, Peter Skensved wrote:
I don't see it announcing anything about AUTH :
Connected to localhost.
Escape character is '^]'.
220 xxx.yyy.QueensU.CA ESMTP Postfix
ehlo localhost
250-xxx.yyy.QueensU.CA
250-PIPELINING
250-SIZE 4096
250-VRFY
On May 24, 2013, at 7:14, Peter Skensved pe...@jay.phy.queensu.ca wrote:
smtpd_tls_auth_only = yes
So, questioned answered then?
I've set up dovecot to provide SASL for postfix and as far as I can
tell everything is working correctly. However, when I do a ehlo localhost
I don't see it announcing anything about AUTH :
Connected to localhost.
Escape character is '^]'.
220 xxx.yyy.QueensU.CA ESMTP Postfix
ehlo localhost
On 5/22/2013 12:42 PM, Peter Skensved wrote:
I've set up dovecot to provide SASL for postfix and as far as I can
tell everything is working correctly. However, when I do a ehlo localhost
I don't see it announcing anything about AUTH :
Connected to localhost.
Escape character is '^]'.
On 22 May 2013, at 13:42, Peter Skensved wrote:
I've set up dovecot to provide SASL for postfix and as far as I can
tell everything is working correctly. However, when I do a ehlo
localhost
I don't see it announcing anything about AUTH :
Connected to localhost.
Escape character is '^]'.
220
I know the subject seems trivial, but i launched a new mail server Friday
night and have been fighting this all weekend. Very desperate now. I truly
think it boils down to SASL configs. I've made so many changes in past 72
hours I can't even remember my name. Please help.
--Brian
* Brian Shanahan bshana...@cruiseplanners.com:
I know the subject seems trivial, but i launched a new mail server Friday
night and have been fighting this all weekend. Very desperate now. I truly
think it boils down to SASL configs. I've made so many changes in past 72
hours I can't even
Hello all,
I am struggeling to get my Dovecot SASL to work within postfix. I have used
the configuration example listed on the main-site of dovecot and it
basically isn't giving me any success at all. I am probably missing
something easy, but after spending a few days testing and walking through
Quoting Rene Bakkum rene.bak...@gmail.com:
Hello all,
I am struggeling to get my Dovecot SASL to work within postfix. I have used
the configuration example listed on the main-site of dovecot and it
basically isn't giving me any success at all. I am probably missing
something easy, but after
On Mon, 2009-04-27 at 00:08 -0400, Victor Duchovni wrote:
On Mon, Apr 27, 2009 at 12:04:50AM -0400, Timo Sirainen wrote:
Oh. That's actually it. Dovecot is listening on private/auth, but Postfix
is connecting to private/dovecot. But what is listening on private/dovecot
then? You've
Timo Sirainen wrote:
On Apr 26, 2009, at 11:58 PM, Timo Sirainen wrote:
smtpd_sasl_path = private/dovecot
..
I can see the private/auth socket created when dovecot starts, with
postfix:postfix permissions. Also, netstat shows it:
bash:# netstat -ln | grep dovecot
unix 2 [ ACC ]
On Sun, 26 Apr 2009, Juha Pahkala wrote:
Wietse Venema wrote:
Juha Pahkala:
Wietse Venema wrote:
Juha Pahkala:
Apr 24 15:42:30 server postfix/smtpd[8126]: name_mask: noanonymous
Apr 24 15:42:30 server postfix/smtpd[8126]:
xsasl_dovecot_server_connect: Connecting
Apr
On Apr 24, 2009, at 11:54 AM, Juha Pahkala wrote:
Apr 24 15:42:50 server postfix/smtpd[8126]: fatal: no SASL
authentication mechanisms
..
auth default:
mechanisms: plain login
So Dovecot is advertising PLAIN and LOGIN mechanisms to Postfix.
client:
path:
On Apr 26, 2009, at 11:58 PM, Timo Sirainen wrote:
smtpd_sasl_path = private/dovecot
..
I can see the private/auth socket created when dovecot starts, with
postfix:postfix permissions. Also, netstat shows it:
bash:# netstat -ln | grep dovecot
unix 2 [ ACC ] STREAM LISTENING
On Mon, Apr 27, 2009 at 12:04:50AM -0400, Timo Sirainen wrote:
Oh. That's actually it. Dovecot is listening on private/auth, but Postfix
is connecting to private/dovecot. But what is listening on private/dovecot
then? You've added some kind of a dovecot service to master.cf?
Almost
Terry Carmen wrote:
Hello,
I've been trying to setup postfix with tls and smtp auth (dovecot sasl).
I'm now stuck with the smtp auth part, with a strange error. For a few
days I've tried to search information about similar problems, but found
none. Now I'm hoping somebody here could help me
Wietse Venema wrote:
Juha Pahkala:
Apr 24 15:42:30 server postfix/smtpd[8126]: name_mask: noanonymous
Apr 24 15:42:30 server postfix/smtpd[8126]:
xsasl_dovecot_server_connect: Connecting
Apr 24 15:42:40 server postfix/smtpd[8126]:
xsasl_dovecot_server_connect: auth reply: status
Apr 24
Wietse Venema wrote:
Juha Pahkala:
Wietse Venema wrote:
Juha Pahkala:
Apr 24 15:42:30 server postfix/smtpd[8126]: name_mask: noanonymous
Apr 24 15:42:30 server postfix/smtpd[8126]:
xsasl_dovecot_server_connect: Connecting
Apr 24 15:42:40 server postfix/smtpd[8126]:
Hello,
I've been trying to setup postfix with tls and smtp auth (dovecot sasl).
I'm now stuck with the smtp auth part, with a strange error. For a few
days I've tried to search information about similar problems, but found
none. Now I'm hoping somebody here could help me out. I'm running
Hello,
I've been trying to setup postfix with tls and smtp auth (dovecot sasl).
I'm now stuck with the smtp auth part, with a strange error. For a few
days I've tried to search information about similar problems, but found
none. Now I'm hoping somebody here could help me out. I'm running
Juha Pahkala:
Apr 24 15:42:30 server postfix/smtpd[8126]: name_mask: noanonymous
Apr 24 15:42:30 server postfix/smtpd[8126]:
xsasl_dovecot_server_connect: Connecting
Apr 24 15:42:40 server postfix/smtpd[8126]:
xsasl_dovecot_server_connect: auth reply: status
Apr 24 15:42:50 server
29 matches
Mail list logo
