authenticate outgoing mail against our valid user
database. I believe this requires us to install a "dummy" Dovecot on
the Postfix server so that Dovecot SASL can provide authentication to
Postfix from the database.
I think Cyrus had a standalone Cyrus-SASL package, but Dovecot doesn't?
If I
postfix does support tls for sasl (i use starttls from thunderbird with
out issues)
assumning that sasl + postfix + openssl have been compiled in properly
here are my config files (without password / auth for the databases) :
Note(s) :
PLEASE READ ALL OF THIS AS POSTFIX + SASL + SSL/TLS +
On 6/11/23 04:36, jeremy ardley via dovecot wrote:
You should be able to use ssh with port forwarding to establish a TLS
connection between devices. Postfix would see a remote SASL service as
a local service.
An alternative and possibly more reliable and easily configured
mechanism would b
On 6/11/23 03:25, Nick Lockheart wrote:
I can't use the real Dovecot IMAP server for auth, because it runs on
a separate server, and Postfix does not support TLS connections for SASL.
--
You should be able to use ssh with port forwarding to establish a TLS
connection between devices. Postfix
n separate
> > machines.
> > The user information is stored in a MariaDB database that is
> > replicated
> > on both servers.
> >
> > Postfix needs to authenticate outgoing mail against our valid user
> > database. I believe this requires us to install a "
d a Postfix server on separate machines.
The user information is stored in a MariaDB database that is replicated
on both servers.
Postfix needs to authenticate outgoing mail against our valid user
database. I believe this requires us to install a "dummy" Dovecot on
the Postfix server s
The user information is stored in a MariaDB database that is replicated
on both servers.
Postfix needs to authenticate outgoing mail against our valid user
database. I believe this requires us to install a "dummy" Dovecot on
the Postfix server so that Dovecot SASL can provide authenticati
d user
database. I believe this requires us to install a "dummy" Dovecot on
the Postfix server so that Dovecot SASL can provide authentication to
Postfix from the database.
I think Cyrus had a standalone Cyrus-SASL package, but Dovecot doesn't?
If I wanted to setup a Dovecot insta
ed
on both servers.
Postfix needs to authenticate outgoing mail against our valid user
database. I believe this requires us to install a "dummy" Dovecot on
the Postfix server so that Dovecot SASL can provide authentication to
Postfix from the database.
I think Cyrus had a standalone Cyr
Dovecot on
the Postfix server so that Dovecot SASL can provide authentication to
Postfix from the database.
I think Cyrus had a standalone Cyrus-SASL package, but Dovecot doesn't?
If I wanted to setup a Dovecot instance on the Postfix server just for
the purposes of SMTP authentication, an
On 2023-04-23 11:53, Benny Pedersen wrote:
dovecot--- via dovecot skrev den 2023-04-23 20:25:
I tried to enable it on postfix smtp_sasl_auth_enable, but it is was
not advertise.
That is because "smtp" is not the same as "smtpd".
http://www.postfix.org/postconf.5.html#smtpd_sasl_auth_enabl
Hi Badli,
thanks for the information.
A few hints:
If possible, please avoid using HTML mails.
And for outputs like 'postconf -n': please use an attached text file if
your MUA (OL) isn't able to transfer them in a proper way.
I would suggest the following changes:
1. postconf -n
[...]
s
Sent: Monday, April 24, 2023, 05:33
To: dovecot@dovecot.org
Subject: Re: dovecot sasl with postfix, smtp auth not available
Hi Badli,
On 23.04.23 05:15, Badli Al Rashid wrote:
> Anybody got any ideas ?
please post the output of:
1) postconf -n
2) postconf -M
Regards,
Mar
HI Benny,
master.cf already have enteries for 465 and 587 as I followed the guide.
Noted and thank you.
Regards,
-badli
From: Benny Pedersen
Sent: Monday, April 24, 2023, 02:54
To: dovecot@dovecot.org
Subject: Re: dovecot sasl with postfix, smtp auth not
Hi Badli,
On 23.04.23 05:15, Badli Al Rashid wrote:
Anybody got any ideas ?
please post the output of:
1) postconf -n
2) postconf -M
Regards,
Markus
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovec
dovecot--- via dovecot skrev den 2023-04-23 20:25:
I tried to enable it on postfix smtp_sasl_auth_enable, but it is was
not advertise.
That is because "smtp" is not the same as "smtpd".
http://www.postfix.org/postconf.5.html#smtpd_sasl_auth_enable
port 25 should not support sasl auth, ma
I tried to enable it on postfix smtp_sasl_auth_enable, but it is was not
advertise.
That is because "smtp" is not the same as "smtpd".
http://www.postfix.org/postconf.5.html#smtpd_sasl_auth_enable
___
dovecot mailing list -- dovecot@dovecot.org
T
e same
node.
Regards,
-badli
*From:* Benny Pedersen
*Sent:* Sunday, April 23, 2023, 20:22
*To:* dovecot@dovecot.org
*Subject:* Re: dovecot sasl with postfix, smtp auth not available
Badli Al Rashid skrev den 2023-04-23
i did an apt install postfix on the node. dovecot is on the same node.
Regards,
-badli
From: Benny Pedersen
Sent: Sunday, April 23, 2023, 20:22
To: dovecot@dovecot.org
Subject: Re: dovecot sasl with postfix, smtp auth not available
Badli Al Rashid skrev den 2023
Badli Al Rashid skrev den 2023-04-23 13:06:
My apologies, i am not using dovecot for submission server using
postfix with dovecot-sasl.
then post doveconf -n that shows it
I was not able to authenticate if I use a webmail when testing using
username to authenticate with smtp connection it
Hi,
My apologies, i am not using dovecot for submission server using postfix with
dovecot-sasl.
I was not able to authenticate if I use a webmail when testing using username
to authenticate with smtp connection it fails.
I could authenticate normally using port 465 / 587 but it is block at
On 04-22-2023 11:15 pm, Badli Al Rashid wrote:
I have set up dovecot sasl with postfix. When I check the smtp with ehlo there
is no auth advertise.
There shouldn't be on port 25. Users should do email submission on port 587 or
465.
But if you really want there to be...
Hi All,
I have set up dovecot sasl with postfix. When I check the smtp with ehlo there
is no auth advertise.
Connected to www.zystro.xyz.
Escape character is '^]'.
220 www.zystro.xyz
ehlo x.zystro.xyz
250-www.zystro.xyz
250-PIPELINING
250-SIZE 10485760
250-ETRN
250-ST
Hi,
I am getting the following error while authenticating any user, using SASL
with postfix, please help me to fix this issue.
May 08 17:34:50 master: Info: Dovecot v2.2.36.4 (baf9232c1) starting up for
imap, pop3, lmtp, sieve (core dumps disabled)
May 08 17:35:10 master: Error: service(auth): c
> On 22/09/2020 20:22 Jorge Bastos wrote:
>
>
> Howdy,
> I'm going back to this matter, to finish the replacement os cyrus SASL per
> dovecot-SASL.
> I want to have the same functionality that i had before, that is, SASL
> check's AUTH agains a different ta
Howdy,
I'm going back to this matter, to finish the replacement os cyrus SASL
per dovecot-SASL.
I want to have the same functionality that i had before, that is, SASL
check's AUTH agains a different table than the users one.
I was looking in the dovecot-SASL docs, and i see nothi
(I removed Wietse Venema from Cc:.)
Aki Tuomi wrote in
<1972528099.4900.1598022980...@appsuite-dev-gw1.open-xchange.com>:
...
|Sorry for duplicate mail, I accidentically pressed too many keys... *sigh*
Sure.
|Anyways, I'm not sure if you understood my point, I ment, have you \
|tried EXTER
Just another reminder..
https://github.com/dovecot/core/pull/86
This will allow plugins to make 'capability' advertisements more dynamic..
On 2020-08-21 7:56 a.m., Steffen Nurpmeso wrote:
Aki Tuomi wrote in
<1907575568.4364.1597984769...@appsuite-dev-gw1.open-xchange.com>:
|> On 21/08/2020
> On 21/08/2020 17:56 Steffen Nurpmeso wrote:
>
>
> Aki Tuomi wrote in
> <1907575568.4364.1597984769...@appsuite-dev-gw1.open-xchange.com>:
> |> On 21/08/2020 02:17 Steffen Nurpmeso wrote:
> ...
> |> Wietse Venema wrote in
> |><4bxstk189nzj...@spike.porcupine.org>:
> |>...
>
> On 21/08/2020 17:56 Steffen Nurpmeso wrote:
>
>
> Aki Tuomi wrote in
> <1907575568.4364.1597984769...@appsuite-dev-gw1.open-xchange.com>:
> |> On 21/08/2020 02:17 Steffen Nurpmeso wrote:
> ...
> |> Wietse Venema wrote in
> |><4bxstk189nzj...@spike.porcupine.org>:
> |>...
>
Aki Tuomi wrote in
<1907575568.4364.1597984769...@appsuite-dev-gw1.open-xchange.com>:
|> On 21/08/2020 02:17 Steffen Nurpmeso wrote:
...
|> Wietse Venema wrote in
|><4bxstk189nzj...@spike.porcupine.org>:
|>...
|>|Steffen Nurpmeso:
|>...
|>|> until SASL says it is done?!. Ho
> On 21/08/2020 02:17 Steffen Nurpmeso wrote:
>
>
> Hello and good evening.
>
> Sorry for responding so late, it is midsummer and i spend as much
> time as possible on the outside (bicycle, mostly). (Just one more
> day, then 10 degrees colder!!)
>
> I Cc: Wietse Venema, because i quote a
Hello and good evening.
Sorry for responding so late, it is midsummer and i spend as much
time as possible on the outside (bicycle, mostly). (Just one more
day, then 10 degrees colder!!)
I Cc: Wietse Venema, because i quote a message of him.
(this is "set quote-add-cc" here.)
Aki Tuomi wrote in
ase here, though.
When i implemented EXTERNAL authentication last year i could not
figure out how to make postfix+dovecot-SASL work with it. First
of all i had to switch configs back and forth, but in the meantime
i learned a very nice trick: if i
ase here, though.
When i implemented EXTERNAL authentication last year i could not
figure out how to make postfix+dovecot-SASL work with it. First
of all i had to switch configs back and forth, but in the meantime
i learned a very nice trick: if i
h.
When i implemented EXTERNAL authentication last year i could not
figure out how to make postfix+dovecot-SASL work with it. First
of all i had to switch configs back and forth, but in the meantime
i learned a very nice trick: if i use two password databases
passdb {
driver = passwd-file
Howdy,
I know i've asked this before, but i think i got really no answer.
I'd like to have dovecot SASL, to check AUTH against an SQL table, instead
of dovecot SASL use the AUTH MECH for imap/pop3.
I want this, to have the same behavior as I have now, where i use postfix
with
login_trusted_networks = 127.0.0.1
fixed the speed problem
Why authenticating over imap takes so slow?
my saslauthd runs like that
/usr/local/sbin/saslauthd -a rimap -O 127.0.0.1 -n 0 -r
imap server is handled by dovecot of course.
to be sure it's not sendmail i've tried testsaslauthd
testsaslauthd -u woj...@puchar.net -p mypassword
works but takes
but it seems sendmail strips domain name from entered login.
No, it is saslauthd. Check the documention and see the "-r" parameter of
saslauthd.
found it a minute before reading this e-mail. thank you
works fine. almost ;)
Why authenticating over imap takes so slow?
my saslauthd runs like
Am 24.03.2019 um 10:01 schrieb Wojciech Puchar via dovecot:
solved by setting saslauthd to authenticate over imap - through dovecot
server.
testsaslauthd shows it works fine.
but it seems sendmail strips domain name from entered login.
No, it is saslauthd. Check the documention and see the "-
On 3/24/19 10:01 AM, Wojciech Puchar via dovecot wrote:
so it will listen on the same socket.
the effect with sendmail is as below
Mar 23 21:23:29 <2.3> puchar dovecot: auth: Error: Authentication
client not compatible with this server (mixed old and new binaries?)
do i need to specify
}
so it will listen on the same socket.
the effect with sendmail is as below
Mar 23 21:23:29 <2.3> puchar dovecot: auth: Error: Authentication client not
compatible with this server (mixed old and new binaries?)
do i need to specify something while compiling sendmail to make it
compatible
i've tried to replace saslauthd with dovecot sasl service
stopped saslauthd daemon and added
service auth {
unix_listener /var/run/saslauthd/mux {
mode = 0660
user = root
group = mail
}
}
so it will listen on the same socket.
the effect with sendmail is as below
Mar 23 21:23:29
On 27.09.2017 14:57, Peter wrote:
> On 28/09/17 00:11, Aki Tuomi wrote:
>>> ssl=yes is not documented to work for the auth service and it's highly
>>> likely that it is simply ignored.
>> It is documented for inet_listener's in general and is not ignored. Any
>> dovecot inet_listener can be given
* Aki Tuomi :
>
>
> On 27.09.2017 13:21, Peter wrote:
> > On 27/09/17 20:35, Thomas Bauer wrote:
> >> service auth {
> >> inet_listener{
> >> address=192.0.0.1
> >> port=10001
> >> ssl=yes
> >> }
> >> }
> > ssl=yes is not documented to work for the auth service and it's highly
> > l
On 28/09/17 00:11, Aki Tuomi wrote:
>> ssl=yes is not documented to work for the auth service and it's highly
>> likely that it is simply ignored.
>
> It is documented for inet_listener's in general and is not ignored. Any
> dovecot inet_listener can be given this flag.
>
> You could use stunnel
On 27.09.2017 13:21, Peter wrote:
> On 27/09/17 20:35, Thomas Bauer wrote:
>> service auth {
>> inet_listener{
>> address=192.0.0.1
>> port=10001
>> ssl=yes
>> }
>> }
> ssl=yes is not documented to work for the auth service and it's highly
> likely that it is simply ignored.
It is
_security_level=encrypt
This definitely does not do what you think it does. This setting is for
the smtpd server, not the SASL client. It will enforce TLS between the
MUA (email client) and postfix. It does not affect the connection
between postfix and the dovecot SASL server at all.
The only
Am 27.09.2017 um 09:35 schrieb Thomas Bauer:
> On the postfix server in master.cf:
>
> submission inet n - - - - smtpd
>...
>-o smtpd_sasl_path=inet:192.0.0.1:10001
>...
You might use
-o smtpd_tls_security_level=encrypt
as well, to ensure postfix
Hi,
Am 27.09.2017 um 01:07 schrieb Raymond Sellars:
> Is it possible to secure the Dovecot SASL auth provider for postfix?
>
I'm using this configuration, which you've suggested.
> Has anyone managed to implement a secure internal approach they can share?
> I'
On 27/09/17 12:07, Raymond Sellars wrote:
> Hi
>
> Is it possible to secure the Dovecot SASL auth provider for postfix?
> https://wiki2.dovecot.org/HowTo/PostfixAndDovecotSASL
>
> I'm currently using the inet option to provide SASL auth to postfix for
> dovecot. Both
Hi
Is it possible to secure the Dovecot SASL auth provider for postfix?
https://wiki2.dovecot.org/HowTo/PostfixAndDovecotSASL
I'm currently using the inet option to provide SASL auth to postfix for
dovecot. Both installs are on different hosts hence the use of inet rather than
unix s
The message in my log is logged by postfix/smtpd which is using dovecot for
sasl.
Should dovecot sasl be passing the username back to postfix?
Brad
> On May 23, 2017, at 11:33 PM, Aki Tuomi wrote:
>
> In fact, looking again, dovecot should log the failure with username, if
&g
gt;>> Aki
>>>
>>>
>>> On 23.05.2017 03:23, Bradley Giesbrecht wrote:
>>>> dovecot 2.2.22
>>>> postfix 3.1.1
>>>>
>>>> I’m seeing "SASL NTLM authentication failed: {long_hash}” in mail.log.
>>>>
>>>> Is there a way to log the SASL username?
>>>>
>>>> I think postfix is logging what Dovecot SASL is returning so I hope I am
>>>> asking on the right list.
>>>>
>>>>
>>>> Regards,
>>>> Bradley Giesbrecht (pixilla)
s. At the moment it's not possible to log this.
>>
>> Aki
>>
>>
>> On 23.05.2017 03:23, Bradley Giesbrecht wrote:
>>> dovecot 2.2.22
>>> postfix 3.1.1
>>>
>>> I’m seeing "SASL NTLM authentication failed: {long_hash
{long_hash}” in mail.log.
>>
>> Is there a way to log the SASL username?
>>
>> I think postfix is logging what Dovecot SASL is returning so I hope I am
>> asking on the right list.
>>
>>
>> Regards,
>> Bradley Giesbrecht (pixilla)
;
> I’m seeing "SASL NTLM authentication failed: {long_hash}” in mail.log.
>
> Is there a way to log the SASL username?
>
> I think postfix is logging what Dovecot SASL is returning so I hope I am
> asking on the right list.
>
>
> Regards,
> Bradley Giesbrecht (pixilla)
dovecot 2.2.22
postfix 3.1.1
I’m seeing "SASL NTLM authentication failed: {long_hash}” in mail.log.
Is there a way to log the SASL username?
I think postfix is logging what Dovecot SASL is returning so I hope I am asking
on the right list.
Regards,
Bradley Giesbrecht (pixilla)
On Mon, 2015-12-14 at 17:53 -0500, Ranbir wrote:
> Is it possible in Dovecot to translate the mail address lookup from
> postfix into just a "uid" search? If I could do that, Dovecot would
> find "ranbir" and report back to postfix the user exists.
I sent this and then realized I could just strip
On Mon, 2015-12-14 at 09:10 -0600, Manuel Delgado wrote:
> This is more a postfix question but I have done this configs before
> in a
> BETA-Lab and it's a real pain. I'll be glad to help if I can.
>
> I my environment I had postfix directly authenticating SASL with the
> IPA
> server (FreeIPA) us
ormática
On Sun, Dec 13, 2015 at 11:21 AM, Ranbir wrote:
> Hi Everyone,
>
> I'm currently using dovecot SASL in postfix and passwd-file in dovecot
> for authenticating my users. I want to switch to using IPA instead.
>
> I have both the postfix (mailman01) and dovecot (mailma
Hi Everyone,
I'm currently using dovecot SASL in postfix and passwd-file in dovecot
for authenticating my users. I want to switch to using IPA instead.
I have both the postfix (mailman01) and dovecot (mailman02) servers
joined to the IPA domain. I have GSSAPI working in dovecot for IMAP
y.
Using FreeBSD here, not Debian.
I have no chroot configured for Postfix at all. The wiki page does not clearly
mention this requirement.
> Quoting Dan Langille :
>
>> I wanted to mention I updated the Postfix and Dovecot SASL wiki entry
>> yesterday.
>
Disabling chroot doesn't fix the issue, it just worked around it.
Aparently your chroot is not configured correctly, likely using debian
based system, and your resolv.conf in the chroot is not updated
correctly.
Quoting Dan Langille :
I wanted to mention I updated the Postfix and Do
I wanted to mention I updated the Postfix and Dovecot SASL wiki entry yesterday.
http://wiki2.dovecot.org/HowTo/PostfixAndDovecotSASL
The entry:
submission inet n - - - - smtpd
was incorrect. It should be:
submission inet n - n - - smtpd
By specifying n for chroot, it ensures that DNS
On Mon, 18 Mar 2013 19:43:49 +0100
Benny Pedersen articulated:
> Jerry skrev den 2013-03-18 13:48:
>
> > smtp_sasl_type = dovecot
>
> smtpd_ vs smtp_ :)
Crap, I looked at the settings for hours and never picked up on
that. I knew it was something exceedingly stupid on my part.
Thanks!
--
Jer
Jerry skrev den 2013-03-18 13:48:
smtp_sasl_type = dovecot
smtpd_ vs smtp_ :)
Okay, I wasn't going to try and fix up the messed up mail server I was
given; however, I decided that I might as well try.
Situation:
The system has a Postfix MTA and uses Dovecot for LDA and Cyrus-SASL
for SASL. That works fine.
I decided that I wanted to switch over to Dovecot for SASL. doveco
On Sun, 17 Mar 2013 17:27:04 +0100
Reindl Harald articulated:
>
> Am 17.03.2013 14:08, schrieb Jerry:
> >> the main benefit of dovecot SASL is that SMTP auth is
> >> using exactly the same users/passwords and auth-mechs
> >> as imap/pop3 - so i do not understand
Am 17.03.2013 14:08, schrieb Jerry:
>> the main benefit of dovecot SASL is that SMTP auth is
>> using exactly the same users/passwords and auth-mechs
>> as imap/pop3 - so i do not understand why you want create
>> anything special
>
> Because that is the way the sy
On 2013-03-17 9:08 AM, Jerry wrote:
Because that is the way the system was originally configured. I had
nothing to do with it.
The system uses a simple format:
u...@doman.com password
The SASL mechanism presently in use uses:
u...@hostname.domain.compassword
Worse,
On Sun, 17 Mar 2013 13:21:38 +0100
Reindl Harald articulated:
> Am 17.03.2013 13:04, schrieb Jerry:
> > I am currently using Postfix with Dovecot and Cyrus-SASL. I want to
> > switch over to Dovecot SASL. The regular Dovecot user/password file
> > is not the same as the fi
Am 17.03.2013 13:04, schrieb Jerry:
> I am currently using Postfix with Dovecot and Cyrus-SASL. I want to
> switch over to Dovecot SASL. The regular Dovecot user/password file is
> not the same as the file used by cyrus-sasl
> I created a flat file that dovecot can use for SASL l
This is probably a dumb question, but I'll ask anyway.
I am currently using Postfix with Dovecot and Cyrus-SASL. I want to
switch over to Dovecot SASL. The regular Dovecot user/password file is
not the same as the file used by cyrus-sasl. Usewr names and passwords
are different. I created a
On 26.2.2013, at 1.55, Thomas Reim wrote:
> I use Dovecot SASL (2.1.15) on Ubuntu 12.04 for IMAP authentication and
> Postfix SASL authentication. I tried to setup SCRAM-SHA-1 as SASL
> mechanism. This works well on Dovecot's client side towards my OpenLDAP
> server (with libs
Dear all,
I use Dovecot SASL (2.1.15) on Ubuntu 12.04 for IMAP authentication and
Postfix SASL authentication. I tried to setup SCRAM-SHA-1 as SASL
mechanism. This works well on Dovecot's client side towards my OpenLDAP
server (with libsasl-2), but fails on the server side (IMAP and SMTP).
I
Charles Marcus skrev den 2013-01-08 21:39:
I would just like to be able tell postfix to use dovecot-sasl for
client side auth as well as server side, so I don't have to maintain
cyrus-sasl just for the client side part.
http://wiki.dovecot.org/HowTo/PostfixAndDovecotSASL
it have worked
* Aleksandar Lazic :
>
> Am 09-01-2013 11:36, schrieb Markus Schönhaber:
> >09.01.2013 09:52, Patrick Ben Koetter:
> >
> >>If it is as good as GNUTLS, I'd rather stick with Cyrus SASL.
> >
> >Out of curiosity: what's so bad with GNUTLS?
>
> +1
>
> I thought the same, you was faster for the quest
Am 09-01-2013 11:36, schrieb Markus Schönhaber:
09.01.2013 09:52, Patrick Ben Koetter:
If it is as good as GNUTLS, I'd rather stick with Cyrus SASL.
Out of curiosity: what's so bad with GNUTLS?
+1
I thought the same, you was faster for the question.
BR Aleks
09.01.2013 09:52, Patrick Ben Koetter:
> If it is as good as GNUTLS, I'd rather stick with Cyrus SASL.
Out of curiosity: what's so bad with GNUTLS?
--
Regards
mks
* Timo Sirainen :
> Then there's the whole other question of whether that client side SASL code
> could be exported to a separate library, possibly even API compatible with
> Cyrus SASL. I think that's unlikely to happen, especially because the code
> most likely would require libdovecot.so, which
On 8.1.2013, at 15.40, Charles Marcus wrote:
> I seem to recall mention of SASL client support either being added, but can't
> remember for sure. The wiki says nothing about Client support (now, or in the
> future)...
>
> http://wiki2.dovecot.org/Sasl
>
> So - is there support for it now? If
* Ed W :
> Hi
>
> >At the moment Dovecot does not implement an SMTP/LMTP client. This might
> >change, when Timo decides to implement all of the LEMONADE feature, which at
> >some point require the IMAP server to edit and send messages on behalf of a
> >(mobile) client. Timo will shed more light o
fix to use dovecot-sasl for client
side auth as well as server side, so I don't have to maintain cyrus-sasl
just for the client side part.
That is all.
--
Best regards,
Charles
Hi
At the moment Dovecot does not implement an SMTP/LMTP client. This might
change, when Timo decides to implement all of the LEMONADE feature, which at
some point require the IMAP server to edit and send messages on behalf of a
(mobile) client. Timo will shed more light on his plans.
Are you
* /dev/rob0 :
> On Tue, Jan 08, 2013 at 08:59:09AM -0500, Charles Marcus wrote:
> > So that postfix can use dovecot-sasl for remotely authenticating
> > against another SMTP server, ie, for secure relays...
>
> I don't think this makes sense for Dovecot to implement -- m
SABLE the 'Save copy to Sent
folder' option in mail clients and do that on the server so the message doesn't
have to be transferred over the
wire twice, which is one thing I *love* about gmail)
that would make dovecot to a MTA,
No it wouldn't, any more than having dovecot-sasl
Am 08.01.2013 18:55, schrieb Charles Marcus:
> I absolutely do recall Timo discussing implementing it at some point - this
> way dovecot could actually provide its
> own submission agent (one reason I'd love to see this would be the ability to
> DISABLE the 'Save copy to Sent
> folder' option
ublic network
(like the internet)? Right now I have to use (as you pointed out)
cyrus-sasl, because dovecot-sasl doesn't (apparently) support
client-side sasl at this time. I'd prefer to not have to install
cyrus-sasl just to do it.
On 2013-01-08 12:12 PM, /dev/rob0 wrote:
I don't e
On Tue, Jan 08, 2013 at 08:59:09AM -0500, Charles Marcus wrote:
> So that postfix can use dovecot-sasl for remotely authenticating
> against another SMTP server, ie, for secure relays...
I don't think this makes sense for Dovecot to implement -- maybe
P@rick and/or Timo will correct t
Am 08.01.2013 16:43, schrieb Urban Loesch:
> For this you don't need dovecot on your site.
>
> I use it as follows on my debian lenny.
> installed packages: postfix, libsasl2-modules
> needed main.cf configuration options:
>
> ...
> relayhost = [the.relayserver.com]
> smtp_sasl_auth_enable = ye
HowTo/PostfixAndDovecotSASL
* dovecot supports authentication for POP3/IMAP
so hich sort fo "client support" are you missing?
CLIENT support... do you not understand the difference?
http://www.postfix.org/SASL_README.html#client_sasl
So that postfix can use dovecot-sasl for remotely authenticating a
n for POP3/IMAP
so hich sort fo "client support" are you missing?
CLIENT support... do you not understand the difference?
http://www.postfix.org/SASL_README.html#client_sasl
So that postfix can use dovecot-sasl for remotely authenticating against
another SMTP server, ie, fo
Am 08.01.2013 14:40, schrieb Charles Marcus:
> Hi all,
>
> I seem to recall mention of SASL client support either being added, but can't
> remember for sure. The wiki says
> nothing about Client support (now, or in the future)...
>
> http://wiki2.dovecot.org/Sasl
>
> So - is there support for
Hi all,
I seem to recall mention of SASL client support either being added, but
can't remember for sure. The wiki says nothing about Client support
(now, or in the future)...
http://wiki2.dovecot.org/Sasl
So - is there support for it now? If not, is it planned for anytime soon?
Thanks,
--
You should get AUTH after you STARTTLS.
Bill
On 9/3/2012 5:10 AM, tseveendorj wrote:
Hello,
I'm trying to configure postfix + Dovecot SASL for user authenticated
mail relay.
I set following configuration on postfix
queue_directory = /var/spool/postfix
smtpd_sasl_auth_enable
Hello,
I'm trying to configure postfix + Dovecot SASL for user authenticated
mail relay.
I set following configuration on postfix
queue_directory = /var/spool/postfix
smtpd_sasl_auth_enable = yes
smtpd_sasl_type = dovecot
smtpd_sasl_path = private/auth
smtpd_sasl_authenticated_header
On 05/24/2012 05:28 PM, Sandro Tosi wrote:
With this setup, we're able to use AUTH LOGIN method on an SMTP session,
but using AUTH PLAIN fails.
It turned out to be a problem in the encoding of the AUTH PLAIN string.
Sorry for the noise,
--
Sandro Tosi
Product Engineer
Shared Hosting Products
R
Hello,
we're trying to setup a platform with authenticated SMTP with exim and
relying on dovecot as auth agent.
We've read http://wiki2.dovecot.org/HowTo/EximAndDovecotSASL and so made
the changes mentioned there, also setting
auth_mechanisms = plain login
in conf.d/10-auth.conf .
With thi
1 - 100 of 276 matches
Mail list logo
