similar to: 1.0-test20

Hi I use rsync as a client to copy a directory structure from a remote server, once every month. Until a few weeks ago, we had direct access to the internet - and the way it would work is that the guy maintaining the rsync server would add my machine's IP to an access list and I would run the rsync command from my machine. Recently however, our network was 'upgraded' to a NAT

Hello all! Some month ago I upgraded our dovecot installation from version 1.0.5 to version 2.1.7 without having any trouble. Postfix is delivering email directly per virtual transport to the maildirs and mailboxes of the users in /var/spool/vhosts/domains/.... Now I want to use dovecot-lda and created a new entry in the master.cf of postfix. dovecot unix - n n - -

Hi.. after upating from 2.0.1 to 2.0.4 postfix often reports errors when deliveing mails to dovecot: "Undelivered Mail Returned to Sender" -> Command died with signal 11: "/usr/libexec/dovecot/dovecot-lda" anyone seens this before ?

Hi Aki, Am 21.02.19 um 12:55 schrieb Aki Tuomi: > > On 21.2.2019 13.47, Lionel Elie Mamane via dovecot wrote: >> I noticed a mail stuck in my mail queue. dovecot-lda was returning >> error 64 Invalid parameter given. (EX_USAGE). >> >> Weird, weird, weird. After some sleuthing, I found the sender address >> was FirstLast at domain.tld, with a UTF8-encoded

Hi Here is my environment: Red Hat Enterprise Linux Server release 5.7 (Tikanga) postfix-2.9.1-1.rhel5 dovecot 1.0.7 I want to config a complete postfix-dovecot mail server. First I configured postfix to use procmail, its default LDA and dovecot for pop3 and imap. I didn't changed main.cf a lot, just myhostname and a few other properties. I didn't set home_mailbox. About dovecot.conf

Hi I noticed in a post that Timo might start work on a LDA Great! If so, here is something I would really like included. Support for PAM There is quite a lengthy reason behind this. In my organisation, user accounts are created on ldap. It is up to the services to create home directories whenever the user first uses them. For instance, Samba will do this the first time they connect to their

I noticed a mail stuck in my mail queue. dovecot-lda was returning error 64 Invalid parameter given. (EX_USAGE). Weird, weird, weird. After some sleuthing, I found the sender address was FirstLast at domain.tld, with a UTF8-encoded Unicode U+FEFF ZERO WIDTH NO-BREAK SPACE character (AKA byte order mark) between "First" and "Last" :) Since that is passed as the -f parameter to

I am using postfix + dovecot 2.0.6 + mailman And others 2 serves with only postfix and dovecot writing at same storage with OCFS2. We are having problens with IOwait, and still trying to figure out why that is happen! But, problem becomes much worse when some emails are used in mailman, when it happens all 3 serves became really slow. iowait goes to 80. Does anyone have an idea how to slow

http://dovecot.org/test/ Should work again with maildir. - Some bugfixes to indexes (possibly fixing the still persisting maildir sync errrors?) - Enabled cache file again. If client asks about something that can be cached for future, it's done. There's currently no smart logic about when not to do it or when to cache more than was asked for future use. Currently nothing is ever

Hi, Our legacy data store retains a single copy of a message regardless of the number of mailboxes in which that message resides. It does this by creating hard links to that message in the mailboxes containing that message. Thus, when we perform data migration to the server target (Dovecot), the copies of the same message are copied over with the migration process (imapsync). We use the storage

http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz.sig Two hours later than promised, I slept longer than intended. :) No changes since v1.1.rc13. Below are the largest changes since v1.0: * After Dovecot v1.1 has modified index or dovecot-uidlist files, they can't be opened anymore with Dovecot versions earlier than v1.0.2. *

http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz.sig Two hours later than promised, I slept longer than intended. :) No changes since v1.1.rc13. Below are the largest changes since v1.0: * After Dovecot v1.1 has modified index or dovecot-uidlist files, they can't be opened anymore with Dovecot versions earlier than v1.0.2. *

http://dovecot.org/releases/dovecot-1.0.rc29.tar.gz http://dovecot.org/releases/dovecot-1.0.rc29.tar.gz.sig Probably one more RC after this. * Security fix: If zlib plugin was loaded, it was possible to open gzipped mbox files outside the user's mail directory. + Added auth_gssapi_hostname setting. - IMAP: LIST "" "" didn't return anything if there didn't

http://dovecot.org/releases/dovecot-1.0.rc29.tar.gz http://dovecot.org/releases/dovecot-1.0.rc29.tar.gz.sig Probably one more RC after this. * Security fix: If zlib plugin was loaded, it was possible to open gzipped mbox files outside the user's mail directory. + Added auth_gssapi_hostname setting. - IMAP: LIST "" "" didn't return anything if there didn't

http://dovecot.org/test/ Keywords are finally stored in maildir filenames and listed in "dovecot-keywords" file. It should be possible to just rename 0.99.x's .customflags file to dovecot-keywords (but it can't be renamed back after modification). Also fixed another uid/sequence mixup bug with setting keywords in general (in mbox too). Fixed SHA1 checksum generation with

After recently adding the -f parameter to the call to the deliver command which is called by Postfix, I found that e-mail with a null return path (MAIL FROM:<>) was causing Dovecot deliver to SEGFAULT. I verified this by making this patch to deliver.c (notice I fixed a typo here, too): *** deliver.c.orig Fri Oct 13 07:32:28 2006 --- deliver.c Fri Oct 27 21:26:08 2006 ***************

I think I won't do any actual releases until it's mostly feature complete. Then maybe v1.1.alpha1 or v1.1.beta1. So if you want to test it before then, use CVS or the nightly snapshots. I'm planning on keeping v1.1 almost completely compatible with v1.0. There could be some minor configuration file changes, but for most people v1.0's dovecot.conf should work with v1.1. I want to

http://dovecot.org/test/ I'm finally using this release myself with mboxes. So far no crashes or corruption. :) - several mbox fixes and optimizations - maildir syncing fix - solaris fixes - create mbox root dir if it doesn't exist -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc:

Hello! I am really need help! I am using dovecot installation on ~700 users with dspam integration via dovecot-antispam plugin. Problem in unpredictable result of moving spam-mails from INBOX to Junk and from Junk to INBOX. In some cases it works fine, but sometimes I see error like "It's not possible to move the message" in client (roundcube). Two different samples on same

Any plans to implement UIDPLUS in Dovecot? Keith