-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Is is possible to specify multiple maildir location in mail_location? (default_mail_env in my case since I'm using version 1.0.rc15/debian etch).
What I want to achieve is receive mail in /var/spool/mail, which is going to contain 1 Maildir per user, and have /home/%u/Maildir/ to store (move) messages from spool location. Postfix is taking care of the 1st (delivery in maildir format in spool location), and dovecot should (I want to) be able to read messages from both locations.
Ideally, is something like:
default_mail_env = maildir:/var/spool/mail:/home/%u/Maildir
possible?
thx -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFI9MEcgUWLzP4xLCERAoLKAJ4ySsAfIKDqIenmww1sTApcjikM3wCeIBA1 vO0glRfNXUtajKMaPYHM8L4= =eL+3 -----END PGP SIGNATURE-----
On Oct 14, 2008, at 6:56 PM, Vassilis Vatikiotis wrote:
What I want to achieve is receive mail in /var/spool/mail, which is going to contain 1 Maildir per user, and have /home/%u/Maildir/ to
store (move) messages from spool location.
So Dovecot should automatically move messages from one maildir to
another when it sees messages there? You could probably do that with
mbox-snarf plugin (it should work with maildir too). See if you can
get it compiled with 1.0.rc15: http://dovecot.org/patches/1.0/mbox-snarf-plugin.c
If you can't, just upgrade. Or I'd suggest upgrading in any case.
There are v1.1 packages available in backports.org and mbox-snarf
plugin comes with it.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Timo Sirainen wrote:
On Oct 14, 2008, at 6:56 PM, Vassilis Vatikiotis wrote:
What I want to achieve is receive mail in /var/spool/mail, which is going to contain 1 Maildir per user, and have /home/%u/Maildir/ to store (move) messages from spool location.
So Dovecot should automatically move messages from one maildir to another when it sees messages there? You could probably do that with mbox-snarf plugin (it should work with maildir too). See if you can get it compiled with 1.0.rc15: http://dovecot.org/patches/1.0/mbox-snarf-plugin.c Actually no, I just want dovecot to be able to access both maildirs of a user, at the same time. So, in my MUA, I'd be able to see 2 locations (folders), 1 at my home directory and 1 under /var/spool.
The reason I need to use /var/spool is that this folder is monitored very closely so it make sense to have postfix storing incoming messages there. End users can move msgs, from the spool locatioon, to their personal maildirs as they see fit.
If you can't, just upgrade. Or I'd suggest upgrading in any case. There are v1.1 packages available in backports.org and mbox-snarf plugin comes with it.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFI9zEvgUWLzP4xLCERAruaAJ91VTTEojJl4YrIIa7mnJxYOhZOswCeMqnZ DeE7fIW4BfTzr/EfFby5CJQ= =hg/s -----END PGP SIGNATURE-----
On Thu, 2008-10-16 at 15:18 +0300, Vassilis Vatikiotis wrote:
What I want to achieve is receive mail in /var/spool/mail, which is going to contain 1 Maildir per user, and have /home/%u/Maildir/ to store (move) messages from spool location.
So Dovecot should automatically move messages from one maildir to another when it sees messages there? You could probably do that with mbox-snarf plugin (it should work with maildir too). See if you can get it compiled with 1.0.rc15: http://dovecot.org/patches/1.0/mbox-snarf-plugin.c Actually no, I just want dovecot to be able to access both maildirs of a user, at the same time. So, in my MUA, I'd be able to see 2 locations (folders), 1 at my home directory and 1 under /var/spool.
The reason I need to use /var/spool is that this folder is monitored very closely so it make sense to have postfix storing incoming messages there. End users can move msgs, from the spool locatioon, to their personal maildirs as they see fit.
Can they be different mailboxes then? So /var/spool/mail/%u is INBOX and the other mailboxes are in ~/Maildir? That'd be easy:
mail_location = maildir:~/Maildir:INBOX=/var/spool/mail/%u
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Timo Sirainen wrote:
On Thu, 2008-10-16 at 15:18 +0300, Vassilis Vatikiotis wrote:
What I want to achieve is receive mail in /var/spool/mail, which is going to contain 1 Maildir per user, and have /home/%u/Maildir/ to store (move) messages from spool location. So Dovecot should automatically move messages from one maildir to another when it sees messages there? You could probably do that with mbox-snarf plugin (it should work with maildir too). See if you can get it compiled with 1.0.rc15: http://dovecot.org/patches/1.0/mbox-snarf-plugin.c Actually no, I just want dovecot to be able to access both maildirs of a user, at the same time. So, in my MUA, I'd be able to see 2 locations (folders), 1 at my home directory and 1 under /var/spool.
The reason I need to use /var/spool is that this folder is monitored very closely so it make sense to have postfix storing incoming messages there. End users can move msgs, from the spool locatioon, to their personal maildirs as they see fit.
Can they be different mailboxes then? So /var/spool/mail/%u is INBOX and the other mailboxes are in ~/Maildir? That'd be easy:
mail_location = maildir:~/Maildir:INBOX=/var/spool/mail/%u
Unfortunately no, and this is a Postfix limitation. Postfix has a hardcoded upper limit for mbox sizes, which is 2GB on 32bit machines, and some of my users don't bother to offload their mbox. I could tweak the Postfix source code but I shudder at the thought of recompiling every time there is a security update...
my current dovecot conf is: default_mail_env = mbox:~/mail/:INBOX=/var/spool/mail/%u
and I need to preserve the "essence" of this setup i.e. mbox:~/mail/ resides in nfs, in users' home dirs and :INBOX is where postfix stores incoming emails, in a local disk.
I could have postfix delivering directly in ~/mail/, in maildir format, but NFS has proved a bit unreliable so far so I'd rather have incoming mails stored in a local, reliable storage area i.e. var/spool/mail. But in a maildir format, cause of postfix mbox size limits :D
After "guarranted" mail deliver in /var/spool by postfix, users can opt to move mails in ~/mail. All in maildir....
Can it be done? Maybe dovecot doesn't support it i.e. multiple maildir locations per user.
thx for your time -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFI90uxgUWLzP4xLCERAlRAAJ9qSCB8PVzcnxRjeDLcrHvRtAhC4wCghosa lTzb06aecdO4otY1b4YqinE= =61TP -----END PGP SIGNATURE-----
On Oct 16, 2008, at 5:12 PM, Vassilis Vatikiotis wrote:
Can they be different mailboxes then? So /var/spool/mail/%u is
INBOX and the other mailboxes are in ~/Maildir? That'd be easy:mail_location = maildir:~/Maildir:INBOX=/var/spool/mail/%u
Unfortunately no, and this is a Postfix limitation. Postfix has a hardcoded upper limit for mbox sizes, which is 2GB on 32bit machines,
The above configuration would be all-maildir.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Timo Sirainen wrote:
On Oct 16, 2008, at 5:12 PM, Vassilis Vatikiotis wrote:
Can they be different mailboxes then? So /var/spool/mail/%u is INBOX and the other mailboxes are in ~/Maildir? That'd be easy:
mail_location = maildir:~/Maildir:INBOX=/var/spool/mail/%u
Unfortunately no, and this is a Postfix limitation. Postfix has a hardcoded upper limit for mbox sizes, which is 2GB on 32bit machines,
The above configuration would be all-maildir. ??? I thought :INBOX denotes mbox style.....I'm gonna definitely give it a try. thx for the help...
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFI903DgUWLzP4xLCERAtXSAJwM78PHG7jI2tco31llTDQTxyS8/QCdFV/z IX2nMwF3LtZkafRBtc4jmzA= =QxKe -----END PGP SIGNATURE-----
On 10/16/2008 10:12 AM, Vassilis Vatikiotis wrote:
Unfortunately no, and this is a Postfix limitation. Postfix has a hardcoded upper limit for mbox sizes, which is 2GB on 32bit machines,
I really don't think that is correct - it is more a filesystem limitation. I don't think Postfix cares how big the mbox files are.
--
Best regards,
Charles
On Thu, 2008-10-16 at 10:29 -0400, Charles Marcus wrote:
On 10/16/2008 10:12 AM, Vassilis Vatikiotis wrote:
Unfortunately no, and this is a Postfix limitation. Postfix has a hardcoded upper limit for mbox sizes, which is 2GB on 32bit machines,
I really don't think that is correct - it is more a filesystem limitation. I don't think Postfix cares how big the mbox files are.
Probably compiled with 32bit off_t, which prevents opening files >2GB. Compiling with 64bit off_t should be pretty easy with Linux, but I don't know if Postfix can be configured to do that without modifying Makefile manually (-D_FILE_OFFSET_BITS=64).
On 10/16/2008 11:01 AM, Timo Sirainen wrote:
On Thu, 2008-10-16 at 10:29 -0400, Charles Marcus wrote:
Unfortunately no, and this is a Postfix limitation. Postfix has a hardcoded upper limit for mbox sizes, which is 2GB on 32bit machines, I really don't think that is correct - it is more a filesystem
On 10/16/2008 10:12 AM, Vassilis Vatikiotis wrote: limitation. I don't think Postfix cares how big the mbox files are.
Probably compiled with 32bit off_t, which prevents opening files >2GB. Compiling with 64bit off_t should be pretty easy with Linux, but I don't know if Postfix can be configured to do that without modifying Makefile manually (-D_FILE_OFFSET_BITS=64).
Ah, thanks for the correction/explanation...
I guess then that this is essentially a 32-bit filesystem limitation? Or are you saying that you could still compile postfix like this even on a 32 bit system?
I'm also guessing that postfix running on a 64 bit system would normally be compiled this way...?
--
Best regards,
Charles
On Oct 16, 2008, at 6:12 PM, Charles Marcus wrote:
Probably compiled with 32bit off_t, which prevents opening files
2GB. Compiling with 64bit off_t should be pretty easy with Linux, but I
don't know if Postfix can be configured to do that without modifying
Makefile manually (-D_FILE_OFFSET_BITS=64).Ah, thanks for the correction/explanation...
I guess then that this is essentially a 32-bit filesystem limitation?
No.
Or are you saying that you could still compile postfix like this even
on a 32 bit system?
Yes. The problem is that you need to be able to seek in files, so you
have this off_t type for storing the file offset. Normally it's signed
32bit in 32bit systems, so the file sizes are limited to 2 GB. But
Linux and Solaris at least support easily recompiling with 64bit off_t.
I'm also guessing that postfix running on a 64 bit system would
normally be compiled this way...?
With 64bit systems off_t is always 64bit.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Charles Marcus wrote:
On 10/16/2008 10:12 AM, Vassilis Vatikiotis wrote:
Unfortunately no, and this is a Postfix limitation. Postfix has a hardcoded upper limit for mbox sizes, which is 2GB on 32bit machines,
I really don't think that is correct - it is more a filesystem limitation. I don't think Postfix cares how big the mbox files are.
ext3 with 4k blocksize, as in my case, has no problem with this.
a relevant W. Wenema's post for postfix large file model support: http://www.mailinglistarchive.com/postfix-users@postfix.org/msg49050.html -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFI+Go5gUWLzP4xLCERAnOgAJ4yKzLfZ0kcxIigyN0Uf5iV3CP6nQCfV6KX 3C6uSOhYQ5gy4D7Z4DO7CbI= =38Oj -----END PGP SIGNATURE-----
participants (3)
-
Charles Marcus
-
Timo Sirainen
-
Vassilis Vatikiotis