Re: [Dovecot] Save/restore IMAP session state
Quoting Timo Sirainen t...@iki.fi: A week ago I thought I'd see how easy it would be to implement this. I got a basic proof of concept working as a X-STATE command. [snip] This could also be used to implement quick session state restoring for webmails (as suggested by Michael Slusarz). Wow. We must have some sort of crazy mind-meld going on: I have been working on this concept the last few days with the idea of generating some sort of draft proposal to provoke further discussion going forward. I would say great minds think alike, but that would be giving myself too much credit. So this provided the necessary motivation to finish the draft concept. Now that I have (somewhat) figured out the RFC 2629 XML format for doing this kind of thing, hopefully this has is presented in a somewhat coherent format. The draft, which is significantly more comprehensive than your suggestion, can be found here: https://raw.github.com/slusarz/horde-sandbox/master/imap-state-draft/draft-imap-state-00.txt Not sure if this should remain the forum for discussing this concept, or if we should move to private messages (or even to the imap-protocol list). Let me know your thoughts on this (or anyone else with an interest). michael
Re: [Dovecot] POLL: v2.2 to allow one mail over quota?
On 29.10.2012 21:39, Timo Sirainen wrote: So what do you think about v2.2 allowing delivery of one last mail even if it brings the user over quota? Except add a limit that if the message size is as much as the user's entire quota limit it wouldn't be added (or 50% or ..?). Also IMAP wouldn't allow this, since user would get an error anyway. I could make this also optional, but if nobody really wants to keep the old behavior there's really no point in adding the option. Great idea. This makes being over quota a stable state and makes it easier for users to understand their problem. Regards Christian
Re: [Dovecot] POLL: v2.2 to allow one mail over quota?
Timo Sirainen wrote: Currently if user is 1MB under quota and someone tries to deliver mail that is over 1MB, Dovecot rejects the mail. But smaller mails aren't rejected probably for days. So user might not even realize that they didn't receive one of the mails. Also having a user almost over quota is a rather strange state I think. So what do you think about v2.2 allowing delivery of one last mail even if it brings the user over quota? Except add a limit that if the message size is as much as the user's entire quota limit it wouldn't be added (or 50% or ..?). Also IMAP wouldn't allow this, since user would get an error anyway. I could make this also optional, but if nobody really wants to keep the old behavior there's really no point in adding the option. This will finally make possible to reject RCPT TO: before the message size is known instead of accepting the message and sending a bounce later (bouncing SPAM is not good). -- Talex Spółka Akcyjna z siedzibą w Poznaniu adres: ul. Karpia 27d, 61-619 Poznań NIP 782-00-21-045 zarejestrowana w Sądzie Rejonowym Poznań – Nowe Miasto i Wilda w Poznaniu VIII Wydział Gospodarczy - KRS pod nr 48779 kapitał zakładowy: 3.000.092,00 PLN (w całości wpłacony) Uwaga: Niniejsza wiadomość, w szczególności jej treść oraz załączniki, może być poufna. W przypadku, gdy nie jest Pan/Pani zamierzonym jej adresatem, informujemy, że wszelkie rozpowszechnianie, dystrybucja lub powielanie powyższej wiadomości jest zabronione. Jednocześnie prosimy o powiadomienie nadawcy oraz niezwłoczne usunięcie powyższej wiadomości wraz z załącznikami. Dziękujemy, Talex S.A. w Poznaniu. Confidentiality Notice: This email, particularly its content and any attached files, may be confidential. If you are not an intended recipient, any disclosure, distribution and reproduction of this message is prohibited. In this case please notify the sender immediately and then delete this message and any attachments. Thank you, Talex S.A., Poznan.
Re: [Dovecot] POLL: v2.2 to allow one mail over quota?
* Jan-Frode Myklebust janfr...@tanso.net: +1 Better to be lenient, than to confuse users by accepting some but not other messages. Amen to that! +1 -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
[Dovecot] copymail deleted
Hi, I had enabled an option in dovecot. mail_attachment_dir = /var/mail/virtual/copymail/attachments After a while I checked /var/mail/virtual and did some cleanup. I did not remember that copymail was specified in dovecot and erased it. Oct 30 10:56:05 mx0 dovecot: imap(hidden): Error: file_istream.stat(/var/mail/virtual/copymail/attachments/6a/50/6a506530265ef7c9feb396410eaf6946036e9a79-b034401e794009503a042cb72ff6) failed: No such file or directory Oct 30 10:56:05 mx0 dovecot: imap(hidden): Error: istream-concat: Failed to get size of stream /var/mail/virtual/copymail/attachments/6a/50/6a506530265ef7c9feb396410eaf6946036e9a79-b034401e794009503a042cb72ff6 Oct 30 10:56:05 mx0 dovecot: imap(hidden): Error: read() failed: Invalid argument (FETCH for mailbox INBOX UID 196) Oct 30 10:56:05 mx0 dovecot: imap(hidden): Disconnected: Internal error occurred. Refer to server log for more information. [2012-10-30 10:56:05] in=150 out=950 I have Bacula and have restored most of the stuff, but obviously not all files. That is not too important. But I do not know, how to tell dovecot that it may forget about files that produce a No such file or directory error. Can I do some rescan/rebuild in dovecot? Kind regards -Christian Rößner -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Joerg Heidrich
Re: [Dovecot] copymail deleted
On 30.10.2012, at 12.11, Christian Rößner wrote: Oct 30 10:56:05 mx0 dovecot: imap(hidden): Error: file_istream.stat(/var/mail/virtual/copymail/attachments/6a/50/6a506530265ef7c9feb396410eaf6946036e9a79-b034401e794009503a042cb72ff6) failed: No such file or directory I have Bacula and have restored most of the stuff, but obviously not all files. That is not too important. But I do not know, how to tell dovecot that it may forget about files that produce a No such file or directory error. Can I do some rescan/rebuild in dovecot? Currently you can't in any easy way. The easiest fix for now I think would be to write a script that reads through dbox files, parses the attachment metadata lines and recreates the missing files with the original size (e.g. sparse-0-filled). The dbox parsing can be done easily with: doveadm dump m.1 | grep ^msg.ext-ref The format is: 1*(start offset byte count options ref) If the options=- then the byte count is the final size. If options=B then byte count is the base64-encoded size while the original file has to be base64-decoded size.
Re: [Dovecot] POLL: v2.2 to allow one mail over quota?
Sounds like a reasonable idea, but one has to keep in mind that file system quotas never work that way. So that change would make quota=fs behave differently from the rest. So it should at least be configurable, I think.
[Dovecot] Problem about SSL for Dovecot.
Hi All,
With the below setting (cropped), the ssl certificate(signed by godaddy) don’t
seems to work. It will still ask me if I want to accept this certificate.
I have use the same certificate for apache host and postfix it works without
any prompt.
dovecot version : 2.0.19
# OS: Linux 3.2.0-32-generic-pae i686 Ubuntu 12.04.1 LTS
Dovecot config:
ssl = required
ssl_cert = /aaa/4/merged5.crt
ssl_key = /certs/proximityjobs.key
userdb {
args = /etc/dovecot/dovecot-mysql.conf
driver = sql
}
verbose_ssl = yes
protocol lda {
auth_socket_path = /var/run/dovecot/auth-master
lda_mailbox_autocreate = yes
log_path = /var/log/sieve.log
mail_plugins = quota sieve autocreate acl
postmaster_address = root
}
protocol imap {
imap_client_workarounds = tb-extra-mailbox-sep
mail_plugins = quota imap_quota autocreate acl imap_acl
}
protocol pop3 {
mail_plugins = quota
pop3_client_workarounds = outlook-no-nuls oe-ns-eoh
pop3_uidl_format = %08Xu%08Xv
}
Best Regards,
Sheng Wei
Re: [Dovecot] mbox vs. maildir storage block waste
On 2012-10-29 5:42 PM, Timo Sirainen t...@iki.fi wrote: On 29.10.2012, at 23.15, Christoph Anton Mitterer wrote: btw: What are the actual advantages of sdbox over maildir? * Not moving files from new/ to cur/ directory * Not renaming files when changing message flags * Not readdir()ing directories (although maildir_very_dirty_syncs=yes helps a lot with this) Basically less disk I/O and making it possible to have mailboxes with a huge number of messages without everything slowing down horribly. I had been wanting to ask about this too... So... what are the disadvantages? -- Best regards, Charles
Re: [Dovecot] mbox vs. maildir storage block waste
On 2012-10-29 4:54 PM, Christoph Anton Mitterer cales...@scientia.net wrote: In the end I probably changed my opinion. ~7GB of wasted block space for all my mails is actually quite a lot, but in days of cheap disk space it's acceptable. And with mbox one has IMHO the major disadvantage that mailservers (including dovecot) store some meta-data_in_ it (i.e. in the mails themselves) , which I don't like a lot. I still think about reports that mbox is much faster with full text search (which sounds reasonable)... but therefore one needs probably and database backend anyway. What makes the most sense for me is to use mbox (or mdbox) for longer term storage that you may be offloading to slower storage systems, and use maildir (or sdbox) for the new mails... Would work great as long as you have a reliable method for archiving older mails out to your slower storage. This is what I plan on doing someday... -- Best regards, Charles
Re: [Dovecot] POLL: v2.2 to allow one mail over quota?
On Oct 30, 2012 5:43 AM, Ralf Hildebrandt ralf.hildebra...@charite.de wrote: * Jan-Frode Myklebust janfr...@tanso.net: +1 Better to be lenient, than to confuse users by accepting some but not other messages. Amen to that! +1 Surely the answer is that as soon as any mail is rejected an over-quota message is injected? That way, the quota remains as it currently is, but the user will a) be aware that he's over or nearly over quota, b) that a mail was rejected for being too big (if you inject the right over-quota message). Simon
Re: [Dovecot] mbox vs. maildir storage block waste
On Tue, 2012-10-30 at 07:00 -0400, Charles Marcus wrote: So... what are the disadvantages? I (but I'm no expert) would guess that it's a dovecot-only format. No support from most other tools,... I'd guess you cannot use e.g. maildrop with it, or can you? I personally was always a bit worried, when meta-data is put in the mail... now AFAIU dbox does _not_ do this... and you can cleanly extract each unmodified mail from the dbox fail (single or multi), right? Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature
Re: [Dovecot] mbox vs. maildir storage block waste
On Tue, 2012-10-30 at 07:03 -0400, Charles Marcus wrote: What makes the most sense for me is to use mbox (or mdbox) for longer term storage that you may be offloading to slower storage systems, and use maildir (or sdbox) for the new mails... Was also something I thought about... still the more I think about it, the more I hate, that with mbox meta-data is stored in the mails. Would work great as long as you have a reliable method for archiving older mails out to your slower storage. I still hope for some DB backend ;) Chris. smime.p7s Description: S/MIME cryptographic signature
[Dovecot] POP3 Proxy : user format not accepted
Hello, I want to use Dovecot as a POP3 proxy (http://wiki.dovecot.org/HowTo/ImapProxy). All is working fine on my sample platform, except that I have plenty (several thousands) of users that login using local_part#domain, instead of local_part@domain, which is an old setting on my POP3 server. And in that case, Dovecot returns 'Authentication failed'. Here is my proxy table : mysql select * from tbl_proxy; ++-++ | user | host | destuser | ++-++ | christ...@mydom.fr | 10.10.100.1 | christ...@mydom.fr | | christian#mydom.fr | 10.10.100.1 | christ...@mydom.fr | ++-++ If I login on the Dovecot proxy with the '@' version, everything is fine : root : ~ telnet 10.10.100.24 110 Trying 10.10.100.24... Connected to 10.10.100.24 (10.10.100.24). Escape character is '^]'. +OK Dovecot ready. user christ...@mydom.fr +OK pass azerty42 +OK christian#mydom.fr has 3 messages (3561 octets) And MySQL logs show the query : 121030 12:55:28 3 Query SELECT NULL AS password, host, destuser, 'Y' AS nologin, 'Y' AS nodelay, 'Y' AS proxy, 'Y' AS nopassword FROM tbl_proxy WHERE user = 'christ...@mydom.fr' If I login on the Dovecot proxy with the '#' version, it fails : root : ~ telnet 10.10.100.24 110 Trying 10.10.100.24... Connected to 10.10.100.24 (10.10.100.24). Escape character is '^]'. +OK Dovecot ready. user christian#mydom.fr +OK pass azerty42 -ERR Authentication failed. And nothing shows up the the MySQL logs. If I login directly on the POP server with the same credentials, no problem : root : ~ telnet 10.10.100.1 110 Trying 10.10.100.1... Connected to 10.10.100.1 (10.10.100.1). Escape character is '^]'. +OK Welcome to POP3 Server V 2.06. Authenticate yourself. user christian#mydom.fr +OK Password required for christian#mydom.fr pass azerty42 +OK christian#mydom.fr has 3 messages (3561 octets) Any idea ? Is the '#' not internally supported in the user login by Dovecot ? Thanks in advance. Christian
Re: [Dovecot] POP3 Proxy : user format not accepted
On 30.10.2012, at 14.01, Christian Gregoire wrote: Any idea ? Is the '#' not internally supported in the user login by Dovecot ? See auth_username_chars setting.
[Dovecot] Dovecot does not update acl_shared_dict file
Hi all, Firstly, thanks for all your effort with this software. Much appreciated. I am having a slight issues trying to enable reading of other users mailboxes. The docs are a little sparse for those that aren't mailadmin heros, I wonder if anyone could please help me see where I am going wrong. I would like to allow some users to list and read the mailboxes of others. E.g: When User1 logs in, they are presented with a list of their own folders, and those of User2, User3, etc to which they have (e.g. read/list) access I followed the instructions on the wiki (for Version 1.X)- there are two concepts here: 1. Grant some [e.g. list/read] access on a mailbox folder to a particular user 2. Enable the acl_shared_dict to allow dovecot to track (and display to IMAP clients) the folders to which they have access. This will take the form of a BDB file: /var/lib/dovecot/shared-mailboxes.db This file can only be updated by using the SETACL command. *This is where I have the problem*. The SETACL command does nothing. No matter how hard I try, I cannot get dovecot to update this file. The only indication I have that the file exists and is readable by dovecot is the disappearance from the logs of the line: No acl_shared_dict setting - shared mailbox listing is disabled So I can see that dovecot knows the file is there because it does not complain any more. The file is there (because I created it myself, although it is empty: size = 0), and in a moment of weakness I made sure it could be updated (this will be changed back!): ls -l /var/lib/dovecot/shared-mailboxes.db -rwxrwxrwx 1 dovecot dovecot 0 2012-10-30 12:27 /var/lib/dovecot/shared-mailboxes.db But if I try to update the ACL, absolutely nothing happens: [ command ] [ reply ] telnet localhost 143 * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=CRAM-MD5] Email server a login [User2] [pass] a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH ACL RIGHTS=texk] Logged in a SETACL Inbox [User 1] rl a OK Setacl complete. At this time, in the dovecot log (with debug enabled): 2012-10-30 13:55:24 IMAP([User2]): Info: Namespace : Using permissions from /home/mailboxes/[domain]/[User1]: mode=0770 gid=-1 2012-10-30 13:55:24 IMAP([User2]): Info: acl vfile: reading file /home/mailboxes/[domain]/[User1]/dovecot-acl 2012-10-30 13:55:24 IMAP([User2]): Info: acl vfile: reading file /home/mailboxes/[domain]/[USer1]/dovecot-acl Can anyone please help me track down what I'm doing wrong here?! It's driving me mad! Thanks for your time if you've read this far!! As requested: dovecot --version 1.2.9 base_dir: /var/run/dovecot/ log_path: /var/log/dovecot info_log_path: /var/log/dovecot.info log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps imap listen: 127.0.0.1:143 ssl_listen: 37.235.54.98 ssl_cert_file: /etc/ssl/dovecot.crt ssl_key_file: /etc/ssl/private/dovecot.key login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_greeting: Email server valid_chroot_dirs: /var/spool/vmail mail_location: maildir:/home/mailboxes/%d/%n mail_debug: yes mbox_write_locks: fcntl dotlock mail_plugins: acl imap_acl lda: postmaster_address: [ valid@ddress ] auth default: mechanisms: plain cram-md5 verbose: yes passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: passwd-file args: /etc/dovecot/users socket: type: listen client: path: /var/spool/postfix/private/auth-client mode: 432 user: postfix group: postfix master: path: /var/spool/postfix/private/auth-master mode: 384 user: postfix group: postfix plugin: acl: vfile acl_shared_dict: file:/var/lib/dovecot/shared-mailboxes.db acl: vfile:/etc/dovecot/acls
Re: [Dovecot] copymail deleted
The format is: 1*(start offset byte count options ref) If the options=- then the byte count is the final size. If options=B then byte count is the base64-encoded size while the original file has to be base64-decoded size. Ok, so far I have grep'ed this here: msg.ext-ref = 83713 1282212 B76 6a/50/6a506530265ef7c9feb396410eaf6946036e9a79-b034401e794009503a042cb72ff6 1443213 550635 B76 56/f2/56f25e225385902f3fc5185dc3d0103f59b34d14-b134401e794009503a042cb72ff6 1994019 477177 B76 c4/36/c436874b56cf3cd105e82f9243c7eac53c467f32-b234401e794009503a042cb72ff6 2561522 1075531 B76 77/af/77af1045a783308dbbf2f8a464c5136a0407e720-b334401e794009503a042cb72ff6 3715582 1195635 B76 99/33/99339b17a21ce052cd8f47f1d88c6e869cc1650b-b434401e794009503a042cb72ff6 4966686 715386 B76 fe/df/fedf23091720d3fa649af3bd6537e66304b8061a-b534401e794009503a042cb72ff6 5805913 788086 B76 ab/36/ab36f53a443f1855bc13caaba9e01e9464b2921f-b634401e794009503a042cb72ff6 6684258 906273 B76 10/70/1070d21039bc3f305bb948315a01344eefb2a465-b734401e794009503a042cb72ff6 7590707 204613 B76 39/44/394402c057791482f79351363f025ae0a7caf1b0-b834401e794009503a042cb72ff6 7795492 1349911 B76 41/bd/41bd01b4880065e5136cafbd1d191a1f8a1ead55-b934401e794009503a042cb72ff6 9271435 1504539 B76 c6/71/c671c1367e843741a2cc8f083a37231522d37640-ba34401e794009503a042cb72ff6 10877759 357555 B76 58/f5/58f582d2644025b843cf991f5cf783d27f9d90c9-bb34401e794009503a042cb72ff6 11826037 890683 B76 82/da/82dabbe06f269e7c79417db3b570246a648d2139-bc34401e794009503a042cb72ff6 msg.ext-ref = 118947 317624 B76 ad/9b/ad9be52e11433cd0337cda13bf0a458fd0fd948d-df905c0cd33d0950ae782cb72ff6 436770 139669 B76 78/15/781526d896a0530a5e76ebce65f2eb690d102dd3-e0905c0cd33d0950ae782cb72ff6 576610 457829 B76 61/3a/613a70c8515c572a04211fb0c63828d9c9acfb70-e1905c0cd33d0950ae782cb72ff6 1107667 410786 B76 7f/6b/7f6b7ee9b08a73600d98e8583aae343a90e76b96-e2905c0cd33d0950ae782cb72ff6 1611186 816686 B76 ff/ff/9362c5356d8bedb17bd56edf0524bd0ae7b3-e3905c0cd33d0950ae782cb72ff6 2516232 643918 B76 4f/aa/4faa153fada5ceea79016cf2eadc1d05110f3f2e-e4905c0cd33d0950ae782cb72ff6 3291363 1036359 B76 e6/f3/e6f342bf28e8edfd3214666aaa52f0c067bae22b-e5905c0cd33d0950ae782cb72ff6 4418344 668813 B76 20/78/2078c98fb9bcadeeaa49bc38dc31548142fc71b1-e6905c0cd33d0950ae782cb72ff6 5154786 502218 B76 40/f4/40f4af3ad2077493caa34faabb201531609b50c4-e7905c0cd33d0950ae782cb72ff6 5782912 628591 B76 cc/a9/cca98a2a325f1be9a398d62890836cf11f267c4b-e8905c0cd33d0950ae782cb72ff6 6518382 526201 B76 17/47/1747a90b58c50c3d01da7f3a6601f7073cd5b163-e9905c0cd33d0950ae782cb72ff6 7140759 517776 B76 04/af/04afe7deb8e6ee99153433d2845da417e54cd042-ea905c0cd33d0950ae782cb72ff6 7769983 2317979 B76 05/13/0513bcfceff303125f233ad2c01c5ba2ed96c6a2-eb905c0cd33d0950ae782cb72ff6 10214312 3097649 B76 35/e4/35e46902b3e6473b9689a92acd71e58fb7165a8f-ec905c0cd33d0950ae782cb72ff6 msg.ext-ref = 75027 1291257 B76 b9/dc/b9dcd6899ae65e5c11b122d7bfc3be9fefc21024-5df010068b3f0950c27d2cb72ff6 1441078 1131344 B76 f6/e6/f6e63f000d6501be472629747448057b122104c1-5ef010068b3f0950c27d2cb72ff6 2572595 2218094 B76 93/96/9396c5eaeac2615119e55c67fa8f010332ba0fd3-5ff010068b3f0950c27d2cb72ff6 4790862 2211695 B76 cc/a5/cca5607fb739306f3628a19575dc41432f74a22d-60f010068b3f0950c27d2cb72ff6 7002730 2614603 B76 66/10/661002c8039997174e34b9ef31d0e693a556eebe-61f010068b3f0950c27d2cb72ff6 9617506 2760312 B76 8c/65/8c656fe835af26c175337cd318daca8ae8e00369-62f010068b3f0950c27d2cb72ff6 12377991 2341764 B76 19/c8/19c83e0bf1284e74e49feecaf95506266201551d-63f010068b3f0950c27d2cb72ff6 15209343 406758 B76 b6/62/b66216837cc48422e22e7a9a22631f840a49ef78-64f010068b3f0950c27d2cb72ff6 15616301 136877 B76 06/9f/069f5ab86dc9e8e9972f3f5c0dda03c1f3103730-65f010068b3f0950c27d2cb72ff6 15753350 971075 B76 a7/7c/a77c36690ff0f0f774b82efaf15f93535ba027e9-66f010068b3f0950c27d2cb72ff6 16849194 1197333 B76 4f/28/4f2881be6d0e8a7f53c0e226c0dbb148b05674c7-67f010068b3f0950c27d2cb72ff6 18168424 850768 B76 92/72/9272e1ea7ceb79df6222686bf157f957fa9851c1-68f010068b3f0950c27d2cb72ff6 19019393 135641 B76 60/fd/60fdcd7851c8f0a21f342aaafce9e49a3e00e1aa-69f010068b3f0950c27d2cb72ff6 19155207 897179 B76 63/59/6359abf4f9e806e3990e0d6590e519924c838fa5-6af010068b3f0950c27d2cb72ff6 20169966 1022612 B76 f8/65/f8654367f5df050d23565644e83c8c50abb69c39-6bf010068b3f0950c27d2cb72ff6 But I did not understand the base64 explanation. Sorry :) For me it seems all options are B-prefixed. So they are all base64? But which value is now the size and how do I create the missing files now? Using dd? Can you give me an example from the output above? That would help me. Thanks a lot Kind regards -Christian Rößner -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669
Re: [Dovecot] copymail deleted
On 30.10.2012, at 15.28, Christian Rößner wrote: msg.ext-ref = 83713 1282212 B76 6a/50/6a506530265ef7c9feb396410eaf6946036e9a79-b034401e794009503a042cb72ff6 But I did not understand the base64 explanation. Sorry :) For me it seems all options are B-prefixed. So they are all base64? But which value is now the size and how do I create the missing files now? Using dd? Can you give me an example from the output above? That would help me. They are all base64 yes, the B76 means that all the encoded lines will be 76 chars long. So the file size above needs to be 1282212, divided by 77 (76+LF) = 16652 full lines and 8 bytes over. Base64 encodes 3 byte blocks into 4 byte chars, so the original data has (16652*76+8)/4*3 = 949170 bytes (or 1-2 bytes less, but that makes no difference because it's padded anyway). So if you create /attachments/6a/50/6a506530265ef7c9feb396410eaf6946036e9a79-b034401e794009503a042cb72ff6 that is 949170 bytes long, and do the same for the rest of the attachments, you should be able to read this mail without errors. You can easily create the files without wasting space with: dd if=/dev/zero of=foo bs=1 seek=949169 count=1
Re: [Dovecot] copymail deleted
Hi, msg.ext-ref = 83713 1282212 B76 6a/50/6a506530265ef7c9feb396410eaf6946036e9a79-b034401e794009503a042cb72ff6 But I did not understand the base64 explanation. Sorry :) For me it seems all options are B-prefixed. So they are all base64? But which value is now the size and how do I create the missing files now? Using dd? Can you give me an example from the output above? That would help me. They are all base64 yes, the B76 means that all the encoded lines will be 76 chars long. So the file size above needs to be 1282212, divided by 77 (76+LF) = 16652 full lines and 8 bytes over. Base64 encodes 3 byte blocks into 4 byte chars, so the original data has (16652*76+8)/4*3 = 949170 bytes (or 1-2 bytes less, but that makes no difference because it's padded anyway). So if you create /attachments/6a/50/6a506530265ef7c9feb396410eaf6946036e9a79-b034401e794009503a042cb72ff6 that is 949170 bytes long, and do the same for the rest of the attachments, you should be able to read this mail without errors. You can easily create the files without wasting space with: dd if=/dev/zero of=foo bs=1 seek=949169 count=1 Thanks. I have calculated both other files and recreated zero padded files. Now I am going to watch the log file and see, if errors are gone. One last question: If the user now opens a mail, where the attachments are broken and he/she removes the mail, are the created hand-made files be removed automatically? Thanks in advance Kind regards -Christian Rößner -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Joerg Heidrich
[Dovecot] Pigeonhole 3.3 broken against Dovecot 2.1.10
I'm compiling as I normally do. The config line for Dovecot is: configure --with-ldap --with-ssl --with-bzlib --with-zlib --with-stemmer --with-lucene --with-ldap followed by make make install Then a 'configure' for Pigeonhole, followed by make, yields: libtool: link: gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -o .libs/sieve-dump sieve-dump.o -Wl,--export-dynamic ../../src/lib-sieve/.libs/libdovecot-sieve.so ../../src/lib-sieve-tool/.libs/libsieve-tool.a /usr/local/lib/dovecot/libdovecot-storage.so /usr/local/lib/dovecot/libdovecot-lda.so -L/usr/local/lib/dovecot /usr/local/lib/dovecot/libdovecot.so -lrt -Wl,-rpath -Wl,/usr/local/lib/dovecot libtool: link: gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -o .libs/sievec sievec.o -Wl,--export-dynamic ../../src/lib-sieve/.libs/libdovecot-sieve.so ../../src/lib-sieve-tool/.libs/libsieve-tool.a /usr/local/lib/dovecot/libdovecot-storage.so /usr/local/lib/dovecot/libdovecot-lda.so -L/usr/local/lib/dovecot /usr/local/lib/dovecot/libdovecot.so -lrt -Wl,-rpath -Wl,/usr/local/lib/dovecot /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `sk_new_null@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_get_error@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_get_peer_certificate@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_CTX_load_verify_locations@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_CTX_use_PrivateKey@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `DH_free@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_set_ex_data@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_CTX_set_tmp_rsa_callback@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_CTX_use_certificate@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_alert_desc_string_long@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_get_ex_data@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_get_ex_new_index@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_CTX_set_client_CA_list@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `X509_get_ext_d2i@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_accept@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `X509_STORE_add_cert@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSLv23_server_method@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `OBJ_txt2nid@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_write@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `sk_num@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `BIO_ctrl_get_write_guarantee@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_set_cipher_list@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `sk_push@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `ERR_get_error@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_alert_type_string_long@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_COMP_get_name@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `ENGINE_by_id@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `BIO_write@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `i2d_DHparams@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `X509_NAME_ENTRY_get_data@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_CIPHER_get_name@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_use_PrivateKey@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_set_info_callback@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `X509_get_subject_name@OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `ENGINE_init@OPENSSL_1.0.0'
Re: [Dovecot] POLL: v2.2 to allow one mail over quota?
On Mon, Oct 29, 2012 at 10:39:51PM +0200, Timo Sirainen wrote: Currently if user is 1MB under quota and someone tries to deliver mail that is over 1MB, Dovecot rejects the mail. But smaller mails aren't rejected probably for days. So user might not even realize that they didn't receive one of the mails. Also having a user almost over quota is a rather strange state I think. So what do you think about v2.2 allowing delivery of one last mail even if it brings the user over quota? Except add a limit that if the message size is as much as the user's entire quota limit it wouldn't be added (or 50% or ..?). Also IMAP wouldn't allow this, since user would get an error anyway. I could make this also optional, but if nobody really wants to keep the old behavior there's really no point in adding the option. I think the thing to do is to adjust the admin's thinking about it. Yes, if the current mailstore is under quota, by all means, you should accept the next email up to the maximum size the server accepts. No exception, just take it. You control $quota and $maxMsg. Set your quota with that in mind, where $(($quota - 1 + $maxMsg)) total is something you can live with. That said, I have been fortunate to never have to set up a quota. Storage is cheap. An occasional cron job can point out individual users who might be beyond what you'd consider reasonable, and to those users, apply a LART. -- http://rob0.nodns4.us/ -- system administration and consulting Offlist GMX mail is seen only if /dev/rob0 is in the Subject:
Re: [Dovecot] POP3 Proxy : user format not accepted
Indeed, I set its value to empty to allow all characters and it now works. Thanks a lot Timo. De : Timo Sirainen t...@iki.fi À : Christian Gregoire cgregoi...@yahoo.com; Dovecot Mailing List dovecot@dovecot.org Envoyé le : Mardi 30 octobre 2012 14h08 Objet : Re: [Dovecot] POP3 Proxy : user format not accepted On 30.10.2012, at 14.01, Christian Gregoire wrote: Any idea ? Is the '#' not internally supported in the user login by Dovecot ? See auth_username_chars setting.
Re: [Dovecot] Pigeonhole 3.3 broken against Dovecot 2.1.10
On 10/30/2012 4:00 PM, Daniel L. Miller wrote: I'm compiling as I normally do. The config line for Dovecot is: configure --with-ldap --with-ssl --with-bzlib --with-zlib --with-stemmer --with-lucene --with-ldap followed by make make install Then a 'configure' for Pigeonhole, followed by make, yields: What kind of system are you compiling this on? Regards, Stephan.
[Dovecot] Unable to get Managesieve working
I have Roundcube webmail (v. 0.8.2) running with the managesieve plugin (v. 5.1). I am able to create sieve rules without any problems in Roundcube, but incoming mail is not being processed with the rule I specify. I suspect there is something that isn't configured correctly in dovecot, but unfortunately I am unable to find a resolution online and my very limited knowledge of dovecot isn't allowing me to solve this problem on my own. I am including my dovecot config below. Please keep my knowledge level in mind when suggesting options and let me know if there is any other information I can provide to help troubleshoot the problem. Thanks for any assistance! # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.6 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps managesieve ssl_cert_file: /etc/ssl/certs/postfix.pem ssl_key_file: /etc/ssl/private/postfix.key ssl_cipher_list: ALL:!LOW:!SSLv2 login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login mail_privileged_group: mail mail_location: maildir:~/mail:LAYOUT=fs:INBOX=~/mail/ mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve auth default: mechanisms: plain login passdb: driver: pam passdb: driver: pam userdb: driver: passwd userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix plugin: sieve: ~/.dovecot.sieve sieve_dir: ~/mail/sieve
Re: [Dovecot] Unable to get Managesieve working
Hi Cliff,
Cliff Dunn wrote:
I have Roundcube webmail (v. 0.8.2) running with the managesieve
plugin (v. 5.1). I am able to create sieve rules without any
problems in Roundcube, but incoming mail is not being processed with
the rule I specify.
managesieve is the service for managing your sieve rules,
it does not process any emails.
In order to actually sort mails into folders, you need to add
the sieve plugin to your mail_plugins list.
http://wiki.dovecot.org/LDA/Sieve/Dovecot
protocol lda {
..
# Support for dynamically loadable plugins. mail_plugins is a space separated
# list of plugins to load.
mail_plugins = sieve # ... other plugins like quota
}
Regards
Daniel
--
https://plus.google.com/103021802792276734820
[Dovecot] lmtp out of memory - raw backtrace
Hi,
Our setup:
- 4 hosts with director and mailbox instance
- delivery via director lmtp into mailbox lmtp
- mailbox format: mdbox
- storage on NFS
- OS: Linux 2.6.32-44-server x86_64 Ubuntu 10.04.4 LTS
- Dovecot 2.1.10
- Pigeonhole 0.3.3
We're getting strange out of memory lmtp errors/backtrace with dovecot 2.1.10
accompanied by high load caused caused by a lot of lmtp deliveries to one user.
First action would be to increase vsz_limit to a higher value, but I just
want to make sure there is no bug - before blindly increasing this limit.
I think it should not crash and corrupt mdbox, even if memory limit is reached:
Oct 29 20:14:56 10.129.3.249 dovecot: lmtp(26698, us...@example.org): Fatal:
pool_system_realloc(16777216): Out of memory
Oct 29 20:14:56 10.129.3.249 dovecot: lmtp(26698, us...@example.org): Error:
Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x4271a) [0x7f6dcbae971a] -
/usr/lib/dovecot/libdovecot.so.0(+0x42766) [0x7f6dcbae
9766] - /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f6dcbabd158] -
/usr/lib/dovecot/libdovecot.so.0(+0x53690) [0x7f6dcbafa690] -
/usr/lib/dovecot/libdovecot.so.0(+0x3e6f5) [0x7f6dcbae56f5] - /usr/lib/dove
cot/libdovecot.so.0(buffer_write+0x7c) [0x7f6dcbae5e7c] -
/usr/lib/dovecot/libdovecot-storage.so.0(+0xa8033) [0x7f6dcbdda033] -
/usr/lib/dovecot/libdovecot-storage.so.0(mail_index_record_map_move_to_private+0x3
c) [0x7f6dcbdda4ec] -
/usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_get_atomic_map+0x18)
[0x7f6dcbde9c88] - /usr/lib/dovecot/libdovecot-storage.so.0(+0xb7cf9)
[0x7f6dcbde9cf9] - /usr/lib/dovecot/lib
dovecot-storage.so.0(mail_index_sync_record+0x7e6) [0x7f6dcbdea626] -
/usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x23c)
[0x7f6dcbdeae4c] - /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_m
ap+0xa8) [0x7f6dcbddc2b8] - /usr/lib/dovecot/libdovecot-storage.so.0(+0xb42da)
[0x7f6dcbde62da] - /usr/lib/dovecot/libdovecot-storage.so.0(+0xb458a)
[0x7f6dcbde658a] - /usr/lib/dovecot/libdovecot-storage.so.0(
mail_index_sync_begin_to+0x4f) [0x7f6dcbde6ecf] -
/usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_begin+0x1e)
[0x7f6dcbde6f4e] -
/usr/lib/dovecot/libdovecot-storage.so.0(mdbox_map_atomic_lock+0x5e) [0x
7f6dcbd6115e] -
/usr/lib/dovecot/libdovecot-storage.so.0(mdbox_transaction_save_commit_pre+0x46)
[0x7f6dcbd64fb6] - /usr/lib/dovecot/libdovecot-storage.so.0(+0x9d4f3)
[0x7f6dcbdcf4f3] - /usr/lib/dovecot/libdov
ecot-storage.so.0(mail_index_transaction_commit_full+0x9f) [0x7f6dcbddd97f] -
/usr/lib/dovecot/libdovecot-storage.so.0(index_transaction_commit+0x8a)
[0x7f6dcbdcf18a] - /usr/lib/dovecot/modules/lib10_quota_plug
in.so(+0xba7f) [0x7f6dca4eca7f] -
/usr/lib/dovecot/libdovecot-storage.so.0(mailbox_transaction_commit_get_changes+0x3d)
[0x7f6d
Oct 29 20:14:56 10.129.3.249 dovecot: lmtp(26698, us...@example.org): Fatal:
master: service(lmtp): child 26698 returned error 83 (Out of memory (service
lmtp { vsz_limit=256 MB }, you may need to increase it))
Oct 30 01:15:49 10.129.3.249 dovecot: lmtp(17927, us...@example.org): Error:
mmap_anon(216690688) failed: Cannot allocate memory
Oct 30 01:15:49 10.129.3.249 dovecot: lmtp(17927, us...@example.org): Error:
mmap_anon(216690688) failed: Cannot allocate memory
Oct 30 10:32:27 10.129.3.249 dovecot: mailbox: mail: imap(us...@example.org):
nURUbUPNBgAKgQPI: Error: Corrupted dbox file
/mail/dovecot/example.org/user1/mail/storage/m.3577 (around offset=1844402):
EOF reading msg header (got 0/30 bytes)
Oct 30 10:33:44 10.129.3.249 dovecot: mailbox: mail: imap(us...@example.org):
ZZ0pYkPN+wAKgQPp: Error:
/mail/dovecot/example.org/user1/mail/mailboxes/Lists/Cron/dbox-Mails/dovecot.index
reset, view is now inconsistent
Oct 30 10:33:44 10.129.3.249 dovecot: mailbox: mail: imap(us...@example.org):
CcYCYkPNkAAKgQPV: Error:
/mail/dovecot/example.org/user1/mail/mailboxes/Lists/postfix/dbox-Mails/dovecot.index
reset, view is now inconsistent
Oct 30 10:33:44 10.129.3.249 dovecot: mailbox: mail: imap(us...@example.org):
t+gLYkPNVQAKgQPV: Error:
/mail/dovecot/example.org/user1/mail/mailboxes/Lists/Dovecot/dbox-Mails/dovecot.index
reset, view is now inconsistent
Oct 30 10:33:46 10.129.3.249 dovecot: mailbox: mail: imap(us...@example.org):
YElVbUPNKwAKgQO/: Error:
/mail/dovecot/example.org/user1/mail/mailboxes/INBOX/dbox-Mails/dovecot.index
reset, view is now inconsistent
Oct 30 10:36:16 10.129.3.249 dovecot: lmtp(21404, us...@example.org): Error:
Timeout (180s) while waiting for lock for transaction log file
/mail/dovecot/example.org/user1/mail/storage/dovecot.map.index.log
Oct 30 10:36:16 10.129.3.249 dovecot: lmtp(21405, us...@example.org): Error:
Timeout (180s) while waiting for lock for transaction log file
/mail/dovecot/example.org/user1/mail/storage/dovecot.map.index.log
Oct 30 10:36:16 10.129.3.249 dovecot: lmtp(21410, us...@example.org): Error:
Timeout (180s) while waiting for lock for transaction log file
Re: [Dovecot] Unable to get Managesieve working
Ok, so when I add the mail_plugins = sieve I get:
sudo service dovecot restart
Restarting IMAP/POP3 mail server: dovecotFPlugin sieve not found from
directory /usr/lib/dovecot/modules/imap
Error: imap dump-capability process returned 89
Fatal: Invalid configuration in /etc/dovecot/dovecot.conf
failed
I am assuming something is missing here?
On 2012-10-30 19:37, Daniel Parthey wrote:
Hi Cliff,
Cliff Dunn wrote:
I have Roundcube webmail (v. 0.8.2) running with the managesieve
plugin (v. 5.1). I am able to create sieve rules without any
problems in Roundcube, but incoming mail is not being processed with
the rule I specify.
managesieve is the service for managing your sieve rules,
it does not process any emails.
In order to actually sort mails into folders, you need to add
the sieve plugin to your mail_plugins list.
http://wiki.dovecot.org/LDA/Sieve/Dovecot
protocol lda {
..
# Support for dynamically loadable plugins. mail_plugins is a space
separated
# list of plugins to load.
mail_plugins = sieve # ... other plugins like quota
}
Regards
Daniel
Re: [Dovecot] lmtp out of memory - raw backtrace
On 31.10.2012, at 2.09, Daniel Parthey wrote: - Dovecot 2.1.10 - Pigeonhole 0.3.3 We're getting strange out of memory lmtp errors/backtrace with dovecot 2.1.10 accompanied by high load caused caused by a lot of lmtp deliveries to one user. First action would be to increase vsz_limit to a higher value, but I just want to make sure there is no bug - before blindly increasing this limit. Recent changes in hg should help with this for LMTP. I'll probably release 2.1.11 somewhat soon. I think it should not crash and corrupt mdbox, even if memory limit is reached: It should crash, because it reached the enforced vsz limit. If you don't want it to crash you can disable the limit, at the cost of potentially eating all of your memory. Oct 30 10:32:27 10.129.3.249 dovecot: mailbox: mail: imap(us...@example.org): nURUbUPNBgAKgQPI: Error: Corrupted dbox file /mail/dovecot/example.org/user1/mail/storage/m.3577 (around offset=1844402): EOF reading msg header (got 0/30 bytes) This does look like something that should be fixed. It's not exactly a corruption so much as finding a partially written mail during rescan (because of the crash), but still it can probably be avoided.
Re: [Dovecot] Unable to get Managesieve working
Cliff Dunn wrote:
In order to actually sort mails into folders, you need to add
the sieve plugin to your mail_plugins list.
http://wiki.dovecot.org/LDA/Sieve/Dovecot
protocol lda {
mail_plugins = sieve
}
Ok, so when I add the mail_plugins = sieve I get:
sudo service dovecot restart
Restarting IMAP/POP3 mail server: dovecotFPlugin sieve not found
from directory /usr/lib/dovecot/modules/imap
Error: imap dump-capability process returned 89
Fatal: Invalid configuration in /etc/dovecot/dovecot.conf
failed
I am assuming something is missing here?
I guess you are missing the sieve plugin completely,
did you install the dovecot-sieve plugin?
Where did you get sieve from and how did you install it?
Did you follow all the compile instructions at
http://wiki.dovecot.org/LDA/Sieve/Dovecot or
did you install some package?
What do the following commands say?
# find /usr/lib/dovecot | grep sieve
# apt-cache policy dovecot-sieve
# dpkg -l dovecot*
Regards
Daniel
--
https://plus.google.com/103021802792276734820
Re: [Dovecot] Pigeonhole 3.3 broken against Dovecot 2.1.10
On 30.10.2012 14:46, Stephan Bosch wrote: On 10/30/2012 4:00 PM, Daniel L. Miller wrote: I'm compiling as I normally do. The config line for Dovecot is: configure --with-ldap --with-ssl --with-bzlib --with-zlib --with-stemmer --with-lucene --with-ldap followed by make make install Then a 'configure' for Pigeonhole, followed by make, yields: What kind of system are you compiling this on? AMD Opteron 4180, Ubuntu Precision, Linux 3.2.0-25, 64-bit. libssl-dev 1.0.1c-3ubuntu1 libc6 2.15 gcc 4.6.3 -- Daniel
[Dovecot] maildir S= and W=
Hi. Even new mails delivered by my MDA don't get the ,S= and ,W= fields set... (but when I upload a mail via IMAP to dovecot, they are set) Is there some place in dovecot where I need to enable this? Or would it be the MDA that has to calculate and set this already when placing a file in ./new? Thanks, Chris. smime.p7s Description: S/MIME cryptographic signature
[Dovecot] maildir and end-of-line encoding
Hi. I just wondered, the following: My MDA may get mails that use LF or CR/LF end of line encodings and deliver them into maildirs. I couldn't find any information about, whether one should or must convert all into one format, cause AFAIK at least on the IMAP side, CR/LF is always used? How does this work on the maildir/backend side of dovcot? Can it work with both and simply automatically convert LF into CR/LF? Thanks, Chris. smime.p7s Description: S/MIME cryptographic signature
