[Dovecot] Store sent email
Hello all, I've set up a webmail solution based on RedHat EL 5, sendmail, spamassassin, clamAV and dovecot by following this tutorial: http://www.redhat.com/magazine/025nov06/features/email/index.html I have configured everything without any problem, I can send and receive emails, using Maildir store format. Now, what I don't know how to set up: I would like to store the emails sent by the users in a dedicated store (Like Sent Emails in many webmails) and I've got no idea on how to do this! By googling a little, I found this thread ( http://www.dovecot.org/list/dovecot/2007-April/021447.html) where a plugin is mentionned. Has it been developped or is there another solution? I'm using dovecot 1.0.7, shipped with RHEL 5 distribution. I am really discovering all the products around the email so I'm a bit confused. Thanks a lot for your answer, Pierre
[Dovecot] Unknown dict module: db with expire plugin
Hello. I use dovecot 1.1.8 in a FreeBSD 6.3 Today, I want to active expire plugin. But it does not work. I made instructions described in http://wiki.dovecot.org/Plugins/Expire for a bdb database. See my dovecot -n: # 1.1.8: /usr/local/etc/dovecot.conf # OS: FreeBSD 6.3-RELEASE-p4 i386 ufs syslog_facility: local6 ssl_cert_file: /etc/ssl/mail/***.cert ssl_key_file: /etc/ssl/mail/.key disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_user: dovecot-auth login_greeting: ** login_processes_count: 2 verbose_proctitle: yes first_valid_uid: 143 last_valid_uid: 143 first_valid_gid: 143 last_valid_gid: 143 mail_access_groups: mail mail_location: maildir:/var/mail/vmail/%u/ mail_plugins: quota imap_quota mail_log expire imap_client_workarounds: delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep auth default: mechanisms: plain login passdb: driver: sql args: /usr/local/etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /usr/local/etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix master: path: /var/run/dovecot/auth-master mode: 432 user: dovecot group: mail plugin: quota: maildir quota_rule: *:storage=1000M quota_rule2: Trash:storage=50M quota_warning: storage=80%% /usr/home/scripts/mail_quota-warning.sh 80 quota_warning2: storage=90%% /usr/home/scripts/mail_quota-warning.sh 90 quota_warning3: storage=95%% /usr/home/scripts/mail_quota-warning.sh 95 sieve: /var/mail/vmail/%u/sieve expire: Trash 7 Trash/* 7 Junk 2 expire_dict: proxy::expire dict: expire: db:/var/lib/dovecot/expire.db The /var/lib/dovecot/expire.db file is not automatically created. So I created it, with root rights. After, the file is always to 0 bytes. When I want to dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool --test I have this: Error: read(/var/run/dovecot/dict-server) failed: Remote disconnected And in my logs: Jan 28 09:24:36 dovecot: dict: Unknown dict module: db Jan 28 09:24:36 dovecot: dict: Failed to initialize dictionary 'expire' I do not understand the problem. I made instructions on the wiki page. Is anybody could help me to resolve this? Thanks. Regards, (ps : another question : what's the advantage of expire plugin with a manual cron job?) -- -Nicolas.
Re: [Dovecot] managesieve proxy cyrus
Does Squirrelmail try to use STARTTLS? Having full session traffic logs I don't think Squirrelmail is trying to use STARTTLS. But anyway I've tried to trace the sieve connection protocol, you could find it in the attachement. It's approximatively the same data, I've posted yesterday with extra protocol tcp/ip :) of when Squirrelmail is logging into Dovecot proxy and when logging into Cyrus proxy would be helpful (ngrep, wireshark, etc). If Squirrelmail uses STARTTLS, this doesn't really work though (but at least the logs will reveal that it is doing STARTTLS). Also if it is doing that, perhaps the issue is SASL PLAIN after all, since Dovecot proxy won't do STARTTLS to the Cyrus. Also if you set auth_debug=yes, what do you see in Dovecot logs when attempting to log in? Here is my dovecot log with auth_debug=yes : Jan 28 09:31:24 myservername dovecot: auth(default): client in: AUTH 3 PLAIN service=managesieve secured lip=127.0.0.1 rip=127.0.0.1 lport=2000 rport=42791 resp=hidden Jan 28 09:31:24 myservername dovecot: auth-worker(default): sql(imap2,127.0.0.1): query: SELECT NULL AS password, host, destuser, 'Y' as nopassword, 'Y' AS proxy FROM proxy WHERE user = 'imap2' Jan 28 09:31:24 myservername dovecot: auth(default): client out: OK3 user=imap2 host=138.138.138.138 destuser=imap2 proxy pass=hidden Jan 28 09:31:24 myservername dovecot: managesieve-login: Disconnected: user=imap2, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Jan 28 09:31:24 myservername dovecot: auth(default): new auth connection: pid=4760 Frame 1 (74 bytes on wire, 74 bytes captured) Arrival Time: Jan 28, 2009 09:31:24.796988000 Time delta from previous packet: 0.0 seconds Time since reference or first frame: 0.0 seconds Frame Number: 1 Packet Length: 74 bytes Capture Length: 74 bytes Protocols in frame: eth:ip:tcp Ethernet II, Src: Xensourc_1f:1f:1f (1f:1f:1f:1f:1f:1f), Dst: Dell_1e:1e:1e (1e:1e:1e:1e:1e:1e) Destination: Dell_1e:1e:1e (1e:1e:1e:1e:1e:1e) Address: Dell_1e:1e:1e (1e:1e:1e:1e:1e:1e) ...0 = Multicast: This is a UNICAST frame ..0. = Locally Administrated Address: This is a FACTORY DEFAULT address Source: Xensourc_1f:1f:1f (1f:1f:1f:1f:1f:1f) Address: Xensourc_1f:1f:1f (1f:1f:1f:1f:1f:1f) ...0 = Multicast: This is a UNICAST frame ..0. = Locally Administrated Address: This is a FACTORY DEFAULT address Type: IP (0x0800) Internet Protocol, Src: IP_proxy_dovecot (IP_proxy_dovecot), Dst: Ip_cyrus_server (Ip_cyrus_server) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00) 00.. = Differentiated Services Codepoint: Default (0x00) ..0. = ECN-Capable Transport (ECT): 0 ...0 = ECN-CE: 0 Total Length: 60 Identification: 0x7d21 (32033) Flags: 0x04 (Don't Fragment) 0... = Reserved bit: Not set .1.. = Don't fragment: Set ..0. = More fragments: Not set Fragment offset: 0 Time to live: 64 Protocol: TCP (0x06) Header checksum: 0xa5f8 [correct] Good: True Bad : False Source: IP_proxy_dovecot (IP_proxy_dovecot) Destination: Ip_cyrus_server (Ip_cyrus_server) Transmission Control Protocol, Src Port: 53996 (53996), Dst Port: sieve (2000), Seq: 0, Len: 0 Source port: 53996 (53996) Destination port: sieve (2000) Sequence number: 0(relative sequence number) Header length: 40 bytes Flags: 0x0002 (SYN) 0... = Congestion Window Reduced (CWR): Not set .0.. = ECN-Echo: Not set ..0. = Urgent: Not set ...0 = Acknowledgment: Not set 0... = Push: Not set .0.. = Reset: Not set ..1. = Syn: Set ...0 = Fin: Not set Window size: 5840 Checksum: 0x384f [correct] Options: (20 bytes) Maximum segment size: 1460 bytes SACK permitted Time stamp: tsval 1185633227, tsecr 0 NOP Window scale: 4 (multiply by 16) Frame 2 (74 bytes on wire, 74 bytes captured) Arrival Time: Jan 28, 2009 09:31:24.797024000 Time delta from previous packet: 0.36000 seconds Time since reference or first frame: 0.36000 seconds Frame Number: 2 Packet Length: 74 bytes Capture Length: 74 bytes Protocols in frame: eth:ip:tcp Ethernet II, Src: Dell_1e:1e:1e (1e:1e:1e:1e:1e:1e), Dst: Xensourc_1f:1f:1f (1f:1f:1f:1f:1f:1f) Destination: Xensourc_1f:1f:1f (1f:1f:1f:1f:1f:1f) Address: Xensourc_1f:1f:1f (1f:1f:1f:1f:1f:1f) ...0 = Multicast: This is a UNICAST frame ..0. = Locally Administrated Address: This is a FACTORY DEFAULT address Source: Dell_1e:1e:1e
Re: [Dovecot] deliver and qmail
On Mon, 26 Jan 2009, Tim Traver wrote: ok, after looking at all of the posts that I've found, and trying numerous settings, I am a little stumped as to how to set up the deliver program with qmail to get everything correct. qmail is way obsolete and buggy. http://mandree.home.pages.de/qmail-bugs.html I've migrated away to Postfix ages before Postfix 1.0 was released and never rued that change a split second... Ultimately, I really don't want to do a lookup of the home dir if I don't have to. I'd rather specify the stuff in the .qmail-user file for that particular user to avoid the extra step. ...are home directory lookups so very expensive on your system? Hard to believe. I always found that qmail's (and qmail-send's) queue spooling behaviour was what really hurted, with a dozen (or so) synchronous writes for just spooling the message into the queue... -- Matthias Andree
Re: [Dovecot] Unknown dict module: db with expire plugin
Hi, Nicolas Letellier schrieb: And in my logs: Jan 28 09:24:36 dovecot: dict: Unknown dict module: db Jan 28 09:24:36 dovecot: dict: Failed to initialize dictionary 'expire' I do not understand the problem. I made instructions on the wiki page. Is anybody could help me to resolve this? Looks like your dovecot was compiled without the --with-db option. Michael
Re: [Dovecot] deliver and qmail
On Tue, 27 Jan 2009, Timo Sirainen wrote: I may be able to create a shell script that set the env variable and then launched deliver, but that's another fork that I'd rather not have, and since I already know the home dir when I set up the .qmail-user file, I'd rather just set it... A shell script doesn't have to fork deliver, just exec it. Even if the shell forks before the exec, that time is nothing compared to the many synchronous writes that qmail does. Even on a 233 MHz Pentium II computer with a reasonable operating system (any halfway recent BSD, or Linux, or Solaris), an extra fork has never hurt me (not even when such a machines were used as mail, web, samba, ftp server and 100 Mbit/s firewall at the same time). Typical shells will try to use lighter-weight vfork() anyways -- only that most operating systems should implement copy-on-write strategies underneath fork() and can then map vfork() on top of fork() because it really makes no noticable difference any more. -- Matthias Andree
Re: [Dovecot] discrete passdb lookups for dovecot-auth
On Jan 27, 2009, at 13.21, Timo Sirainen wrote: On Tue, 2009-01-27 at 11:54 -0500, benjamin thielsen wrote: hi- i'm using ldap for user authentication, and would like to use different ldap lookups for authentication happening via postfix (smtp auth) vs. authentication happening through dovecot (imap logins). how can this be done, without running multiple instances? Unfortunately currently you can't. The best you can do is to use %s in the ldap filters or base, but that probably won't be enough for you. thanks for the confirmation. has this been considered? in my particular case, we have users who can receive and retrieve mail, but not send mail, defined by the groups they belong to in our directory tree. would the ability to define discrete lookups (based on the service? - maybe other criteria as well?) also be useful in other scenarios? regards -ben
Re: [Dovecot] deliver and qmail
On Jan 28, 2009, at 2:56 AM, Matthias Andree wrote: On Mon, 26 Jan 2009, Tim Traver wrote: ok, after looking at all of the posts that I've found, and trying numerous settings, I am a little stumped as to how to set up the deliver program with qmail to get everything correct. qmail is way obsolete and buggy. http://mandree.home.pages.de/qmail-bugs.html Yes, in it's default form. Hence netqmail. I've migrated away to Postfix ages before Postfix 1.0 was released and never rued that change a split second... and I suppose you've never upgraded it - right? :P Ultimately, I really don't want to do a lookup of the home dir if I don't have to. I'd rather specify the stuff in the .qmail-user file for that particular user to avoid the extra step. ...are home directory lookups so very expensive on your system? Hard to believe. I always found that qmail's (and qmail-send's) queue spooling behaviour was what really hurted, with a dozen (or so) synchronous writes for just spooling the message into the queue... The bigger problem, other than a minor hardware/filesystem upgrade, is does deliver obey .qmail files in the user's home directory? It doesn't seem like it. Please correct me if I'm wrong, because if it doesn't, you'll need to modify at least how user's vacations and forwards are done. Rick
Re: [Dovecot] managesieve proxy cyrus
I've found this in the cyrus log file : Jan 28 13:19:18 cyrus_server sieve[10793]: login: proxy_dovecot[138.138.138.138] imap2 PLAIN User logged in When I test with sivtest -a myuser I can connect with PLAIN mechanism. If I replay with a telnet cyrus_server 2000 exactly what avelsieve send to a dovecot server I got this : telnet cyrus_server sieve Trying 138.138.138.138... Connected to cyrus_server.inria.fr (138.138.138.138). Escape character is '^]'. IMPLEMENTATION Cyrus timsieved v2.2.12 SASL PLAIN SIEVE fileinto reject envelope vacation imapflags notify subaddress relational comparator-i;ascii-numeric regex STARTTLS OK AUTHENTICATE PLAIN AGltYXAyAGltYXAy OK CAPABILITY IMPLEMENTATION Cyrus timsieved v2.2.12 SIEVE fileinto reject envelope vacation imapflags notify subaddress relational comparator-i;ascii-numeric regex OK It's like avelsieve just stop the connection by itself because once the user is logged, there is no other command send ! I don't understand why avelsieve tell me : unable to connect to server IMAP. localhost. I've done some others tests : - sivtest to a dovecot sieve server it's working. - telnet cyrus_server 2000 : it's working too - directly telnet dovecot 2000 : it's working too - telnet dovecot_proxy 2000 : it's not working ! (complain with NO Authentication failed.) It seems like the problem comes from dovecot in proxy mode ?? (only to connect to a cyrus sieve server, because it's working well with a dovecot sieve server) Mathieu Kretchner wrote: Does Squirrelmail try to use STARTTLS? Having full session traffic logs I don't think Squirrelmail is trying to use STARTTLS. But anyway I've tried to trace the sieve connection protocol, you could find it in the attachement. It's approximatively the same data, I've posted yesterday with extra protocol tcp/ip :) of when Squirrelmail is logging into Dovecot proxy and when logging into Cyrus proxy would be helpful (ngrep, wireshark, etc). If Squirrelmail uses STARTTLS, this doesn't really work though (but at least the logs will reveal that it is doing STARTTLS). Also if it is doing that, perhaps the issue is SASL PLAIN after all, since Dovecot proxy won't do STARTTLS to the Cyrus. Also if you set auth_debug=yes, what do you see in Dovecot logs when attempting to log in? Here is my dovecot log with auth_debug=yes : Jan 28 09:31:24 myservername dovecot: auth(default): client in: AUTH 3 PLAIN service=managesieve secured lip=127.0.0.1 rip=127.0.0.1 lport=2000 rport=42791 resp=hidden Jan 28 09:31:24 myservername dovecot: auth-worker(default): sql(imap2,127.0.0.1): query: SELECT NULL AS password, host, destuser, 'Y' as nopassword, 'Y' AS proxy FROM proxy WHERE user = 'imap2' Jan 28 09:31:24 myservername dovecot: auth(default): client out: OK3 user=imap2 host=138.138.138.138 destuser=imap2 proxy pass=hidden Jan 28 09:31:24 myservername dovecot: managesieve-login: Disconnected: user=imap2, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Jan 28 09:31:24 myservername dovecot: auth(default): new auth connection: pid=4760 begin:vcard fn:Mathieu Kretchner n:Kretchner;Mathieu org:INRIA;Syslog adr;dom:;;2004 route des lucioles - BP93;Sophia Antipolis;;06902 CEDEX email;internet:mathieu.kretch...@sophia.inria.fr tel;work:04 92 38 76 67 x-mozilla-html:FALSE version:2.1 end:vcard
Re: [Dovecot] deliver and qmail
Rick Romero schrieb: On Jan 28, 2009, at 2:56 AM, Matthias Andree wrote: On Mon, 26 Jan 2009, Tim Traver wrote: ok, after looking at all of the posts that I've found, and trying numerous settings, I am a little stumped as to how to set up the deliver program with qmail to get everything correct. qmail is way obsolete and buggy. http://mandree.home.pages.de/qmail-bugs.html Yes, in it's default form. Hence netqmail. So? netqmail fixes only a minority of qmail's bugs, but not the ones that require touching qmail's concepts - and I don't even make an attempt to update my bug list, since I find netqmail's change list too terse. I've migrated away to Postfix ages before Postfix 1.0 was released and never rued that change a split second... and I suppose you've never upgraded it - right? :P Nah. Of course I upgraded Postfix - but I have yet to see another piece of software where upgrades go so smoothly. The bigger problem, other than a minor hardware/filesystem upgrade, is does deliver obey .qmail files in the user's home directory? Dovecot's deliver certainly doesn't. It doesn't seem like it. Please correct me if I'm wrong, because if it doesn't, you'll need to modify at least how user's vacations and forwards are done. -- Matthias Andree
Re: [Dovecot] Store sent email
Hello, normaly the first time you'll send an e-mail like with a thunderbird client. The client will create a directory .Sent and store the mail inside. Try it! pierre.casen...@almerys.com wrote: Hello all, I've set up a webmail solution based on RedHat EL 5, sendmail, spamassassin, clamAV and dovecot by following this tutorial: http://www.redhat.com/magazine/025nov06/features/email/index.html I have configured everything without any problem, I can send and receive emails, using Maildir store format. Now, what I don't know how to set up: I would like to store the emails sent by the users in a dedicated store (Like Sent Emails in many webmails) and I've got no idea on how to do this! By googling a little, I found this thread ( http://www.dovecot.org/list/dovecot/2007-April/021447.html) where a plugin is mentionned. Has it been developped or is there another solution? I'm using dovecot 1.0.7, shipped with RHEL 5 distribution. I am really discovering all the products around the email so I'm a bit confused. Thanks a lot for your answer, Pierre begin:vcard fn:Mathieu Kretchner n:Kretchner;Mathieu org:INRIA;Syslog adr;dom:;;2004 route des lucioles - BP93;Sophia Antipolis;;06902 CEDEX email;internet:mathieu.kretch...@sophia.inria.fr tel;work:04 92 38 76 67 x-mozilla-html:FALSE version:2.1 end:vcard
Re: [Dovecot] deliver and qmail
On Jan 28, 2009, at 8:23 AM, Matthias Andree wrote: Rick Romero schrieb: On Jan 28, 2009, at 2:56 AM, Matthias Andree wrote: On Mon, 26 Jan 2009, Tim Traver wrote: ok, after looking at all of the posts that I've found, and trying numerous settings, I am a little stumped as to how to set up the deliver program with qmail to get everything correct. qmail is way obsolete and buggy. http://mandree.home.pages.de/qmail-bugs.html Yes, in it's default form. Hence netqmail. So? netqmail fixes only a minority of qmail's bugs, but not the ones that require touching qmail's concepts - and I don't even make an attempt to update my bug list, since I find netqmail's change list too terse. Some of the 'problem' concepts are opinions. For example, I use qmail's unbundled sending to monitor mail throughput. (I run a free service) When the queue sizes shoot up, it's shut down and I remove the spammer. A bundled email to 150 users would still be 1 email, and that does me no good. The only place for Postfix would be a dumb relay for those providers that throttle connections (assuming that was a real issue for me). I've migrated away to Postfix ages before Postfix 1.0 was released and never rued that change a split second... and I suppose you've never upgraded it - right? :P Nah. Of course I upgraded Postfix - but I have yet to see another piece of software where upgrades go so smoothly. make setup check didn't seem to hard for me (even after my custom patches). And you've now said that software is updated to fix problems and add features. It's a crime to not specify AT LEAST what version of qmail you're complaining about. Or is it a bunch of different issues with different versions all crammed on one page? The first complaint acknowledges that it may no longer exist in 1.03 (released when?). If anyone really reads beyond that, I'd be surprised. The bigger problem, other than a minor hardware/filesystem upgrade, is does deliver obey .qmail files in the user's home directory? Dovecot's deliver certainly doesn't. So back to the original question: Then it's pretty much useless in a qmail environment unless the admin has already changed those features to require maildrop or procmail. If that has been done, then the directory lookup should already be done, and you can do deliver at the end of your maildrop or procmail script. Rick
Re: [Dovecot] dovecot 1.2 virtual folders question rules like RestrictAccess ?
Robert Schetterer schrieb:
Hi Timo
Timo Sirainen schrieb:
On Jan 26, 2009, at 7:45 PM, Robert Schetterer wrote:
is this possible a possible setup ?
for downloading imap folders ( including inbox )
with pop3 controlled by a a dovecot-virtual file
in usr/local/virtual/%d/%u/
Place that in to e.g.: /etc/dovecot/virtual/INBOX
Ahhh understand, done *g
namespace private {
prefix = virtual/
separator = /
location = virtual:/usr/local/virtual/%d/%u:LAYOUT=maildir++
inbox = no
}
For pop3 to use virtual mailbox you must use something like:
namespace private {
prefix = virtual/
separator = /
location = virtual:/etc/dovecot/virtual:INDEX=~/virtual
subscriptions = no
}
Ok done understand
namespace private {
separator = /
prefix =
location=maildir:/usr/local/virtual/%d/%u/:CONTROL=/usr/local/virtual/%d/%u/:INDEX=/usr/local/virtual/%d/%u/
inbox = yes
subscriptions = yes
list = yes
list = no here.
done
}
Then depending on if user is logging in with imap or pop3, set inbox=yes
to one of those namespaces. What userdb are you using? You'll anyway
need to return something like namespace_0_inbox=yes or ..1.._inbox=yes
i am not clear here, you mean i have to change inbox=yes
in namespace depend on pop3 or imap login?
so this means some split at login process by script etc?
like i.e.
http://wiki.dovecot.org/PostLoginScripting?highlight=(login)
i use sql backend, and have no fields relate to imap or
pop3
like this
driver = mysql
connect = host=localhost dbname=... user=... password=...
default_pass_scheme = PLAIN
password_query = \
SELECT password \
FROM mailbox WHERE username = '%u' AND active = '1'
user_query = SELECT concat('/usr/local/virtual/', maildir) AS home, \
concat('*:bytes=', mailbox.quota) AS quota_rule, \
#when saving to Trash mailbox the user gets additional 50MB
Trash:storage=50240 AS quota_rule2, \
#when saving to Sent mailbox the user gets additional 50MB
Sent:storage=50240 AS quota_rule3, \
#when saving to Drafts mailbox the user gets additional 50MB
Drafts:storage=50240 AS quota_rule4, \
#when saving to Templates mailbox the user gets additional 50MB
Templates:storage=50240 AS quota_rule5, \
#when saving to Junk mailbox the user gets additional 50MB
Junk:storage=50240 AS quota_rule6, \
#ignore quota on shared
#shared:ignore AS quota_rule7, \
concat('maildir:/usr/local/virtual/', maildir) AS mail, \
1001 AS uid, 1001 AS gid FROM mailbox WHERE username = '%u' AND active
= '1'
Hi Timo, after study
http://wiki.dovecot.org/Authentication/RestrictAccess
it should be possible
to include
namespace_0_inbox=yes or ..1.._inbox=yes
to a sql query
i.e ( sorry i am not good in sql so this is just a stupid non working
example to show what i mean )
password_query = \
SELECT password \
FROM mailbox WHERE username = '%u' AND active = '1' \
CASE '%Ls' = 'pop3' THEN namespace_1_inbox=yes
whats your meaning with this, would dovecot understand changing
inbox=yes depend by login type ( pop3/imap ) this way?
--
Best Regards
MfG Robert Schetterer
Germany/Munich/Bavaria
Re: [Dovecot] Store sent email
Hi, Thanks a lot... it is working! I'll give that answer to the development team ... Sorry for this silly question so ;) Pierre De : Mathieu Kretchner mathieu.kretch...@sophia.inria.fr A: pierre.casen...@almerys.com Cc : dovecot@dovecot.org Date: 28/01/2009 15:37 Objet : Re: [Dovecot] Store sent email Hello, normaly the first time you'll send an e-mail like with a thunderbird client. The client will create a directory .Sent and store the mail inside. Try it! pierre.casen...@almerys.com wrote: Hello all, I've set up a webmail solution based on RedHat EL 5, sendmail, spamassassin, clamAV and dovecot by following this tutorial: http://www.redhat.com/magazine/025nov06/features/email/index.html I have configured everything without any problem, I can send and receive emails, using Maildir store format. Now, what I don't know how to set up: I would like to store the emails sent by the users in a dedicated store (Like Sent Emails in many webmails) and I've got no idea on how to do this! By googling a little, I found this thread ( http://www.dovecot.org/list/dovecot/2007-April/021447.html) where a plugin is mentionned. Has it been developped or is there another solution? I'm using dovecot 1.0.7, shipped with RHEL 5 distribution. I am really discovering all the products around the email so I'm a bit confused. Thanks a lot for your answer, Pierre [pièce jointe mathieu_kretchner.vcf supprimée par Pierre CASENOVE/ALMERYS]
Re: [Dovecot] Old Thunderbird problem - need a fix
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 27 Jan 2009, Marc Perkel wrote: What Dovecot version do you use? Which mailbox format? When I empty my trash folder it doesn't empty. I get an indication that email has arrived in my inbox by the unread message count but can't access it. Messages arrive by appear to be empty. Folders that should be empty still have message counts showing. When you enable mail_debug, is there something in the logs? With all of the above problems - restarting dovecot make them all go away. Does it work if you just kill -HUP dovecot? Whatever the problem is I think that when I restart Dovecot I'm forcing Thunderbird to reconnect. Perhaps the solution is to somehow force Thunderbird to have to reconnect every time rather than have a persistent connection? Try to lower the number of simultaenous connections Thunderbird may use. This has the same effect, eventually. Is the mailbox pretty large? thousands of Mails or = 2GB in size? Thunderbird does not like those ones. We had an user with a similiar effect. It was a years-old profile (probably even converted from a Netscape 4 profile years back). When I re-created the profile, just copied the bookmarks file and re-imported the addressbooks, the problem was not seen again. How many users are working on your server? Bye. - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSYBx13WSIuGy1ktrAQLevAgAiddHAnbnS8A+iSvNTrCCYPMcGkbBqen1 nHZxdx7sGkwjAPSXdHTEfdkA1Q2B4y8wUW3puCHNZI7dDQMSztWkXyFUDBre5t1O MZbuZFws4nvkrYfUpkWXlB+wQ1tisrT6Cxjwp6DShtBRx1VMgf31RRqq5Z4mQcV/ 7+GZ2egg7keSY21TteNZRmdmt5sysgEjQdlRsFdph8/QqkLqZ1nNOEyLKYktdu2g 9GZ2rKaczd8OJR9K8URu8TOjPg0SKtIzavU9/fGjvOZUf8p6cT3Qj0diTgMDFoht FUrv7g1jGqAZu/CvW5AsNu9iSrYNc5oD9kE073wtJvM6BvbGZTd02g== =BKuw -END PGP SIGNATURE-
[Dovecot] Confused about permissions needed for shared mailbox
Hello, let me re-state, hopefully in clearer terms, what I tried to described in a previous thread : With dovecot-1.1.8/Maildir/LDAP pass/userdb (prefetch), I'm trying to set up a Maildir .box shared in rw between 2 users in a Public namespace. I can't get it to work unless I chmod 777 everything, which obiously is not what I want. 1) am I correct thinking that the system_user userdb extra_field and unix permissions should be enough to achieve that and that ACLs is only if I want to fine tunes mailbox permissions ? 2) let's say that my public namespace prefix is Public/, that the .box/ maildir is in /path/to/public/.box and my 2 users belong to the doveshared unix group. I thought it would be enough to have drwxrws--- 3 root doveshared 4096 Jan 28 14:55 public drwxrws--- 3 root doveshared 4096 Jan 28 14:55 public/.box -rwxrws--- 1 root doveshared 0 Jan 26 18:25 public/.box/dovecot-shared provided that my prefetch userdb returns system_user, as I think the following says in dovecot-ldap.conf : pass_attrs = uid=user,userPassword=password,homeDirectory=userdb_home,,,uidNumber=userdb_uid,gidNumber=userdb_gid,shadowMax=userdb_system_user and providedt that in LDAP shadowMax: 80 (whatever value). But this doesn't seem to work. By the way : Am I supposed to have a dovecot-shared file in public as well (that is not only in public/.box) ? 3) let's say I try ACLs with the same setup (anyone all permissions for starters) would pass_attrs = uid=user,userPassword=password,homeDirectory=userdb_home,,,uidNumber=userdb_uid,gidNumber=userdb_gid,shadowMax=userdb_system_user.title=userdb_acl_groups and title: group1,doveshared be a correct setup ? Do I need an dovecot-acl file only in .box or in public too ? My understanding is that my setup doesn't work because for some reason, dovecot doesn't see my users secondary groups or doesnt take them into account... Any thoughts which might help ? -- Thomas Hummel | Institut Pasteur hum...@pasteur.fr | Pôle informatique - systèmes et réseau
[Dovecot] Trash for lda
Hi, I was wondering if there is a solution to the case when the user can't recieve emails because of being over quota, something like http://wiki.dovecot.org/Plugins/Trash, but for the lda, not the imap? Thanks, - You can never find the chance to be the first to know about the newest movies showing in Arab theatres until you visit Maktoob Movies! http://www.maktoob.com/movies
Re: [Dovecot] Trash for lda
Words by Alaa Ibrahim [Wed, Jan 28, 2009 at 03:17:03PM +]: Hi, I was wondering if there is a solution to the case when the user can't recieve emails because of being over quota, something like http://wiki.dovecot.org/Plugins/Trash, but for the lda, not the imap? That would kind of defeat the purpose of quota I think. -- Jose Celestino | http://japc.uncovering.org/files/japc-pgpkey.asc One man’s theology is another man’s belly laugh. -- Robert A. Heinlein
Re: [Dovecot] (imap) killed with signal 9 on Linux/OpenVZ VPS
On Tue, 27 Jan 2009, Timo Sirainen wrote: On Tue, 2009-01-27 at 14:13 -0500, Adam Flott wrote: On Tue, 27 Jan 2009, Timo Sirainen wrote: On Mon, 2009-01-26 at 22:07 -0500, Adam Flott wrote: I'm trying to get dovecot running on my VPS and the main imap process is receiving a SIGKILL from what I presume to be the Linux Kernel and/or OpenVZ. This happens after I login and my client(s) just sit their idling. The mailbox is empty. See if it helps to set mail_process_size=0 Still no luck. Does dmesg show anything? If not, I've no idea. I switched to Xen and the problem seems to be solved. dovecot ran all night with a few clients connected. Therefore, looks like VPS Link + OpenVZ (2.6.18-ovz028stab039.1-smp) + dovecot (any version) is not an option.
Re: [Dovecot] (imap) killed with signal 9 on Linux/OpenVZ VPS
Adam Flott wrote: On Tue, 27 Jan 2009, Timo Sirainen wrote: On Tue, 2009-01-27 at 14:13 -0500, Adam Flott wrote: On Tue, 27 Jan 2009, Timo Sirainen wrote: On Mon, 2009-01-26 at 22:07 -0500, Adam Flott wrote: I'm trying to get dovecot running on my VPS and the main imap process is receiving a SIGKILL from what I presume to be the Linux Kernel and/or OpenVZ. This happens after I login and my client(s) just sit their idling. The mailbox is empty. See if it helps to set mail_process_size=0 Still no luck. Does dmesg show anything? If not, I've no idea. I switched to Xen and the problem seems to be solved. dovecot ran all night with a few clients connected. Therefore, looks like VPS Link + OpenVZ (2.6.18-ovz028stab039.1-smp) + dovecot (any version) is not an option. For what it's worth I'm running Dovecot under OpenVZ without problems. But I'm running a much newer kernel.
Re: [Dovecot] Unknown dict module: db with expire plugin
On Wed, 28 Jan 2009 09:56:47 +0100 Michael Lechtermann dove...@lechtermann.net wrote: Hi, Nicolas Letellier schrieb: And in my logs: Jan 28 09:24:36 dovecot: dict: Unknown dict module: db Jan 28 09:24:36 dovecot: dict: Failed to initialize dictionary 'expire' I do not understand the problem. I made instructions on the wiki page. Is anybody could help me to resolve this? Looks like your dovecot was compiled without the --with-db option. Michael Oh That's seem to be the solution! Thanks a lot! Regards, -- -Nicolas.
[Dovecot] Differences when expire plugin and cronjob?
Hello. I would like to see the differnces between the expire plugin and a cronjob which make a find/delete. Is there performances differences? What's the best to use? I use dovecot 1.1.8. Is expire plugin update the maildirsize and other indexes files? Thanks. Regards, -- -Nicolas.
[Dovecot] Killing Dovect, an unpleasant surprise
When it came time to upgrade DC or replace the certificate, I would find the root instance of dovecot and do a kill -7 of it. Within 20-30 seconds, all the hundreds of DC related processes would go away, I would swap the executable or certificate/key and restart DC. Very clean and quick. Surprise. After switching from 1.0.15 to 1.1.8 and doing the kill, I found that all the imap-login instances had been inherited by the root (1) process and did not go away. Yikes! An Unpleasant Surprise. So instead of being down for a minute, I was out for a much more noticeable 5-7 minutes, while I QUICK did an awk of the ps list to give me the pids and then xarg killed them. My boss asked me if this was a pink slip notice. :( Is this The Way Things Will Be? Is there a new way to kill everything DC related quickly and cleanly? -- Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sd...@bard.edu voice: 845-758-7475, fax: 845-758-7035 Resolve then, that on this very ground, with small flags waving and tinny blasts on tiny trumpets, we shall meet the enemy, and not only may he be ours, he may be us. === From the introduction to the original Pogo Papers
Re: [Dovecot] Symlink shared mailboxes and system_user extra field
On Tue, Jan 27, 2009 at 03:28:27PM +0100, Thomas Hummel wrote: Please, ignore this thread, I will sum up what I figure out in another one. -- Thomas Hummel | Institut Pasteur hum...@pasteur.fr | Pôle informatique - systèmes et réseau
Re: [Dovecot] Confused about permissions needed for shared mailbox
On Wed, Jan 28, 2009 at 04:06:20PM +0100, Thomas Hummel wrote: Please ignore this message, I will sum up what I did figure out in another thread. -- Thomas Hummel | Institut Pasteur hum...@pasteur.fr | Pôle informatique - systèmes et réseau
Re: [Dovecot] deliver and qmail
Rick Romero schrieb: Some of the 'problem' concepts are opinions. For example, I use qmail's unbundled sending to monitor mail throughput. (I run a free service) When the queue sizes shoot up, it's shut down and I remove the spammer. A bundled email to 150 users would still be 1 email, and that does me no good. The only place for Postfix would be a dumb relay for those providers that throttle connections (assuming that was a real issue for me). Unbundling mail just for accounting? Seems a rather wasteful approach to me. Other open-source MTAs I've looked at, including Sendmail, Exim, and Postfix, that transport mail bundled, emit sufficient log information to obtain the number of recipients. But that's a long way from the topic... It's a crime to not specify AT LEAST what version of qmail you're complaining about. Since that's a public complaint, I'll still respond to this paragraph: The version (qmail 1.03, netqmail 1.05) is up front, and has been from the beginning. Or is it a bunch of different issues with different versions all crammed on one page? The first complaint acknowledges that it may no longer exist in 1.03 (released when?). If anyone really reads beyond that, I'd be surprised. Irrelevant polemics, and if either you're overly susceptible to surprise or your imagination is so limited, such may not transfer to everybody else... The first complaint shows two examples, and I simply haven't checked if the second example works against 1.03 or only older 1997 versions, because it doesn't matter, the resource exhaustion vulnerability is there. I don't care much, if someone presents evidence to one side or the other, I'll update the page, but I'm not doing further research myself. The bigger problem, other than a minor hardware/filesystem upgrade, is does deliver obey .qmail files in the user's home directory? Dovecot's deliver certainly doesn't. So back to the original question: Then it's pretty much useless in a qmail environment unless the admin has already changed those features to require maildrop or procmail. If that has been done, then the directory lookup should already be done, and you can do deliver at the end of your maildrop or procmail script. It's probably possible to plug deliver late in the delivery process of qmail-local (i. e. as default delivery), but I forgot the details - let somebody else speak up who knows qmail better than your or me do off-hand; or better ask the qmail list (but be prepared for crusades on the list... BTST). As a pointer, check the various qmail examples on how procmail can be integrated into qmail and see if those can be adjusted for deliver. -- Matthias Andree
[Dovecot] Public namespace permissions documentation/questions
Hello Timo, In my trials to setup a shared namespace with dovecot-1.1.8/LDAP passdb/userdb (prefetch)/Maildir, I found out that : 1) ACL are mandatory (at least if the acl plugin is triggered in dovecot.conf) Am I correct ? I'm still not sure if we can do without ACL at all (only with unix permissions and system_user userdb extra field). 2) the system_user userdb extra field is supposed to be ...the logname of the user the secondary groups of whom we want to check ! i.e. if user foobar belongs to secondary groups foogid, zgid, wgid and doveshared uid=xxx(foobar) gid=yyy(foogid) groups=zzz(zgid),www(wgid),vvv(doveshared) and we dovecot to take them into account, we have to make the usedb return the system_user extra field with the value foobar. Seems obvious now and said this way, but looking at the wiki : system_user: If this is given, the user's groups are read from /etc/group (or wherever NSS is configured to taken them from). I thought 'system_user' was a flag (a boolean) which, when triggered made dovecot look for the secondaries group of the user (user whose name is already known). a) am I correct ? b) why isn't system_user such a boolean ? Is there a case where we'd want system_user to be different than the user dovecot runs as at the moment the check takes place ? 3) same idea with acl_groups : since this extra_field holds a list of groups for the ACL plugin, why not rely on the native unix groups of the system the user belong to ? Thanks (and sorry for the 2 previous threads where I was blindly confused by the system_user thing). -- Thomas Hummel | Institut Pasteur hum...@pasteur.fr | Pôle informatique - systèmes et réseau
Re: [Dovecot] deliver and qmail
On Jan 28, 2009, at 11:32 AM, Matthias Andree wrote: Rick Romero schrieb: Some of the 'problem' concepts are opinions. For example, I use qmail's unbundled sending to monitor mail throughput. (I run a free service) When the queue sizes shoot up, it's shut down and I remove the spammer. A bundled email to 150 users would still be 1 email, and that does me no good. The only place for Postfix would be a dumb relay for those providers that throttle connections (assuming that was a real issue for me). Unbundling mail just for accounting? Seems a rather wasteful approach to me. Other open-source MTAs I've looked at, including Sendmail, Exim, and Postfix, that transport mail bundled, emit sufficient log information to obtain the number of recipients. But that's a long way from the topic... It needs to be done 'in-process'. I suppose total concurrency could be retrieved by some sort of combination of gathering and multiplication, but logs also tend to be 'after the fact'. By 'lining up' multiple queues, with a delay, outgoing spam bursts can be caught quickly. So multiple SMTP transfers between internal systems could also be considered 'wasteful', but then, the people who received the spam that could have been stopped would disagree. It's a crime to not specify AT LEAST what version of qmail you're complaining about. Since that's a public complaint, I'll still respond to this paragraph: The version (qmail 1.03, netqmail 1.05) is up front, and has been from the beginning. Or is it a bunch of different issues with different versions all crammed on one page? The first complaint acknowledges that it may no longer exist in 1.03 (released when?). If anyone really reads beyond that, I'd be surprised. Irrelevant polemics, and if either you're overly susceptible to surprise or your imagination is so limited, such may not transfer to everybody else... The first complaint shows two examples, and I simply haven't checked if the second example works against 1.03 or only older 1997 versions, because it doesn't matter, the resource exhaustion vulnerability is there. I don't care much, if someone presents evidence to one side or the other, I'll update the page, but I'm not doing further research myself. You've listed two DIFFERENT versions, which may or may not include the noted patches. Which is the entire point - The page is just plain out of date. It's equivalent to me saying I don't run Windows and link to a page with Windows 98 issues. Will every Win98 issue be resolved in XP or Vista? I doubt it, but that doesn't really make the page any more relevant, and any issues listed that no longer exist are just plain misleading. Do I dare say the 3 letter F word? :) The bigger problem, other than a minor hardware/filesystem upgrade, is does deliver obey .qmail files in the user's home directory? Dovecot's deliver certainly doesn't. So back to the original question: Then it's pretty much useless in a qmail environment unless the admin has already changed those features to require maildrop or procmail. If that has been done, then the directory lookup should already be done, and you can do deliver at the end of your maildrop or procmail script. It's probably possible to plug deliver late in the delivery process of qmail-local (i. e. as default delivery), but I forgot the details - let somebody else speak up who knows qmail better than your or me do off-hand; or better ask the qmail list (but be prepared for crusades on the list... BTST). As a pointer, check the various qmail examples on how procmail can be integrated into qmail and see if those can be adjusted for deliver. or Sieve (which I should have added earlier) might be the better solution, since dovecot has the plugin. I use both maildrop and procmail with qmail/vpopmail. In my case, vdelivermail has to be replicated by dovecot deliver, OR I need to migrate the different ways I have of doing Spam scaning/real-time useage allocation/vacations/forwards to single system. Not a bad thing, and will happen eventually, but not something I personally have time for at the moment. Rick -- Matthias Andree
Re: [Dovecot] deliver and qmail
On 1/28/2009 1:04 PM, Rick Romero wrote: I use both maildrop and procmail with qmail/vpopmail. Ummm... this is the dovecot list, right?
Re: [Dovecot] deliver and qmail
On Jan 28, 2009, at 12:29 PM, Charles Marcus wrote: On 1/28/2009 1:04 PM, Rick Romero wrote: I use both maildrop and procmail with qmail/vpopmail. Ummm... this is the dovecot list, right? deliver would replace either qmail-local(I believe, I've never used it in that way) or vdelivermail - but to do so, it needs to either be a drop in replacement and do everything that those two programs did (quota is another we haven't brought up yet), or we have to do that processing somehow (via Sieve/maildrop/procmail) prior to calling deliver. OR - it has to be specifically placed in every user's .qmail delivery file. Oh another one could be obeying qmail extension addresses, which leads us to .qmail-user-alt files that need to be processed too.. it depends on your installation and how you want to use dovecot's deliver. There's a lot that needs to be addressed if one wants to try and use dovecot's deliver. Not that it's not possible, but I wouldn't consider it a drop in replacement. Rick
Re: [Dovecot] deliver and qmail
Rick Romero schrieb: You've listed two DIFFERENT versions, which may or may not include the noted patches. I don't find All subsequent contents of this document refer to qmail-1.03, most of the bugs apply to the netqmail-1.05 patchkit, too. unclear. I've removed the netqmail part of it, although netqmail addressed only a fraction of the points last time I looked at it. qmail 1.03 does not include any of the patches, and netqmail isn't an official qmail release, but a third-party patch kit. Which is the entire point - The page is just plain out of date. No, it is not - it pertains to the latest official qmail release (which is over a decade old BTW). Feel free to send a patch that weaves info about netqmail 1.06 in. I'm not doing that. -- Matthias Andree
Re: [Dovecot] deliver and qmail
On 1/28/2009, Matthias Andree (matthias.and...@gmx.de) wrote: No, it is not - it pertains to the latest official qmail release (which is over a decade old BTW). Which is as good a reason as any to not use it... Lets please limit discussion to dovecot related issues, not qmail related issues.
Re: [Dovecot] deliver and qmail
Words by Rick Romero [Wed, Jan 28, 2009 at 12:51:14PM -0600]: Oh another one could be obeying qmail extension addresses, which leads us to .qmail-user-alt files that need to be processed too.. it depends on your installation and how you want to use dovecot's deliver. There's a lot that needs to be addressed if one wants to try and use dovecot's deliver. Not that it's not possible, but I wouldn't consider it a drop in replacement. Not really that much to be addressed, I'm using it with much fuzz. -- Jose Celestino | http://japc.uncovering.org/files/japc-pgpkey.asc One man’s theology is another man’s belly laugh. -- Robert A. Heinlein
Re: [Dovecot] deliver and qmail
On Jan 28, 2009, at 1:09 PM, Jose Celestino wrote: Words by Rick Romero [Wed, Jan 28, 2009 at 12:51:14PM -0600]: Oh another one could be obeying qmail extension addresses, which leads us to .qmail-user-alt files that need to be processed too.. it depends on your installation and how you want to use dovecot's deliver. There's a lot that needs to be addressed if one wants to try and use dovecot's deliver. Not that it's not possible, but I wouldn't consider it a drop in replacement. Not really that much to be addressed, I'm using it with much fuzz. Excellent! How do you handle vacations and forwards? Do you use qmail extension addresses? Exactly how did you implement deliver? Rick
Re: [Dovecot] deliver and qmail
In all honesty, switching to qmail-ldap would fix most of these issues I'm hearing on this thread ; as you move the .qmail and forward logic to a proper centralized directory and can store the maildir info there.Integration with dovecot is mostly trivial once the info is LDAP based. ~Max On Jan 28, 2009, at 11:18 AM, Rick Romero wrote: On Jan 28, 2009, at 1:09 PM, Jose Celestino wrote: Words by Rick Romero [Wed, Jan 28, 2009 at 12:51:14PM -0600]: Oh another one could be obeying qmail extension addresses, which leads us to .qmail-user-alt files that need to be processed too.. it depends on your installation and how you want to use dovecot's deliver. There's a lot that needs to be addressed if one wants to try and use dovecot's deliver. Not that it's not possible, but I wouldn't consider it a drop in replacement. Not really that much to be addressed, I'm using it with much fuzz. Excellent! How do you handle vacations and forwards? Do you use qmail extension addresses? Exactly how did you implement deliver? Rick
Re: [Dovecot] managesieve proxy cyrus
Ok thanks for your help, By the way I've another question, we have configure a postfix smtp proxy with plain text database in order to redirect mail that coming to imap proxy to be delivered to the right imap backend. Does the dovecot imap proxy do to the local delivery itself to the right backend server ? Stephan Bosch wrote: Mathieu Kretchner schreef: It seems like the problem comes from dovecot in proxy mode ?? (only to connect to a cyrus sieve server, because it's working well with a dovecot sieve server) I'll do a few tests in the coming days. Let's see what I can find out. If you want some other network capture or tests I've done let me known, it would be a pleasure to help you ! Regards, begin:vcard fn:Mathieu Kretchner n:Kretchner;Mathieu org:INRIA;Syslog adr;dom:;;2004 route des lucioles - BP93;Sophia Antipolis;;06902 CEDEX email;internet:mathieu.kretch...@sophia.inria.fr tel;work:04 92 38 76 67 x-mozilla-html:FALSE version:2.1 end:vcard
