Re: 2.3.0 upgrade from 2.2.x

> 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

Re: Question about imap (expunge response)

Bron Gondwana writes: > Yeah, that smells bogus. You can't send the EXPUNGE right away, even if [...] Thank for confirmation > Having said that, fetchmail is also wrong here: > > fetchmail: IMAP> A0008 STORE 1 +FLAGS.SILENT (\Seen \Deleted) fetchmail: > IMAP< * 1 EXPUNGE

Re: 2.3.0 upgrade from 2.2.x

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

2.3.0 upgrade from 2.2.x

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?

Re: Package repository now available

On December 27, 2017 4:38:02 PM EST, Aki Tuomi wrote: > >> On December 27, 2017 at 6:11 PM Aki Tuomi >wrote: >> >> >> >> > On December 27, 2017 at 6:05 PM "Fabian A. Santiago" > wrote: >> > >> > >> > December 27, 2017

Re: Renewing certificates

Kenneth Porter writes: Thanks. Some digging indicates that this is equivalent to doveadm reload. Both paths ultimately send a SIGHUP to the server which initiates a full reload of the configuration. I'll be combining this with a restart of sendmail. Alas, I don't see a

Re: Ubuntu Auth Issues with new repository code..

On 12/27/17 4:38 PM, Howard Leadmon wrote: >    Saw the new repository notification, and figured what the heck I > would try letting it upgrade me from the current v2.2.22 release that > apparently is in the Ubuntu 16.04 packages, to the new repository > release of v2.3.0. > >  I followed the

Re: Ubuntu Auth Issues with new repository code..

Another thing to check is the RPM scripts that run during an upgrade. Compare the output of "rpm -q --scripts dovecot" for the old and new package. See if the new package is doing all the necessary things expected by Ubuntu. Scripts are the most platform-specific part of the package and the

Re: Ubuntu Auth Issues with new repository code..

The problem would appear that pam is reporting a system error, which fails your authentication. Are you supposed to be using pam? Aki > On December 28, 2017 at 12:50 AM Howard Leadmon wrote: > > >   I hear what your saying, but if you read and follow the repo page, it >

Re: Ubuntu Auth Issues with new repository code..

  I hear what your saying, but if you read and follow the repo page, it says run update, and then upgrade.   Also as a test, I did remove the old 2.2 code, and installed the new 2.3 code, and again authentication fails.  I am sure I may be missing something stupid, but the bottom line is,

Re: Ubuntu Auth Issues with new repository code..

On 28/12/2017 07:38, Howard Leadmon wrote: > Saw the new repository notification, and figured what the heck I would try > letting it upgrade me from the current v2.2.22 release that apparently is in > the Ubuntu 16.04 packages, to the new repository release of v2.3.0. > > I followed the info

Re: Package repository now available

> On December 27, 2017 at 6:11 PM Aki Tuomi wrote: > > > > > On December 27, 2017 at 6:05 PM "Fabian A. Santiago" > > wrote: > > > > > > December 27, 2017 10:53 AM, aki.tu...@dovecot.fi wrote: > > > > > Small amendment... > > > > > > if

Ubuntu Auth Issues with new repository code..

   Saw the new repository notification, and figured what the heck I would try letting it upgrade me from the current v2.2.22 release that apparently is in the Ubuntu 16.04 packages, to the new repository release of v2.3.0.  I followed the info on repo.dovecot.org, and first it started

Re: Package repository now available

Should be fixed now. Aki > On December 27, 2017 at 8:32 PM Aki Tuomi wrote: > > > Thank you for your report, we'll look into it! > > Aki > > > On December 27, 2017 at 8:16 PM Florent B wrote: > > > > > > Hi, > > > > This repository does not

Re: Renewing certificates

--On Wednesday, December 27, 2017 9:24 AM -0500 Bill Shirley wrote: --reloadcmd "systemctl reload dovecot.service" Notice the --reloadcmd. Thanks. Some digging indicates that this is equivalent to doveadm reload. Both paths ultimately send a SIGHUP to the

