similar to: maildir: could lda/lmtp log filenames?

On 4/28/2015 1:40 PM, Tobias Franz?n <lists.zxinn at otaking.se> wrote: > On 2014-01-08 14:32, Charles Marcus wrote: >> On 2012-04-09 8:53 AM, Timo Sirainen <tss at iki.fi> wrote: >>> On 9.4.2012, at 15.50, Charles Marcus wrote: >>>>> LMTP adds a new Delivered-To:<rcpt-to at address> header when there is >>>>> a single RCPT TO. You

I'm resurrecting this again because I'm getting pretty close to possibly being ready to install a brand new dovecot server (finally), but I still need for dovecots LMTP to add the x-original-to header. So... was this completed quietly, or is support for it still not there? Thanks, Charles On Tue Apr 28 2015 15:27:07 GMT-0400 (Eastern Standard Time), Charles Marcus <CMarcus at

On 2014-01-08 14:32, Charles Marcus wrote: > On 2012-04-09 8:53 AM, Timo Sirainen <tss at iki.fi> wrote: >> On 9.4.2012, at 15.50, Charles Marcus wrote: >>>> LMTP adds a new Delivered-To:<rcpt-to at address> header when there is >>>> a single RCPT TO. You can force a single RCPT TO from Postfix side by >>>> setting

Hi, I am trying to set up my own mail server (to get off Google) and I have a problem with mail delivery. I'm using Postfix as a SMTP front-end, and use the LMTP server included in dovecot to receive mail from postfix. I have a setup which works with the dovecot LDA, it involves calling dovecot-lda with the -d flag. Postfix computes the username by removing what's after the

On 04.03.2018 16:25, Reio Remma wrote: > Hello! > > I'm having crashes with LMTP delivery when user is over quota on the > latest CentOS 7.4 with the latest Dovecot 2.3.0.1 from Dovecot repo. > > I see the issue has been fixed on January 17, but it doesn't seem to > have made it into 2.3.0.1 (I compared with the source from >

Dear All, I have a bit complex question about ldap based user/passdb with some twists caused by the LDAP schema I have to use. It's complex for me at least, since it's my first time to try to setup any dovecot install which is more than a "trivial" thing eg for some unix system users. What I'd like to do: Users are stored in LDAP with the following schema: storageMailUid:

Hi list, I am running a Debian Lenny machine with Postfix 2.5.5 and Dovecot 2.0.8. Up until now I ran Postfix with the Procmail delivery agent succesfully. The machine has only local users; I am not using virtual mailboxes. Due to obvious reasons I want to switch to Dovecot LDA delivery, through LMTP. I spend quite some time finding 'the' configuration for both Postfix and Dovecot,

Hello! I'm having crashes with LMTP delivery when user is over quota on the latest CentOS 7.4 with the latest Dovecot 2.3.0.1 from Dovecot repo. I see the issue has been fixed on January 17, but it doesn't seem to have made it into 2.3.0.1 (I compared with the source from https://dovecot.org/releases/2.3/dovecot-2.3.0.1.tar.gz).

On 03/11/2017 11:48, Stephan Bosch wrote: > Hi, > > Sorry, we're in a bit of a v2.3 merge frenzy. Much of the LMTP code will be > replaced in v2.3, but I'll give the? older code a look as well. > > This can take a while though. Thank you very much for getting back to me, I can appreciate it can get hectic, and I don't wish to appear ungrateful, I wholeheartedly

On 26/10/2017 19:33, David Zambonini wrote: > On 26/10/2017 18:38, Alexander Dalloz wrote: >> Am 26.10.2017 um 12:20 schrieb David Zambonini: >>> >>> There seems to be a bug with RFC822 processing in ltmp proxying that >>> doesn't >>> quote local parts that, for example, contain spaces. >> >> Newer related RFCs are RFC 5321 and 5322.

On 23/06/2020 16:01, Pascal Christen wrote: > Hi Stephan > > We tried it again last week with the latest dovecot version and still > having the same issue. The whole setup works perfectly fine with the > latest version of dovecot 2.2 > > The problem only exists if the quota of the user is full, every other > message gets delivered without a problem, and the lmtp process

Hello dovecot-users, (This problem was being discussed a little in this thread from 2011: http://www.dovecot.org/list/dovecot/2011-May/059009.html) I noticed (using LMTP) that Dovecot handles 'no space left on device' just like an 'over-quota', if I read this part of method "static int client_deliver(struct client *client, const struct mail_recipient *rcpt, struct mail

Hello, I'm using dovecot 2.2.9 and a director/backend setup. On the director I've the LMTP in proxy mode, mapping the users to one of the backends. The backends to quota check and return the OverQuota message already at RCPT TO time. Here is what I typed, connected to the director Connection to director1 2525 port [tcp/*] succeeded! 220 director1.rz.hs-example.de Dovecot

Am 26.10.2017 um 12:20 schrieb David Zambonini: > > There seems to be a bug with RFC822 processing in ltmp proxying that doesn't > quote local parts that, for example, contain spaces. Newer related RFCs are RFC 5321 and 5322. [ ... ] > MAIL FROM:<test at testdomain.com>\r\n > RCPT TO:<deemzed.uk+Junk E-mail>\r\n > > 501 5.5.4 Invalid.parameters\r\n That

Hello all, Is there a way to use LMTP (or LDA) so that maildir index and dovecot-uidlist are not updated? My setup is such that mail delivery sees user's maildir as write only. This setup works well when using postfix for mail delivery, but when I try to switch to dovecot LMTP the lmtp process wants to read the dovecot-uidlist and fails on insufficient privileges. Is there a way around this

On Thursday 22 of March 2018, Arkadiusz Mi?kiewicz wrote: > I have a problem with some messages passed from exim to dovecot lmtp > service: > > From exim debug: > > using socket /var/run/dovecot/lmtp > LMTP<< 220 mbox8 ready > LMTP>> LHLO mbox8... > LMTP<< 250-mbox8 > LMTP<< 250-STARTTLS > LMTP<< 250-8BITMIME >

On 2012-04-05 4:18 AM, Thomas Leuxner <tlx at leuxner.net> wrote: > Also with 2.x you may want to use LMTP rather than the LDA Piping. > > http://wiki2.dovecot.org/HowTo/PostfixDovecotLMTP I am preparing to convert my main client's postfix_courier-imap setup to dovecot 2.1, which currently just uses the postfix virtual delivery agent... Does anyone know if the use of LMTP

Hi, Sorry, we're in a bit of a v2.3 merge frenzy. Much of the LMTP code will be replaced in v2.3, but I'll give the? older code a look as well. This can take a while though. Regards, Stephan. Op 1-11-2017 om 18:34 schreef David Zambonini: > Hi again, > > I've not heard anything further regarding this bug, so I've had a look at the code. > > To restate the bug

There seems to be a bug with RFC822 processing in ltmp proxying that doesn't quote local parts that, for example, contain spaces. director config: director_username_hash = %Ln lmtp_proxy = yes recipient_delimiter = + protocol lmtp { auth_socket_path = director-userdb auth_username_chars = auth_username_format = %Ln passdb {

I tried setting the "destuser" setting on the LMTP director as follows, to preserve the original envelope rcpt: protocol lmtp { auth_socket_path = director-userdb passdb { driver = ... override_fields = destuser=%{orig_user} } } The passdb driver would return the appropriate "user" for each alias. Suppose, for example, user1 has emails user1 at domain.tld,