similar to: Indexing Performance Question (was tpop3d vs dovecot)

Hello, I am new to the list and have spent extensive time researching performance suggestions through the list and the documentation. Particularly interesting is the recent performance thread related to the upcoming release. I just upgraded one of our email servers from tpop3d to dovecot 1.0rc19. tpop3d has served us well for many years; however, it basically has lost all it's support

Hello All! I am new to this list so I hope I'm not in the wrong list with my question. First, I have to say that dovecot is (in my opinion) one of the best POP3/IMAP servers arround. I especialy like its' simplicity (configuration) and powerfullness (speed, auth mechs). In my production environment I would like to cange from tpop3d to dovecot, but I have only one little problem :).

Hi, Here is an updated patch which allows to use tpop3d compatible UIDL in dovecot (it's against 1.0rc1): http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/dovecot-tpop3d-uidl.patch?rev=1.2 which is based on: http://dovecot.org/pipermail/dovecot/2006-March/012080.html Please consider merging it. -- Arkadiusz Mi?kiewicz PLD/Linux Team arekm / maven.pl

Hello, I've attached a patch that adds an additional expando to pop3_uidl_format. The additional expando (%M) expands to the md5sum of the filename (which is already available via %f.) This UIDL style is compatible with tpop3d when using Maildir. The patch is against dovecot 1.0 beta3, and I'd love to see it be merged into the official tree. Comments welcome. -- Ben Winslow

Yes, again! :) I googled this issue but found no solution. Then, simple question - on this moment, it is possible without losing UIDLs or not?

Hi people, I am trying to migrate some users from tpop3d (Maildir mailboxes) to dovecot. The most important aspect of this migration, and which I cannot seem to get right, is to first be able to make dovecot to authenticate against the current DB being used by tpop3d so that I can use imapsync to transfer the user mails. And I do believe that is what I am unable to get right!! So here goes what

================================================================= "Never refuse any advance of friendship, for if nine out of ten bring you nothing, one alone may repay you." Madame de Tencin ================================================================= Release Announcements ===================== This is the latest bugfix release release of the Samba 3.3

================================================================= "Never refuse any advance of friendship, for if nine out of ten bring you nothing, one alone may repay you." Madame de Tencin ================================================================= Release Announcements ===================== This is the latest bugfix release release of the Samba 3.3

Hi, sys: Centos 5.2 x86_64 Trying to switch from sendmail to postfix I did: # yum remove sendmail which resulted in erasing of: mdadm sendmail-doc sendmail sendmail-cf mutt fetchmail redhat-lsb I did then: yum -y install redhat-lsb.x86_64 postfix and got this error: Installing: postfix ######################### [1/2] postfix: fatal: file /etc/postfix/main.cf:

Sending (in my case: forwarding) messages from Sieve via sendmail does not work with version 2.3.1. I have narrowed it down to this simple test case: # dovecot -n # 2.3.1 (c5a5c0c82): /etc/dovecot/dovecot.conf # OS: Linux 4.4.0-119-generic x86_64 Ubuntu 16.04.4 LTS # Hostname: tuxi.topfen.net first_valid_gid = 200 first_valid_uid = 200 mail_location = mbox:~/mail passdb { args =

Hi I have a problem with doveadm and flush # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24.rc1 (debaa297) # OS: Linux 3.16.0-5-amd64 x86_64 Debian 8.10 example: #doveadm director status mail server ip tag vhosts state state changed users 10.0.100.24??????? 1????? up??? -???????????? 65 10.0.100.25??????? 100??? up??? -???????????? 989 #doveadm director flush

Op 12/30/2017 om 6:47 AM schreef tony: > On 2017-12-29 18:35, tony wrote: >> I did some more digging around and found this is reproducible on >> multiple hosts running the same version of Dovecot/Pigeonhole/Postfix. >> The problem resurfaces on any host to an account with enabled >> Vacation/OOO response. The Vacation/OOO reply filter was created in >>

Hi All, I'm running CentOS 5.2 with SELinux in enforcing mode (default targeted policy). The server hosts a PHP web app that sends mail. I'm getting the following errors (see end of message) in my selinux audit.log file every time the app sends an email. The email always seems to get sent successfully, despite the log messages. However, they do concern me and I would like to understand

On 2017-12-29 18:35, tony wrote: > I did some more digging around and found this is reproducible on > multiple hosts running the same version of Dovecot/Pigeonhole/Postfix. > The problem resurfaces on any host to an account with enabled > Vacation/OOO response. The Vacation/OOO reply filter was created in > Roundcubemail, but has been fine for years. One thing to note is in >

On 02/01/18 14:07, Stephan Bosch wrote: >> I can see 21:21:38 is when the below errors showed up with the above >> 21:21:38 timestamps: >> >> Dec 29 21:21:38 >> lmtp(recipient at domain.net)<17187><UA2fMEQiR1ojQwAAUXb6+w>: Error: >> program `/usr/sbin/sendmail' was forcibly terminated with signal 15 >> Dec 29 21:21:38 >>

On 2018-01-02 17:21, tony wrote: > On 2018-01-02 16:37, tony wrote: >> On 2018-01-01 17:26, Peter wrote: >>> On 02/01/18 14:07, Stephan Bosch wrote: >>>>> I can see 21:21:38 is when the below errors showed up with the >>>>> above >>>>> 21:21:38 timestamps: >>>>> >>>>> Dec 29 21:21:38 >>>>>

On 2018-01-02 16:37, tony wrote: > On 2018-01-01 17:26, Peter wrote: >> On 02/01/18 14:07, Stephan Bosch wrote: >>>> I can see 21:21:38 is when the below errors showed up with the above >>>> 21:21:38 timestamps: >>>> >>>> Dec 29 21:21:38 >>>> lmtp(recipient at domain.net)<17187><UA2fMEQiR1ojQwAAUXb6+w>: Error:

After upgrading to centos 5.4 I am getting a selinux violation, yet nothing is logged to /var/log/audit/audit.log. Other violations do get logged. The violation occurs when running the following command on the mail server: aspen> /usr/bin/Mail centos at centos.org Subject: test hi Cc: aspen> send-mail: warning: premature end-of-input on /usr/sbin/postdrop -r while reading input

On 2018-01-01 17:26, Peter wrote: > On 02/01/18 14:07, Stephan Bosch wrote: >>> I can see 21:21:38 is when the below errors showed up with the above >>> 21:21:38 timestamps: >>> >>> Dec 29 21:21:38 >>> lmtp(recipient at domain.net)<17187><UA2fMEQiR1ojQwAAUXb6+w>: Error: >>> program `/usr/sbin/sendmail' was forcibly

On Thu, May 11, 2017 at 7:58 PM, Alexander Dalloz <ad+lists at uni-x.org> wrote: > Am 11.05.2017 um 20:30 schrieb Larry Martell: >> >> On Wed, May 10, 2017 at 3:19 PM, Larry Martell <larry.martell at gmail.com> >> wrote: >>> >>> On Wed, May 10, 2017 at 3:07 PM, Jonathan Billings <billings at negate.org> >>> wrote: >>>>