Re: 2.3.0 upgrade from 2.2.x

[Aki Tuomi]

> On December 28, 2017 at 4:15 AM "Fabian A. Santiago" 
>  wrote:
> 
> 
> On December 27, 2017 8:07:18 PM EST, "Fabian A. Santiago" 
>  wrote:
> >Question; So after updating to 2.3.0 and following the recommended
> >warnings / changes from running doveconf -n and then doing that same
> >command > "a new conf file", and then renaming the conf files and
> >restarting dovecot, I should be good to go with my old config updated
> >to the new config spec? Just confirming. Thanks. 
> >
> >What I mean is doing the -n to a new file hasn't changed or removed
> >anything from my old config? Unless it was a changed or obsoleted
> >option and in that case it would have warned me anyway, correct? 
> >--
> >
> >Thanks,
> >
> >Fabian S.
> >
> >OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

Yeah, it should tell you if you have deprecated options or something that needs 
looking into.

Aki

Re: 2.3.0 upgrade from 2.2.x

[Fabian A. Santiago]

On December 27, 2017 8:07:18 PM EST, "Fabian A. Santiago" 
 wrote:
>Question; So after updating to 2.3.0 and following the recommended
>warnings / changes from running doveconf -n and then doing that same
>command > "a new conf file", and then renaming the conf files and
>restarting dovecot, I should be good to go with my old config updated
>to the new config spec? Just confirming. Thanks. 
>
>What I mean is doing the -n to a new file hasn't changed or removed
>anything from my old config? Unless it was a changed or obsoleted
>option and in that case it would have warned me anyway, correct? 
>--
>
>Thanks,
>
>Fabian S.
>
>OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC


--

Thanks,

Fabian S.

OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

2.3.0 upgrade from 2.2.x

[Fabian A. Santiago]

Question; So after updating to 2.3.0 and following the recommended warnings / 
changes from running doveconf -n and then doing that same command > "a new conf 
file", and then renaming the conf files and restarting dovecot, I should be 
good to go with my old config updated to the new config spec? Just confirming. 
Thanks. 

What I mean is doing the -n to a new file hasn't changed or removed anything 
from my old config? Unless it was a changed or obsoleted option and in that 
case it would have warned me anyway, correct? 
--

Thanks,

Fabian S.

OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC