similar to: deliver copies "^From " header lines when delivering to Maildir

Hi list, I understand that dovecot's deliver does a little more than deliver: it also updates the dovecot metadata stored with each Maildir. Thus, if I use deliver as opposed to procmail's internal Maildir delivery, it seems that the IMAP server later has less work to do since the metadata is can use are up to date. Doing this, however, incurs an extra process for each mail delivered. I

On 08/19/2015 10:45 PM, Paulo Matos wrote: > > Hi all, > > I have a running dovecot with: > $ dovecot -n > # 2.2.18: /etc/dovecot/dovecot.conf > [...] > I started to filter my email with imapfilter running on the same host as > dovecot. I would therefore like to deliver email to a folder called > PreINBOX so that imapfilter then sorts the email and ends up

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 19 Aug 2015, Paulo Matos wrote: >> You can't change the name of the INBOX - the INBOX is always the INBOX. >> But you can choose the name of the target mailbox. > > How do I do that? Depends on your way to deliver messages. With Dovecot LDA you could use the -m option. > >> I don't know

Looks like this is a dovecot problem after all. :) I can get Postfix to deliver to lmtp, but it's telling it to deliver to a fully qualified 'user at domain.tld' address. Postfix says that it can't find that user, and that turns out to be the case. dovecot: auth: Debug: master in: USER#0112#011user at domain.tld#011service=lmtp So I read up on that error, and it looked like I

On Thu, Aug 20, 2015 at 8:41 am, Steffen Kaiser < skdovecot at smail.inf.fh-brs.de [skdovecot at smail.inf.fh-brs.de] > wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 19 Aug 2015, Paulo Matos wrote: >> You can't change the name of the INBOX - the INBOX is always the INBOX. >> But you can choose the name of the target mailbox. > > How do I do that?

Hello Doug, First off since this is a postfix configuration problem I beleive it would be better suited in the postfix mailing list. The way I understand it is that you are editing the virtual transport map when you should be changing the local transport map because you are delivering to a normal, system user, not a virtual user. Try and see if that works for you. ? -- Yassine. On

On 19/08/15 22:11, Pascal Volk wrote: > On 08/19/2015 10:45 PM, Paulo Matos wrote: >> >> Hi all, >> >> I have a running dovecot with: >> $ dovecot -n >> # 2.2.18: /etc/dovecot/dovecot.conf >> [...] >> I started to filter my email with imapfilter running on the same host as >> dovecot. I would therefore like to deliver email to a folder

Hi all, I have a running dovecot with: $ dovecot -n # 2.2.18: /etc/dovecot/dovecot.conf # OS: Linux 4.1.0-x86_64-linode59 x86_64 Fedora release 22 (Twenty Two) ext4 auth_debug = yes auth_mechanisms = plain login digest-md5 cram-md5 auth_verbose = yes auth_verbose_passwords = yes default_internal_user = root imap_client_workarounds = delay-newmail tb-extra-mailbox-sep mail_debug = yes

Hi all, I have a running dovecot with: $ dovecot -n # 2.2.18: /etc/dovecot/dovecot.conf # OS: Linux 4.1.0-x86_64-linode59 x86_64 Fedora release 22 (Twenty Two) ext4 auth_debug = yes auth_mechanisms = plain login digest-md5 cram-md5 auth_verbose = yes auth_verbose_passwords = yes default_internal_user = root imap_client_workarounds = delay-newmail tb-extra-mailbox-sep mail_debug = yes

I considered sending to the postfix list instead, and would be happy to do that if it's more appropriate. In regards to your suggestion, I've tried local_transport and mailbox_transport, but both result in mail bouncing because "User doesn't exist." I've added my virtual_maps file to local_recipient_maps, and that still doesn't work. I did get the expected

I asked this question in a more detailed post, with no response, so I'm going to ask point blank. Is there a way make dovecot's deliver use default mailbox and directory settings? I'm thinking of the mail_location parameter, which deliver seems to ignore. Thanks! -- Mark Edwards

/ I'm testing a new setup of postfix using deliver to put the messages into the user's maildir, and am curious if there is a way to make deliver create custom maildirs when it delivers to a valid user without a maildir? Right now it only creates the inbox, I'd like it to create the .sent/ .Trash/ and .SPAM dirs. Is this possible? Thanks -------------------------------------- /

Hi, I want to use the zlib plugin to compress my mail storage. According to the wiki, only messages with size attribute in the message id should by compressed. If I added the size part, dovecot assumes it is a new message. While dovecot undertands the ',S=<size>' attribute (IMAP shows that size), I could not configure deliver to add the size to message name. I'm using

Hi all, I have the following situation: On a qmail toaster I am running (with dovecot 1.2.12 as the IMAP server), spam mail gets automatically put into a 'this might be spam' folder (per user). Now, every user has the opportunity to move that mail into either a 'learn as spam' or a 'this was ham' folder and the mail items will be treated accordingly. As a cronjob, I run

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi @ll, sorry i am new to dovecot so this may asked before i this in dovecot.conf protocols = pop3 imap ssl_disable = yes mail_extra_groups = mail valid_chroot_dirs = /usr/local/virtual/ default_mail_env = maildir:/usr/local/virtual/%d/%n disable_plaintext_auth = no protocol lda { postmaster_address = postmaster at test.de } protocol pop3 {

Hi, I'm using deliver for storing new mails (nfs). Since v.1.2 deliver does not reject mails if over quota (maildir quota). test with v. 1.1.18: # HOME=/tmp/maildir/ /path/dovecot-1.1.18/libexec/dovecot/deliver -e -c /path/dovecot-1.1.18/etc/dovecot.conf # Quota exceeded (mailbox for user is full) test with v. 1.2.4: # HOME=/tmp/maildir/ /path/dovecot-1.2.4/libexec/dovecot/deliver -e -c

Hello list, I have a need for someone to point me in the right direction. Our old email system (system A) had an account that acted as a mailing list accumulator/archiver. This account was a member of every list and mail would be sent to it's address. The strange part is that email was not delivered to system A because there was a . (dot) forward alias to another machine (system B) that

First I'd like to thank all the developers and contributors to dovecot. I've been using it for many years, and deeply appreciate your fine work. :) dovecot --version 2.2.22 (fe789d2) I have a working installation with postfix and dovecot, and I want to add sieve to it, so I am trying to configure postfix to use lmtp instead of 'virtual' for its delivery service. However it is

Deliver from latest 1.1 HG with sieve also from latest 1.1 HG is dying with an assertion failure when it delivers to my mailbox. Other mailboxes on the same system are unaffected, but I can read my mailbox fine through IMAP. Dovecot and sieve were compiled with -march=nocona -pipe -ggdb I've commented out my entire sieve script and the problem still occurs. file index-mail-headers.c: line

I'd like to flag a problem we are observing that looks like it is caused by the listescape-plugin.c. I realize that this plugin is not part of the standard Dovecot 1.0 distribution but I would appreciate any insights or suggestions for fixes that anyone is kind enough to offer. The problem concerns subfolder renames when used in conjunction with Maildir folders (I've not tested this