Hi,
Is it possible to change convert plugin, so it would keep old UIDVALIDITY and UIDNEXT after conversion from mbox to Maildir? As far as I can tell, this shouldn't be a big problem as this information already exists in the mbox. Well, at least for mboxes, that have that information.
The problem is easy, if UIDVALIDITY changes during conversion, then client has to reload whole mailbox from the server. And this is not easy for users with 5+ Gb of mail.
Thanks,
FiL
On Mon, 2008-02-04 at 15:00 -0500, Dmitry Filonov wrote:
Is it possible to change convert plugin, so it would keep old UIDVALIDITY and UIDNEXT after conversion from mbox to Maildir?
It would also have to preserve all messages' UIDs. This is something that has been in my TODO for a while, but it would require pretty large changes so it hasn't been done yet.
Maildir -> dbox migration can preserve UIDs though. :)
Timo Sirainen wrote:
On Mon, 2008-02-04 at 15:00 -0500, Dmitry Filonov wrote:
Is it possible to change convert plugin, so it would keep old UIDVALIDITY and UIDNEXT after conversion from mbox to Maildir?
It would also have to preserve all messages' UIDs. This is something that has been in my TODO for a while, but it would require pretty large changes so it hasn't been done yet.
Maildir -> dbox migration can preserve UIDs though. :)
Why this require large changes? Isn't it only about creating dovecot-uidlist on migration? Anyway, it's your time and I can't ask you to work on my problem first.
What about mbox->dbox migration? Does it preserve UIDs?
Thanks,
FiL
On Tue, 2008-02-05 at 10:50 -0500, Dmitry Filonov wrote:
Timo Sirainen wrote:
On Mon, 2008-02-04 at 15:00 -0500, Dmitry Filonov wrote:
Is it possible to change convert plugin, so it would keep old UIDVALIDITY and UIDNEXT after conversion from mbox to Maildir?
It would also have to preserve all messages' UIDs. This is something that has been in my TODO for a while, but it would require pretty large changes so it hasn't been done yet.
Maildir -> dbox migration can preserve UIDs though. :)
Why this require large changes? Isn't it only about creating dovecot-uidlist on migration?
That would be one way to do it. But then the conversion must not create dovecot.index* files or they'll contain different UIDs. And I'd rather implement it in a generic way that allows migration from any mailbox format to another, even maildir -> mbox.
What about mbox->dbox migration? Does it preserve UIDs?
No. dbox was designed so that an existing maildir could be quickly migrated to dbox. In that case dbox will use the existing maildir files as they are, only new mails (or modified mails) are really migrated to the proper dbox format.
I have a little problem on my hands. I followed the following how to and made plenty of changes.
http://www.howtoforge.com/postfix_mysql_dovecot_dspam_clamav_postgrey_rbl_de bian_etch
However my basic setup is this:
Mail comes in via Postfix incoming mail server only. Sends it to a DSPAM machine who checks the mail for spam and the uses Dovecot to deliver the email.
My problem is this:
I have users setup with forwards in my MySQL database. So dovecot tries to deliver mail (such as to my blackberry) and it fails. What is the proper way for me to forward this mail outside of the local mailbox?
Should I use .forward files in the mailboxes themselves instead?
Thanks,
Fred
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
use sieve Action redirect
http://www.ietf.org/rfc/rfc3028.txt Paragraph : 4.3
Fred Newtz wrote: | I have a little problem on my hands. I followed the following how to and | made plenty of changes. | | http://www.howtoforge.com/postfix_mysql_dovecot_dspam_clamav_postgrey_rbl_de | bian_etch | | However my basic setup is this: | | Mail comes in via Postfix incoming mail server only. Sends it to a DSPAM | machine who checks the mail for spam and the uses Dovecot to deliver the | email. | | My problem is this: | | I have users setup with forwards in my MySQL database. So dovecot tries to | deliver mail (such as to my blackberry) and it fails. What is the proper | way for me to forward this mail outside of the local mailbox? | | Should I use .forward files in the mailboxes themselves instead? | | Thanks, | | Fred
Evaggelos Balaskas - http://ebalaskas.gr Unix System Engineer Informatics Engineer Technological Education -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHqKhQWIK+Pe9twhoRAhhoAJwNfH+GvLA97pw+rRb7qS3p3VMwEgCeOM8r Ie7v3eol+7moiprUwIpuEM8= =CDGX -----END PGP SIGNATURE-----
On Tue, 5 Feb 2008, Evaggelos Balaskas wrote:
use sieve Action redirect
http://www.ietf.org/rfc/rfc3028.txt Paragraph : 4.3
More directly: http://tools.ietf.org/html/rfc3028#section-4.3
Plus it lets you know in the header that it's been "obsoleted by RFC 5228". The relevant section of the new RFC:
http://tools.ietf.org/html/rfc5228#section-4.2
Best, Ben
Fred Newtz wrote: | I have a little problem on my hands. I followed the following how to and | made plenty of changes. | | http://www.howtoforge.com/postfix_mysql_dovecot_dspam_clamav_postgrey_rbl_de | bian_etch | | However my basic setup is this: | | Mail comes in via Postfix incoming mail server only. Sends it to a DSPAM | machine who checks the mail for spam and the uses Dovecot to deliver the | email. | | My problem is this: | | I have users setup with forwards in my MySQL database. So dovecot tries to | deliver mail (such as to my blackberry) and it fails. What is the proper | way for me to forward this mail outside of the local mailbox? | | Should I use .forward files in the mailboxes themselves instead? | | Thanks, | | Fred
Evaggelos Balaskas - http://ebalaskas.gr Unix System Engineer Informatics Engineer Technological Education -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHqKhQWIK+Pe9twhoRAhhoAJwNfH+GvLA97pw+rRb7qS3p3VMwEgCeOM8r Ie7v3eol+7moiprUwIpuEM8= =CDGX -----END PGP SIGNATURE-----
Thanks guys! I will check this out!
Fred
-----Original Message----- From: Benjamin R. Haskell [mailto:dovecot@benizi.com] Sent: Tuesday, February 05, 2008 12:25 PM To: Evaggelos Balaskas Cc: Fred Newtz; 'Dovecot Mailing List' Subject: Re: [Dovecot] Predicament
On Tue, 5 Feb 2008, Evaggelos Balaskas wrote:
use sieve Action redirect
http://www.ietf.org/rfc/rfc3028.txt Paragraph : 4.3
More directly: http://tools.ietf.org/html/rfc3028#section-4.3
Plus it lets you know in the header that it's been "obsoleted by RFC 5228". The relevant section of the new RFC:
http://tools.ietf.org/html/rfc5228#section-4.2
Best, Ben
Fred Newtz wrote: | I have a little problem on my hands. I followed the following how | to and made plenty of changes. | | http://www.howtoforge.com/postfix_mysql_dovecot_dspam_clamav_postgrey_ rbl_de | bian_etch | | However my basic setup is this: | | Mail comes in via Postfix incoming mail server only. Sends it to a | DSPAM machine who checks the mail for spam and the uses Dovecot to | deliver the email. | | My problem is this: | | I have users setup with forwards in my MySQL database. So dovecot tries to | deliver mail (such as to my blackberry) and it fails. What is the | proper way for me to forward this mail outside of the local mailbox? | | Should I use .forward files in the mailboxes themselves instead? | | Thanks, | | Fred
Evaggelos Balaskas - http://ebalaskas.gr Unix System Engineer Informatics Engineer Technological Education -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHqKhQWIK+Pe9twhoRAhhoAJwNfH+GvLA97pw+rRb7qS3p3VMwEgCeOM8r Ie7v3eol+7moiprUwIpuEM8= =CDGX -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
~From sieve plugin source libsieve code : Compliant with RFC 3028
I dont know if more actions from the 5228 (and 5229) rfc are compliant with dovecot sieve plugin.
btw: i wasnt informed for the updated rfc, thanks
Benjamin R. Haskell wrote: | | More directly: http://tools.ietf.org/html/rfc3028#section-4.3 | | Plus it lets you know in the header that it's been "obsoleted by RFC | 5228". The relevant section of the new RFC: | | http://tools.ietf.org/html/rfc5228#section-4.2
Evaggelos Balaskas - http://ebalaskas.gr Unix System Engineer Informatics Engineer Technological Education -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHqh6kWIK+Pe9twhoRAhfjAKCCL9g/MgMZfnquEBG6s3VP28zIhACgynnm fANuXsJhWWRrZONDg9H4PGc= =Fd/M -----END PGP SIGNATURE-----
participants (5)
-
Benjamin R. Haskell
-
Dmitry Filonov
-
Evaggelos Balaskas
-
Fred Newtz
-
Timo Sirainen