similar to: test

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

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

Hello, My setup consists of the following: * Freebsd 6.2 system with software installed from ports tree: * Postfix 2.3.8,1 * postfixadmin 2.1.0_7 * mysql 5.0.33 * dovecot-1.0.r25 * dovecot-sieve 1.0.1 * clamav 0.90_3 * SpamAssassin 3.1.8_1 * amavisd-new 2.4.5_1,1 My mail setup is a virtual user setup with all users/domains sharing same UID:GID. Postfix and dovecot get their

On 23/06/15 13:10, Steffen Kaiser wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Tue, 23 Jun 2015, lejeczek wrote: >> On 23/06/15 09:32, Steffen Kaiser wrote: >>> On Mon, 22 Jun 2015, lejeczek wrote: >>>> On 22/06/15 09:43, Steffen Kaiser wrote: >>>>> On Mon, 22 Jun 2015, lejeczek wrote: >>>>>> On 22/06/15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 23 Jun 2015, lejeczek wrote: > On 23/06/15 09:32, Steffen Kaiser wrote: >> On Mon, 22 Jun 2015, lejeczek wrote: >>> On 22/06/15 09:43, Steffen Kaiser wrote: >>>> On Mon, 22 Jun 2015, lejeczek wrote: >>>>> On 22/06/15 09:16, lejeczek wrote: >>>>>> >>>>>> to=<me

Greetings all, After running for more than a year without issue on debian lenny while it was in the testing- we're now experiencing problems under Lenny/Stable. Dovecot now converts some sort of lockfile into messages, and they're owned by root. The result is a mess; clients can't read their mailboxes with the root-owned files, and when the file is changed to be owned by them, many

Cit?t Timo Sirainen <tss at iki.fi>: > On 29 Nov 2018, at 15.46, azurit at pobox.sk wrote: >> >> Hi, >> >> is this a know problem? Newest Dovecot 2.3.4 package from >> repo.dovecot.org , Debian Stretch (fully upgraded). >> >> >> >> Nov 29 14:25:11 server00 dovecot: lmtp(16854): Panic: file >> ostream-dot.c: line 208

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 22 Jun 2015, lejeczek wrote: > On 22/06/15 09:43, Steffen Kaiser wrote: >> On Mon, 22 Jun 2015, lejeczek wrote: >>> On 22/06/15 09:16, lejeczek wrote: >>>> >>>> to=<me at my.domain>,orig_to=<root at localhost>, relay=dovecot, delay=39296, >>>> delays=39294/2.2/0/0.27,

A patch has been proposed for SpamAssassin to process Maildir folders of spam: <https://issues.apache.org/SpamAssassin/show_bug.cgi?id=3003> Is this patch compatible with Dovecot's implementation of Maildir? For example, is anything needed to avoid stepping on Dovecot's metadata?

After v1.0 is released, I can finally get back to sane version numbers. But any comments on which one is better: a) Postfix-style: "1.1.UNSTABLE.YYYYMMDD" -> 1.1.0 (stable) b) Odd-even numbering: 1.1.x (unstable) -> 1.2.0 (stable) With a) style the releases could be done by simply copying a nightly snapshot to releases/ directory and announcing the changes since the last

Cit?t azurit at pobox.sk: > Cit?t azurit at pobox.sk: > >> Cit?t Timo Sirainen <tss at iki.fi>: >> >>> On 29 Nov 2018, at 15.46, azurit at pobox.sk wrote: >>>> >>>> Hi, >>>> >>>> is this a know problem? Newest Dovecot 2.3.4 package from >>>> repo.dovecot.org , Debian Stretch (fully upgraded).

On 17 Oct 2015, at 12:41, Timo Sirainen <tss at iki.fi> wrote: > >> Connect postfix at localhost on postfix >> 134 Query SELECT bytes FROM quota2 WHERE username = >> 'user at mydomain.lan' >> 135 Query SELECT bytes FROM quota2 WHERE username = >> 'user at mydomain.lan' >> 135 Query BEGIN

http://dovecot.org/releases/2.1/dovecot-2.1.16.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.16.tar.gz.sig + Added quota-status policy service for Postfix + Added "doveadm batch" command to run multiple commands before moving onto the next user (useful only with -A and -u <usermask>) + Added forwards compatibility for v2.2 index files - mdbox: Index rebuilding crashed

http://dovecot.org/releases/2.1/dovecot-2.1.16.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.16.tar.gz.sig + Added quota-status policy service for Postfix + Added "doveadm batch" command to run multiple commands before moving onto the next user (useful only with -A and -u <usermask>) + Added forwards compatibility for v2.2 index files - mdbox: Index rebuilding crashed

--On Thursday, January 29, 2004 11:16 PM +0200 Timo Sirainen <tss at iki.fi> wrote: > I don't yet really even want Dovecot to be too well known, it's not > ready yet. When 1.0 comes (this spring I hope) I'll start publicizing it > more. After that I should only need to add new features - existing ones > should be perfect and better than anyone else's ;) Just a

It doesn't in my current 2.2.18 setup with the config I posted. On Mon, Sep 7, 2015 at 5:22 PM, Timo Sirainen <tss at iki.fi> wrote: > It should. > > On 08 Sep 2015, at 01:01, Larry Rosenman <larryrtx at gmail.com> wrote: > > should fts_autoindex handle that case? > > > On Mon, Sep 7, 2015 at 5:00 PM, Timo Sirainen <tss at iki.fi> wrote: >

It works for me. I don't know why it wouldn't work for you. Looking at the autoindexing code I don't see how it could be possible that it works for saving but not copying. > On 10 Sep 2015, at 21:05, Larry Rosenman <larryrtx at gmail.com> wrote: > > Is there a fix coming for this, Timo? Or is it a longer term issue? > > On Mon, Sep 7, 2015 at 5:23 PM, Larry

I have always seen some people indicate they use MySQL for mailboxes in Postfix and I wondered how difficult something like this would be? I have 300 users on my company Postfix server right now. I am just using Postfix, Dovecot (IMAP4 only), & Roundcube (Webmail). I have MySQL loaded on the machine that runs Postfix but only to manage the database for Roundcube. Do you think that 300+ users

should fts_autoindex handle that case? On Mon, Sep 7, 2015 at 5:00 PM, Timo Sirainen <tss at iki.fi> wrote: > On 09/08/2015 12:56 AM, Larry Rosenman wrote: > > that the fts data gets lost? > > All full text search backends are now implemented so that if you > copy/move mails, the mails need to be indexed again the destination folder. > > Alternative would be to