On Sun, Feb 19, 2012 at 06:45:14PM -0500, Wietse Venema wrote:
> Peter:
> > On 20/02/12 11:14, Wietse Venema wrote:
> > > Peter:
> > >> Note that if you put the old config in dovecot will give
> > >> a warning on startup and `doveconf -n' will show the new
> > >> config that you should replace it w
Am 20.02.2012 00:45, schrieb Wietse Venema:
> Peter:
>> On 20/02/12 11:14, Wietse Venema wrote:
>>> Peter:
Note that if you put the old config in dovecot will give a warning on
startup and `doveconf -n' will show the new config that you should
replace it with.
>>>
>>> http://www.po
Peter:
> On 20/02/12 11:14, Wietse Venema wrote:
> > Peter:
> >> Note that if you put the old config in dovecot will give a warning on
> >> startup and `doveconf -n' will show the new config that you should
> >> replace it with.
> >
> > http://www.postfix.org/SASL_README.html was updated for Postf
On 20/02/12 11:14, Wietse Venema wrote:
> Peter:
>> Note that if you put the old config in dovecot will give a warning on
>> startup and `doveconf -n' will show the new config that you should
>> replace it with.
>
> http://www.postfix.org/SASL_README.html was updated for Postfix 2.9.
> What are th
Peter:
> Note that if you put the old config in dovecot will give a warning on
> startup and `doveconf -n' will show the new config that you should
> replace it with.
http://www.postfix.org/SASL_README.html was updated for Postfix 2.9.
What are the errors?
Wietse
The dovecot config listed in the SASL_README is obsoleted for dovecot
2.0, it should probably be updated to reflect that. I'm not sure
exactly what should go in the SASL_README file but I'll show the
relevant part of my own dovecot config (which uses an sql db for
authentication, not pam):
auth_m