Re: Package repository now available

Thank you for your report, we'll look into it! Aki > On December 27, 2017 at 8:16 PM Florent B wrote: > > > Hi, > > This repository does not work with Aptly. > It seems "architecture" line is wrong in InRelease file (needs to be > "Architectures:" instead of

Re: Package repository now available

> On December 27, 2017 at 6:05 PM "Fabian A. Santiago" > wrote: > > > December 27, 2017 10:53 AM, aki.tu...@dovecot.fi wrote: > > > Small amendment... > > > > if you ran > > > > gpg --export > /etc/apt/trusted.gpg.d/dovecot.gpg > > > > please run > > > > gpg

Re: Package repository now available

December 27, 2017 11:06 AM, "Fabian A. Santiago" wrote: > December 27, 2017 10:53 AM, aki.tu...@dovecot.fi wrote: > >> Small amendment... >> >> if you ran >> >> gpg --export > /etc/apt/trusted.gpg.d/dovecot.gpg >> >> please run >> >> gpg --export ED409DA1 >

Re: Package repository now available

December 27, 2017 10:53 AM, aki.tu...@dovecot.fi wrote: > Small amendment... > > if you ran > > gpg --export > /etc/apt/trusted.gpg.d/dovecot.gpg > > please run > > gpg --export ED409DA1 > /etc/apt/trusted.gpg.d/dovecot.gpg > > Aki > >> On December 27, 2017 at 5:00 PM aki.tu...@dovecot.fi

Re: Package repository now available

Small amendment... if you ran gpg --export > /etc/apt/trusted.gpg.d/dovecot.gpg please run gpg --export ED409DA1 > /etc/apt/trusted.gpg.d/dovecot.gpg Aki > On December 27, 2017 at 5:00 PM aki.tu...@dovecot.fi wrote: > > > Dovecot now has package repository for Debian, CentOS and Ubuntu

Re: Package repository now available

Yes. Aki > On December 27, 2017 at 5:05 PM azu...@pobox.sk wrote: > > > Are provided packages suitable for production usage? > > > > > > Citát aki.tu...@dovecot.fi: > > > Dovecot now has package repository for Debian, CentOS and Ubuntu > > available at https://repo.dovecot.org/ > > > >

Re: Package repository now available

Are provided packages suitable for production usage? Citát aki.tu...@dovecot.fi: Dovecot now has package repository for Debian, CentOS and Ubuntu available at https://repo.dovecot.org/ Packages are provided for 2.3 series and forward. Please let us know if you run into any trouble

[Dovecot-news] Package repository now available

Dovecot now has package repository for Debian, CentOS and Ubuntu available at https://repo.dovecot.org/ Packages are provided for 2.3 series and forward. Please let us know if you run into any trouble with these. --- Aki Tuomi Dovecot oy ___

Package repository now available

Dovecot now has package repository for Debian, CentOS and Ubuntu available at https://repo.dovecot.org/ Packages are provided for 2.3 series and forward. Please let us know if you run into any trouble with these. --- Aki Tuomi Dovecot oy

Re: dovecot-submission SMTP send error with Thunderbird (BODY=8BITMIME)

Op 12/24/2017 om 7:54 AM schreef Reuben Farrelly: > Hi again, > > On 24/12/2017 7:11 am, Stephan Bosch wrote: >> Op 12/23/2017 om 7:18 AM schreef Reuben Farrelly: >>> Hi, >>> >>> With latest 2.3 -git (and 2.3.0 release), I'm running into this error >>> with Thunderbird: >>> >>> "An error occurred

Re: Renewing certificates

I'm using acme.sh to get my Let's Encrypt certificates.  The install command is: acme.sh --installcert -d imap.example.com \     --keypath /etc/pki/dovecot/private/imap.example.com.pem \     --certpath /etc/pki/dovecot/certs/imap.example.com.crt \     --fullchainpath