similar to: Test mail

Hi, The bug reported in http://dovecot.org/list/dovecot/2006-July/014786.html still exists in 1.0.rc6 % grep "$ ./configure" dovecot-1.0.rc6/config.log $ ./configure --prefix=/srv/software/dovecot Install prefix ...................... : /srv/software/dovecot File offsets ........................ : 64bit I/O loop method ..................... : poll File change notification method

Hi, I'm using Dovecot's (1.0.rc2) 'deliver' (no sieve) as LDA - calling it from a .qmail file. It seems that 'deliver' destroys "message/rfc822" attachments (forward as attachment). My .qmail file looks like this, and use qmail to deliver a copy directly to my Maildir, and 'deliver' to deliver a second copy of the same message to the same Maildir: %

This part of the body will be zapped by Dovecot's deliver... This is bad.... Injecting the message: % cat /tmp/mail.txt | /var/qmail/bin/qmail-inject Having qmail process the message: % sudo /var/qmail/rc status: local 0/10 remote 0/20 new msg 1596241 info msg 1596241: bytes 364 from <csa at csa-net.dk> qp 23105 uid 1000 starting delivery 1: msg 1596241 to local csa at csa-net.dk

This part of the body will be zapped by Dovecot's deliver... This is bad.... /Claus A Second one (delivered by Dovecot's 'deliver') doesn't look good: % cat 1154938875.P23113Q0M326713.silver

Hello, I'm trying dovecot-lda (deliver.c has CVS version 1.18). When I try to deliver a mail, an empty directory is created name $HOME/mail. This is neither the configured (via LDAP) nor the default "mail" setting in the /usr/local/etc/dovecot-deliver.conf. When the $HOME directory does not exist, but the user itself: Sep 1 11:47:12 localhost deliver: mbox: Can't create

Hi! I am using Dovecot 1.0.10 with LDA/postfix option reading user data from ldap, but the problem would be nonexistent maildir. Connection with ldap should be fine since reading proper maildir folder. Is it possible to auto creating maildir folders even on received mail since the you can auto create when user login with mail_executable scripts as it's seen from configuration I am doing

Anyone had any thoughts on the item below? If the problem is with my config, I'd like to be guided towards how I might resolve it. If it is a bug in rc7, it would be good to fix it, and I'd be happy to beta-test. -- : David Lee I.T. Service : : Senior Systems Programmer Computer Centre : :

I would not have expected this upon implementing sieve. And I really need to get around this limitation. LDA has no problem writing to these large mbox files. Why does sieve have a problem with them? This is very odd. May 10 17:45:04 greer dovecot: deliver(stan): write() failed with mbox file /home/stan/mail/1-Debian-Users: File too large May 10 17:45:04 greer dovecot: deliver(stan): write()

dovecot-request at dovecot.org demis ki:: > Send dovecot mailing list submissions to > dovecot at dovecot.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://dovecot.org/cgi-bin/mailman/listinfo/dovecot > or, via email, send a message with subject or body 'help' to > dovecot-request at dovecot.org > > You can reach the person managing

http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta8.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta8.tar.gz.sig Changes since beta7: - Added a new "raw" mail storage backend which allows opening files/streams as single mail mailboxes. deliver uses this now instead of opening the incoming mail as a mbox. So deliver should be now faster and it doesn't anymore remove

> On 23 Dec 2019, at 11.57, Philip Colmer <philip.colmer at linaro.org> wrote: > > I'm trying to diagnose a really strange situation where certain emails, when submitted to the mailbox by Postfix, are not considered to be unseen by Dovecot. > > During testing, I've shut down anything else on the server that might want to access the mailbox. I submit the email to the

Hello: I have virtual users set up for the various mailing lists that I subscribe to. Everything has been working well in both Postfix and Dovecot. Postfix is configured to deliver to a specific mbox file within my mbox mail root. I can access retrieve and read email via Dovecot without any issues. Now I want to make my setup more robust and have these messages delivered to a maildir

I thought I had Dovecot configured to use Maildir instead of mbox, but apparently it is still using mbox. Excerpt from dovecot.conf: mail_location = maildir:~/Maildir Excerpt from sendmail.mc: MAILER(dovecot)dnl dovecot.m4: ######################################## ### DOVECOT Mailer Specification ### ######################################## Mdovecot,

Hello! Currently I'm trying to integrate dovecot's deliver program into procmail. So basically I'd write a patch for procmail to deliver not directly into the mbox file but delivering with the dovecot deliver program. Do you think this is a good concept? For testing I use the commands discussed below. Currently I'm having a problem that deliver doesn't recognize the

Hi, I'm trying to get Dovecot's deliver to create and use mailboxen with one uid per user. Reading the wiki, I decided to go with the sudo attempt, but I'm stuck because deliver fails to create the intermediate directories. The auth.log has this on the matter: sudo: dovelda : TTY=unknown ; PWD=/var/spool/postfix ; USER=root ; COMMAND=/usr/lib/dovecot/deliver -f toni at

http://dovecot.org/releases/dovecot-1.0.rc28.tar.gz http://dovecot.org/releases/dovecot-1.0.rc28.tar.gz.sig Still a bit more fixes. My coding TODO list is again empty. Unless something special happens in the next few weeks, I'll still make rc29 with the documentation included and v1.0 will be released April 13. * deliver + userdb static: Verify the user's existence from passdb,

http://dovecot.org/releases/dovecot-1.0.rc28.tar.gz http://dovecot.org/releases/dovecot-1.0.rc28.tar.gz.sig Still a bit more fixes. My coding TODO list is again empty. Unless something special happens in the next few weeks, I'll still make rc29 with the documentation included and v1.0 will be released April 13. * deliver + userdb static: Verify the user's existence from passdb,

We are running Postfix 2.3.3 and Dovecot 1.0-RC27 on a Solaris 10 server. We use the Dovecot LDA for local delivery. Problems arise with looping mail whenever a user's .forward contains a reference to themselves. This most frequently occurs when a user sets up a vacation since it then puts this in their .forward file: \username, "|/usr/bin/vacation username" The vacation program

Hello! As discussed in the previous thread about "Dovecot deliver logging problem and procmail" I have made a small patch for procmail to deliver through dovecot's deliver program (or any other delivery program). So Procmail does not write the mailboxes directly any more. So delivery is done through pipes and an external program which can deliver the files. Since dovecot's

On 14.07.2016 10:56, Arkadiusz Mi?kiewicz wrote: > 2.2.25 (also happens on 2.2.24). Happens every time I try to make deliver > and only for this user: > > Jul 14 09:52:02 mbox dovecot: lmtp(25601): Connect from local > Jul 14 09:52:02 mbox dovecot: lmtp(powiadomienia): session=<CRU2EaJEh1cBZAAALZVUYQ>, Error: Index /var/mail/powiadomienia/dovecot.index: Lost log for seq=1009