[Dovecot] Quota + Sieve
Thanx to everybody's help , i have got a working combination of;
- dovecot LDA
- smtp auth thru dovecot sasl
- postfix
- virtual users in mysql
- postfixadmin
- thunderbird as the email client
Just 2 additional questions -
A. Sieve ..............
With the imap filters in thunderbird, do i need to use sieve in dovecot? my initial observations/ findings say "no"?
B. Quota .............
If i have not set quota in dovecot or postfix ( no quota related configuration ), may i then assume, the users have "unlimited storage" , limited only by the hardware/filesystem?
I would like to have this feature ( just like unlimited storage in yahoo ) and just have a cron script running regularly to delete old emails ( for middle level, low level users ). Is such a strategy ok?
regards, mgomez
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, 26 Feb 2009, Linux Advocate wrote:
A. Sieve ..............
With the imap filters in thunderbird, do i need to use sieve in dovecot? my initial observations/ findings say "no"?
Thunderbird filters work in the client, not server. If you want to filter before the client has seen or downloaded the message, you need Sieve.
B. Quota .............
If i have not set quota in dovecot or postfix ( no quota related configuration ), may i then assume, the users have "unlimited storage" , limited only by the hardware/filesystem?
I would like to have this feature ( just like unlimited storage in yahoo ) and just have a cron script running regularly to delete old emails ( for middle level, low level users ). Is such a strategy ok?
This is completely up to you :)
It depends on you user base, how they react upon "delete old mails". I wouldn't do so.
Bye,
Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iQEVAwUBSaZ4OXWSIuGy1ktrAQJeVAgAx6IkLEIDzWjiDi2SqgvbrgkkBUAroq+c AlMIIE7O9Ptu7d9dCIuTWaE1E3i2ZQ1MERTDlmury2SGRM4oHsKsgF4sfA9RosiP SWa8qPjYjaZ8r9grh9KbSeb49qOSrVQVNubIefS8bmsU1nKc72cosgbasy0R1aIf Dx8eORzjFQg2UTiUzW6wg1CLPoqqyhu+syu/FfwEmbMSXP5b3qDprDMcG0iuXy5k Q4MEn8ZMx+qgLVS1M3+rqJ81Z0dTr1aWGN/rdFwCDkh2NvK/DqxcOKiqDjuXm8lC pUx/LgUV/I+mcAPp3JysobZzbOyB3K5fIebADAzYIgkk+V5vttZ/AA== =aNLw -----END PGP SIGNATURE-----
steffen,
A. Sieve ..............
With the imap filters in thunderbird, do i need to use sieve in dovecot? my initial observations/ findings say "no"?
Thunderbird filters work in the client, not server. If you want to filter before the client has seen or downloaded the message, you need Sieve.
users will most probably use filters to sort out their email, therefore its better to be client side, as all have their won way or working? what can i use sieve on the server side for?
typo in earlier email... sorry... rephrasing question/comment.
steffen,
A. Sieve ..............
With the imap filters in thunderbird, do i need to use sieve in dovecot? my initial observations/ findings say "no"?
Thunderbird filters work in the client, not server. If you want to filter before the client has seen or downloaded the message, you need Sieve.
users will most probably use filters to sort out their email, therefore its better to be client side? as all have their own way or working/ classifying their email?
Additionally what can i use sieve on the server side for?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, 26 Feb 2009, Linux Advocate wrote:
With the imap filters in thunderbird, do i need to use sieve in dovecot? my
initial observations/ findings say "no"?
Thunderbird filters work in the client, not server. If you want to filter before the client has seen or downloaded the message, you need Sieve.
users will most probably use filters to sort out their email, therefore its better to be client side? as all have their own way or working/ classifying their email?
Well, if you ask me this question, it is probably better to not use Sieve, because the way users work is set - basta - any change would cause problems.
Several of our users have slow connections, therefore they want to see only minimal stuff in the INBOX, definitely no message the relay tagged as SPAM. They check out the other folders from their offices only. Client-side filtering would require them to download all messages, even SPAM, just to move them into a "not-urgent" folder never looked at.
This is one example of server-side filtering.
Initially I deployed a fixed Sieve script for everybody, which moved tagged SPAM into a SPAM folder, but more and more users wanted to hack their own.
Additionally what can i use sieve on the server side for?
Well, current implementation is cmusieve, see: http://hg.dovecot.org/dovecot-sieve-1.0/file/1ddefc5e4e33/src/libsieve/READM...
Dovecot v1.2 will support/use: http://hg.rename-it.nl/dovecot-libsieve/file/ab9a06342d33/README
The basic language is the same, but there are different extensions supported.
Bye,
Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iQEVAwUBSaaak3WSIuGy1ktrAQLbmQf9HbwHJzc5sj95Es/tzyJzTXUMtM0r8XDp 8uRVMlVDTwS67hwranW0CJnml6WhuVzbptv4XS9td4gwERn3PyO+AvDU8RvPuBhV y+e6Qq6JITFtYGJZ1AJ2Cip0fADOgwHw9cLysMVtt4WmlxNwA8jr+sbXRfoz+x3i Zw4AfCsjS8w0RBNY0r1x3V67Z0QEqzaku5dh9lZMazmuo1+jPX/asdiJcf9SyKN4 B3SHkCdX1h+5g4QQ8F6dVTKD/YElZ85oy1HcYCg2MRQjzb/MKLPT48UHYY3VJbVu Q+N0U+oVkdN1OA6gEGVEKqPCZW09rBqFVXuwj8anyFOUXX3AijMsbQ== =+0AJ -----END PGP SIGNATURE-----
thanx.
On Thu, 26 Feb 2009, Linux Advocate wrote:
With the imap filters in thunderbird, do i need to use sieve in dovecot? my
initial observations/ findings say "no"?
Thunderbird filters work in the client, not server. If you want to filter before the client has seen or downloaded the message, you need Sieve.
users will most probably use filters to sort out their email, therefore its better to be client side? as all have their own way or working/ classifying their email?
Well, if you ask me this question, it is probably better to not use Sieve, because the way users work is set - basta - any change would cause problems.
Several of our users have slow connections, therefore they want to see only minimal stuff in the INBOX, definitely no message the relay tagged as SPAM. They check out the other folders from their offices only. Client-side filtering would require them to download all messages, even SPAM, just to move them into a "not-urgent" folder never looked at.
This is one example of server-side filtering.
Initially I deployed a fixed Sieve script for everybody, which moved tagged SPAM into a SPAM folder, but more and more users wanted to hack their own.
Additionally what can i use sieve on the server side for?
Well, current implementation is cmusieve, see: http://hg.dovecot.org/dovecot-sieve-1.0/file/1ddefc5e4e33/src/libsieve/READM...
Dovecot v1.2 will support/use: http://hg.rename-it.nl/dovecot-libsieve/file/ab9a06342d33/README
The basic language is the same, but there are different extensions supported.
Bye,
- -- Steffen Kaiser
participants (2)
-
Linux Advocate
-
Steffen Kaiser