similar to: upgrading: should I and what will change?

Since FreeBSD has decided to drop Dovecot 0.99 and only provide a port for 1.0alpha4, what are the considerations for upgrading from 0.99.14 to 1.0a4? Thanks, Jim -- Jim Trigg, Lord High Everything Else O- /"\ Hostmaster, Huie Kin family website \ / ASCII RIBBON CAMPAIGN Verger and System Administrator, X HELP CURE HTML MAIL All Saints Church - Sharon Chapel

I realize that there have been some big changes in features and configuration file settings between 0.99.xx and 1.0-stable, so when I went to perform an upgrade on our testing server, I carefully combed through the configuration files and matched up everything I could. I fired up dovecot-1.0-stable and was pleased to see that it was happily running. I attempted to connect to it, and

OK. After checking the 0.99->1.0 migration documentation, it seems I've been a little confused between customflags and keywords. (Though this is partly due to my repeated requests for clarification being ignored.) The page (http://wiki.dovecot.org/moin.cgi/UpgradingDovecot) says 1.0 does not use .customflags any more. Now, I'm hoping they're still supported, in which case

Hi all, I originally posted this on postfix's mailing list but then realized that this COULD be a pop3 server problem since that downloads and deletes mail. This has only been happening since I upgraded from .99 to 1.0-7 ... Our users have been reporting double messages in their inbox, as well as emails that they deleted a long time ago reappearing. The only thing in my maillog is a

[Sending this again from the email account that I actually have subscribed to the list - hopefully won't be a dup...] We have been running dovecot-0.99.11-2.EL4.rpm on CentOS4 (since that's the latest that ships with RHEL/CentOS) for a while. Aalso in parallel, we have been running various 1.0 betas and RCs on a different port for a different set of more test-tolerant users. This

I just installed the latest alpha on Debian Sarge and am getting a lot of this sort of error: Oct 4 16:18:58 tarsier dovecot: imap-login: Disconnected: rip=70.209.254.178, lip=192.168.50.105, TLS Oct 4 16:19:04 tarsier dovecot: imap(jeff): mbox sync: UID inserted in the middle of mailbox /home/jeff/mail/Junk (329 > 274, seq=2, idx_msgs=55) Oct 4 16:19:07 tarsier dovecot: imap(jeff): mbox

I have installed dovecot version 0.99.11 on my Slackware 10.1 system recently and it basically works as expected. However I can't get it to 'see' existing mbox hierarchies. I have the following in dovecot.conf:- default_mail_env = mbox:/home/%u/Mail:INBOX=/var/mail/%u (I also originally tried with %h/Mail) IMAP MUAs can see the INBOX OK but I can't get them to see any of

We're getting ready to set up a new mail server running dovecot 0.99.11 (CentOS 4) with maildir and filesystem quotas. I saw on the Dovecot web site that "hard filesystem quota can also be problematic." How problematic? What problems might we anticipate? Thanks. Josh Kelley

I have been reading up : http://wiki.dovecot.org/moin.cgi/DovecotPostgresql to create virtual users who can access the email. Can i follow these steps with a few changes to get to use mysql instead of Postgresql ? Also i dont know if u all can help.. but i have tried to do : SASL2 authentication configuration in main.cf(Postfix): smtpd_recipient_restrictions = permit_sasl_authenticated,

Hi, One of my users can't read message of his Inbox, he can view subject of message with Thunderbird or Squirrelmail and IMAP but when he click on a message in order to read it he has thess messages with Thunderbird : The current command did not succeed. Invalidmessageset: 1181461470:-1181461446. ou 1181461444:* ou 1181461444:-1181461445 with Squirrelmail : SquirrelMail: ERREUR ERREUR: Le

I am using Dovecot to provide IMAP and IMAP+SSL service for my users, but am still using QPopper for POP3 service, wrapped with stunnel for POP3+SSL. I am hesitant to get rid of QPopper because it supports APOP, which encrypts authentication data (both where it is stored, and when it is transmitted), and because APOP passwords can be managed by the users themselves, via the popauth tool that they

Hi, I have just noticed that one our box is still running ancient 0.99 version (shame on me). Is there anything what I have to take care about during update? I am completely aware about changes in configuration files so my question is mainly about existing maildirs. L??a -------------- next part -------------- An HTML attachment was scrubbed... URL:

I've noticed that there are some parameters mentioned in the docs that aren't identified therein (ie: login_process_per_use). Is there a more generic set of docs that can identify what each of the parameters and what they do, or at least something that will allow me a simple how to to avoid embarrasing situations. I supposed I should only settle for ssl based connections (imaps/pops)

Hi all, I was looking to upgrade my dovecot .99.14 installation to 1.0alpha5 today and bumped into an issue. My setup is on Mac OS X 10.4 and I am using After reading http://wiki.dovecot.org/UpgradingDovecot , I created a default dovecot.conf file with the following information grabbed from my prior installation: Snow:~ ed$ grep -v '^ *#' /usr/local/etc/dovecot.conf|grep -v ^$

Just built one and figured I'd write down what I did :) Still needing some web thingy to configure it. At least a password changer plugin for Squirrelmail. http://wiki.dovecot.fi/moin.cgi/DovecotPostgresql

I need to migrate an old mail server running Dovecot (0.99.14) to a new server running Dovecot (1.0.7; as shipped with CentOS 5.2). My plan was to use the imapsync utility as this will "seamlessly" do the conversion from mbox to maildir between the boxes as well. I've got the MasterUser authentication working fine on the new host and was just about to start getting

On 21/02/18 22:30, Fabian Arrotin wrote: > That's a good question, as we'll also have to migration for moinmoin if > we can't find a support path to migrate to supported version anyway. > So first question (already asked on the list) : is there a way to get in > touch with moin people willing to help/assist us ? (as their upgrade > tool wasn't working to test

In case anyone besides me is interested, installing these packages on CentOS4.2 seems to work. You can determine the correct mirror to use from: http://www.postgresql.org/ftp/binary/v8.0.4/linux/rpms/redhat/rhel- es-4/ The rpm command that I used was: rpm --upgrade --nodeps --hash -v <package url> Packages in order of installation:

On Mon, Apr 11, 2016 at 10:37 AM, Karsten Wade <kwade at redhat.com> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 04/11/2016 09:18 AM, Jim Perrin wrote: >> What are the thoughts or concerns about this sort of workflow >> change? > > Any chance Moin Moin can store wiki source in git and sync > automatically with a central git repository?

Hello, world! I have a long-running Dovecot & Postfix installation using PostgreSQL back-end. Until now I've been using MD5 hashing but would like to "upgrade" to the salted SSHA512. Is there a way to configure Dovecot so that it would automatically detect the type of the hash stored in the database, so that users who have changed their password (and thus being hashed with