Re: [Dovecot] piegonhole sieve prepending header lines with an extra space
Hi Stephan, I'm not sure, I'm using Dovecot-managesieved 0.4.0-14, which I believe is commit 1771:b41f5cf04b8f, which is actually *before* the commit you mentioned. I'm not clear because you already have a release (v4.1) which does contain that patch; are you suggesting that an upgrade to that version might help? Regards, Anand On 24 July 2013 15:10, Stephan Bosch step...@rename-it.nl wrote: Op 7/24/2013 3:30 PM, Stephan Bosch schreef: Op 7/24/2013 1:04 PM, Anand Kumria schreef: As I said, my suspicions are on 'mail_crlf_save = yes', since that *is* specifically modifying the headers associated with the message. This setting has no effect on Sieve redirect since the message is not saved. However, redirect does use Dovecot functionality that filters headers and fixes line endings. What could be happening here is that the header of the message is somehow consolidated into one big Delivered-To header. I'll discuss this some more with Timo. As you suggested earlier, this change may have something to do with it: http://hg.rename-it.nl/**dovecot-2.2-pigeonhole/rev/**e439789e3211http://hg.rename-it.nl/dovecot-2.2-pigeonhole/rev/e439789e3211 The reporter of the bug that led to this change indicated that Exim presents strange behavior when the message mixes LF and CRLF line endings in the header. Since your next-hop MTA is also Exim, this may have the same root cause. Please try to apply this change and see whether this problem persists. If this fixes it, I should make a new release soon. When the problem persists, try to capture the outgoing message before it enters the MTA, e.g. by pointing sendmail_path to a shell script that saves the message somewhere. That way we can see what mail is actually being sent to the MTA. Regards, Stephan.
Re: [Dovecot] dbus support in dovecot?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 24 Jul 2013, Gene Heskett wrote: I am trying to transition from ubu10.04.4 LTS to ubu12.04.2 LTS, but in the changeover I want to setup dovecot as a local only imap server so that I can read respond to email from any of the other 4 or so machines on my local net. To that end, and given that I have a well working setup right now, using fetchmail driving mailfilter as a pre-check, procmail as the MTA delivering to /var/spool/mail/me, with clamav and spamd in the mix to intercept and send to /dev/null the worst of the spam, or to a quarantine file if clamav triggers. The current transfer mechanism is driven by a script that uses inotifywait to detect newly delivered mail in that directory, and which then sends kmail a dbus message to go get the mail. Since I want to insert dovecot into this chain, does dovecot have a dbus port, and if so, what is the format of the command it expects? Dovecot does not have no dbus support, as far as I know. If you only want to monitor one (or some minor number of mailboxes), you would setup kmail using IMAP, then tag this mailboxes to be monitored. Dovecot then uses that open connection to signal a newly arrived message. Kind regards, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUfDNdl3r2wJMiz2NAQJP3ggAqiPfjSNJm+VVSirdnx3fhk2JVlu0EkgL GUFt2vEnrsoKnqnJbo9sygjH+qL81tFS+aqN1be7yLd03pz+gBNTBNil5iG3yht3 evFoFY8m8t59wIRL4D/knIHR74tsoPxctMTvr/SmnpnmfrOQ+JuMh/Ni9/by8v8k RfyGrv3nKD16E/A01TFNfrzsnkplG9uXyl9O37UWvkPIeD7kO1cv+qkne2IQrQrH /pUmdf0C9Ws8u0hayvqZlgG4rfp/azefyde8jaMQrvghYyDqov442CgHokbvQcqO 7Bp7jvL6+UnHftLmTIionCT2pRgQAfqf+lw03bjH+EUKb0MEBoIRzg== =lr21 -END PGP SIGNATURE-
Re: [Dovecot] piegonhole sieve prepending header lines with an extra space
On 7/25/2013 8:06 AM, Anand Kumria wrote: Hi Stephan, I'm not sure, I'm using Dovecot-managesieved 0.4.0-14, which I believe is commit 1771:b41f5cf04b8f, which is actually *before* the commit you mentioned. I'm not clear because you already have a release (v4.1) which does contain that patch; are you suggesting that an upgrade to that version might help? Oh, right, it is already released. So, yes, upgrade. Regards, Stephan.
Re: [Dovecot] Managing IMAP IDLE/Push with Sieve – possible?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 23 Jul 2013, FF wrote: Thanks, that's interesting -- two questions: 1) Why is it not possible? Just not implemented, or is there any technical reason that actually prevents it from being implemented? Because the current implementation of IDLE signals any message to the waiting client. 2) What do you mean by INBOX? Another, completely separate email account? Yes, that would be my backup plan. When your client IDLEs, it monitors just one particular mailbox, say INBOX, top.sub.sub2.box, or whatever. So, if you have your client IDLE (monitor) INBOX and have all senders delivered to yet another, newly created mailbox (mail folder, ..., _not_ another mail account), which is not monitored with IDLE, you get no PUSH for them. You have to pull them. = Did you've read Robert's answer about LEMONADE? Maybe ESEARCH and NOTIFY do what you want, because RFC5465 / sec 5.2: If a search context is in effect as specified in [RFC5267], an ESEARCH ADDTO will also be generated, if appropriate. In this case, the EXISTS response MUST precede the ESEARCH response. Both the NOTIFY command and the SEARCH and SORT commands (see Section 7) can specify attributes to be returned for new messages. These attributes SHOULD be combined into a single FETCH response. The server SHOULD avoid sending duplicate data. The FETCH response(s) MUST follow any ESEARCH ADDTO responses. You could flag priority senders in Sieve and let you notify for new messages with that flag. How well or if at all Dovecot supports this (and your client ;-) ), I don't know. kind regards, -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 22 Jul 2013, FF wrote: I've been using Dovecot with Sieve for a long time already, and I'm very happy with it. Push is working fine too. I was wondering, however, whether it would be possible to define a Sieve rule (perhaps using some plug-in), such that an IMAP push message gets sent out only for specific senders etc.? I think you cannot. But you could split your INBOX into senders with PUSH (that are delivered to the INBOX) and others, that are delivered to INBOX2. - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUe4zH13r2wJMiz2NAQLd4gf/ZcfpXHUQCOozFV5L464voasate3T+aDf W6dnk9s+jOZiYmZZzaxZPw2z14v0GA5BAJdp4h/klbFPxg7Fs9MjUdoi2kusKaw6 ofbQwCsGnGD+kxme0JKtnayWo07Vwdo1rjbhxtSSGU7K4RVtnh4Kj6wTySCYrzKN +0mPIU1XUVJqw6ir+xrJSmcWY5joOnQ1+m1TI6J4E+qIqc+QjJkX1LFOMz+1Lz0x QR05UaH0+bWQPZqknWrxEEHz0eIXZsbrTuosMDHnHjDv1jRe1RzPFi6k+JvbCXcj N4ip0MNuMuYp/tXG9ntYjRwUvjJ8Du9smwh4FE72Uv11povihr7PzA== =0Afu -END PGP SIGNATURE- - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUfDSFl3r2wJMiz2NAQIvPQf/ajXvgPyv4tViMjSQsVeZkk9OWv8sYh/V 9+X30olLhCWCkVRrt1RBpwmulYkQtXgbKT09wiK+Ro5dZcT9Xmr2g9+mKdPIPFFY StXW3k82S/4IwyWRoaJRfIq5qM7UFWTcxSZFZbc0+Wo903VBZ+MdFHeQv2B6K8uX fR0BRDgbmgUhqK71r2Bg76d+rzovEGUdr21RNFrTui/cuR26uf2tsMHqAYwIU/V6 rdmjy5d9Zg4GCUcBQWMkRSjXN5E9q6NKdzh2AtHtt5BerCbG0gCSU7mWEXMwjVRx fHoy4Lhwx5vlKaFBV9Gd8oc+5jQ+po4N7drmLwtDrAZUBvKbR7jrkQ== =NFGc -END PGP SIGNATURE-
[Dovecot] Duplicate Mails downloding issue
Hi All, We are repeatedly getting the below warning / errors on our pop server. Please help us out buy knowing what could be the issue. --- Jul 23 15:34:51 popserver dovecot: pop3(14949_kavish): Warning: Locking transaction log file /indexes//mail/v3store/example.com/14949_kavish/.INBOX/dovecot.index.log took 133 seconds Jul 23 15:34:51 popserver dovecot: pop3(kav...@example.com): Error: Broken file /indexes//mail/v3store/example.com/14949_kavish/.INBOX/dovecot-uidlist line 180: UIDs not ordered (10156 = 10156) Jul 23 15:35:01 popserver dovecot: pop3(kav...@example.com): Error: utime(/indexes//mail/v3store/example.com/kavish/.INBOX/dovecot-uidlist.lock) failed: No such file or directory Jul 23 15:35:11 popserver dovecot: pop3(kav...@example.com): Error: utime(/indexes//mail/v3store/example.com/kavish/.INBOX/dovecot-uidlist.lock) failed: No such file or directory Jul 23 15:35:21 popserver dovecot: pop3(kav...@example.com): Warning: Our dotlock file /indexes//mail/v3store/example.com/kavish/.INBOX/dovecot-uidlist.lock was deleted (kept it 30 secs) - Regards, Kavish Karkera
Re: [Dovecot] dbus support in dovecot?
On Thursday 25 July 2013 07:10:38 Steffen Kaiser did opine: On Wed, 24 Jul 2013, Gene Heskett wrote: I am trying to transition from ubu10.04.4 LTS to ubu12.04.2 LTS, but in the changeover I want to setup dovecot as a local only imap server so that I can read respond to email from any of the other 4 or so machines on my local net. To that end, and given that I have a well working setup right now, using fetchmail driving mailfilter as a pre-check, procmail as the MTA delivering to /var/spool/mail/me, with clamav and spamd in the mix to intercept and send to /dev/null the worst of the spam, or to a quarantine file if clamav triggers. The current transfer mechanism is driven by a script that uses inotifywait to detect newly delivered mail in that directory, and which then sends kmail a dbus message to go get the mail. Since I want to insert dovecot into this chain, does dovecot have a dbus port, and if so, what is the format of the command it expects? Dovecot does not have no dbus support, as far as I know. If you only want to monitor one (or some minor number of mailboxes), you would setup kmail using IMAP, then tag this mailboxes to be monitored. Dovecot then uses that open connection to signal a newly arrived message. Kind regards, Might be a workable solution, if the 12.4.2 LTS supplied kmail would run. Unforch it throws an error no one on the kde-pim or kde mailing lists has ever seen, and exits when the failure advisory is closed. Fat lot of good at troubleshooting the problem that is, and one, just one of several reasons I want to switch to claws-mail. Not to mention that in order to post to either of those two lists, I have to nuke my whole sig else its held forever as potential spam. So, can this become a request for this dbus support to be added to dovecot? Or does it have its own mechanism that would cause a newly arrived message to be sieved or pigeonholed such that an imap client see's it asap? I am not fussy how the job gets done, as long as it does. Alternatively, if dovecot could take over for the fetchmail procmail/spamd/clamav chain I've been using for years, then it would know when a new message has been 'pop'ed from one of the servers I scan with fetchmail now. I printed and scanned the Steve Litt dovecot docs, but wasn't able to glean that info from what I have. And apparently the wiki2 pages have not been collated into a pdf for reference as I try to make it work. I may have something fubared there now, as my main mail server, which uses portsentry, and I am winding up in that machines hosts.deny file file every time I boot to 12.4.2 LTS + kde. I have that drive mounted in this boot. And I can't fix it once I'm blocked because my ip is blocked, so I'd have to ssh into one of the other machines at the tv station, and then ssh from that machine to the mail server. I don't keep those passwords on the wall, or use them that often. So, where in the boot sequence is dovecot started? I can mv the link in /etc/init.d, but since its a link to upstart, is that sufficient? Try it I guess. Thanks for reading this far. Cheers, Gene -- There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) My web page: http://coyoteden.dyndns-free.com:85/gene is up! My views http://www.armchairpatriot.com/What%20Has%20America%20Become.shtml Everything might be different in the present if only one thing had been different in the past. A pen in the hand of this president is far more dangerous than 200 million guns in the hands of law-abiding citizens.
Re: [Dovecot] dbus support in dovecot?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 25 Jul 2013, Gene Heskett wrote: Date: Thu, 25 Jul 2013 07:57:55 -0400 From: Gene Heskett ghesk...@wdtv.com To: dovecot@dovecot.org Subject: Re: [Dovecot] dbus support in dovecot? On Thursday 25 July 2013 07:10:38 Steffen Kaiser did opine: On Wed, 24 Jul 2013, Gene Heskett wrote: I am trying to transition from ubu10.04.4 LTS to ubu12.04.2 LTS, but in the changeover I want to setup dovecot as a local only imap server so that I can read respond to email from any of the other 4 or so machines on my local net. To that end, and given that I have a well working setup right now, using fetchmail driving mailfilter as a pre-check, procmail as the MTA delivering to /var/spool/mail/me, with clamav and spamd in the mix to intercept and send to /dev/null the worst of the spam, or to a quarantine file if clamav triggers. The current transfer mechanism is driven by a script that uses inotifywait to detect newly delivered mail in that directory, and which then sends kmail a dbus message to go get the mail. Since I want to insert dovecot into this chain, does dovecot have a dbus port, and if so, what is the format of the command it expects? Dovecot does not have no dbus support, as far as I know. If you only want to monitor one (or some minor number of mailboxes), you would setup kmail using IMAP, then tag this mailboxes to be monitored. Dovecot then uses that open connection to signal a newly arrived message. Kind regards, Might be a workable solution, if the 12.4.2 LTS supplied kmail would run. Unforch it throws an error no one on the kde-pim or kde mailing lists has ever seen, and exits when the failure advisory is closed. Fat lot of good at troubleshooting the problem that is, and one, just one of several reasons I want to switch to claws-mail. Not to mention that in order to post to either of those two lists, I have to nuke my whole sig else its held forever as potential spam. So, can this become a request for this dbus support to be added to dovecot? Or does it have its own mechanism that would cause a newly arrived message to be sieved or pigeonholed such that an imap client see's it asap? I am not fussy how the job gets done, as long as it does. Alternatively, if dovecot could take over for the fetchmail procmail/spamd/clamav chain I've been using for years, then it would know when a new message has been 'pop'ed from one of the servers I scan with fetchmail now. there might be a misunderstanding here, Dovecot is an IMAP and POP3 server. It ships tools that replicate messages from other Dovecot servers and in limits from other IMAP servers. If you intend to POP other servers, copy their messages to one local host and view your messages offline, I would keep fetchmail and Co. Or when it suits more, maybe imapsync. If you keep that chain any local mailer should be able to pick up the locally spooled messages. Maybe you could switch to Maildir as backend, in order to minimizes locking issues. Of course, you could serve that local mail spool with Dovecot to other IMAP or POP3 clients. You also could fetchmail the remote hosts and inject them into a local Dovecot server via LMTP, you can then try to run clamav and spamd from Sieve and you have the other Sieve-capabilities as well. I printed and scanned the Steve Litt dovecot docs, but wasn't able to glean that info from what I have. And apparently the wiki2 pages have not been collated into a pdf for reference as I try to make it work. I may have something fubared there now, as my main mail server, which uses portsentry, and I am winding up in that machines hosts.deny file file every time I boot to 12.4.2 LTS + kde. I have that drive mounted in this boot. And I can't fix it once I'm blocked because my ip is blocked, so I'd have to ssh into one of the other machines at the tv station, and then ssh from that machine to the mail server. I don't keep those passwords on the wall, or use them that often. So, where in the boot sequence is dovecot started? I can mv the link in /etc/init.d, but since its a link to upstart, is that sufficient? Try it I guess. Thanks for reading this far. Cheers, Gene - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUfEXv13r2wJMiz2NAQJBFQf/aXqeUlzDa7u74cfyNhtPNPGbzwKg9TCJ LhO56PmSHP9pTQncOYcdgeOAu5brNv/zPB6xBifOrpnfbjcLRRov+78GGnTszozv Zn3LMqGXbvdPrxqdMa25W5/Znm3Ndpvtb8kdhK2GwW6tQFrs5gfW82P/OdQX4FU1 xNdL34xNImj8j74q1w9wHZ8xTcQMTJCdQKJheQktR/ftyi+Eu1obq7OVt9EoIrWY bu5TBcTOPnuOOC9AQLCk1K70usoUSRoQADHfnkymwX9BLQaWnhPTT/XsB4r9bBWp hmxQDsWof8Qm3AYqJcn7FibO9tLKGW9AldBwB0gM40z3CI1qIEUSyw== =Hxz+ -END PGP SIGNATURE-
Re: [Dovecot] Duplicate Mails downloding issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 25 Jul 2013, Kavish Karkera wrote: --- Jul 23 15:34:51 popserver dovecot: pop3(14949_kavish): Warning: Locking transaction log file /indexes//mail/v3store/example.com/14949_kavish/.INBOX/dovecot.index.log took 133 seconds some process keeps the INBOX locked, but does not touch the file, so it looks like a stale lock. Jul 23 15:34:51 popserver dovecot: pop3(kav...@example.com): Error: Broken file /indexes//mail/v3store/example.com/14949_kavish/.INBOX/dovecot-uidlist line 180: UIDs not ordered (10156 = 10156) Therefore some other process had broken the lock and had appended a message. Jul 23 15:35:01 popserver dovecot: pop3(kav...@example.com): Error: utime(/indexes//mail/v3store/example.com/kavish/.INBOX/dovecot-uidlist.lock) failed: No such file or directory Jul 23 15:35:11 popserver dovecot: pop3(kav...@example.com): Error: utime(/indexes//mail/v3store/example.com/kavish/.INBOX/dovecot-uidlist.lock) failed: No such file or directory then the former process(es) finish and try to clean up, but the some other process already deleted the lock file. Jul 23 15:35:21 popserver dovecot: pop3(kav...@example.com): Warning: Our dotlock file /indexes//mail/v3store/example.com/kavish/.INBOX/dovecot-uidlist.lock was deleted (kept it 30 secs) - So you have to check your system why a process, that as locked INBOX, is stalled for more than 120min. - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUfEY6F3r2wJMiz2NAQICHwf9HJG66UAHGJp1nT8Ql31n1Bk1KWb+wAhA p2nReYZVSbzZOJM84Dkw8xLu3WoHzFxFEIS+CJc7xGtaeWGrwrTik6d7LKjwI9gf HCun1rq9VzfS85sHvn1owVJxMnUrA3YcY90aQZ6SWHNwvrdmmqqIPhQdGx7xc3En N1jJ0wPEd9hbJyi+2MScZt0WxKuRR+Wpkl14gO6ZPcX95uONGzLcSTs071rAXT+c 6RWLxn2jhruk4qUIm+PGnHkwXTnKL2Dqfladj4/ybxTRn2hgNldK8w4piUwwPWIn HW/hN+sDM/hlRtyu0zHVfiFC7MES6s0JonzwDlOKAFt9dUUG4Mcr9Q== =mar+ -END PGP SIGNATURE-
Re: [Dovecot] Duplicate Mails downloding issue
Thanks Steffen for the valuable knowledge. Need to know futher that, how could this lead to mails to get re-downloaded. ?? Regards, Kavish Karkera From: Steffen Kaiser skdove...@smail.inf.fh-brs.de To: Kavish Karkera kavish.kark...@yahoo.com Cc: dovecot@dovecot.org dovecot@dovecot.org Sent: Thursday, 25 July 2013 5:54 PM Subject: Re: [Dovecot] Duplicate Mails downloding issue -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 25 Jul 2013, Kavish Karkera wrote: --- Jul 23 15:34:51 popserver dovecot: pop3(14949_kavish): Warning: Locking transaction log file /indexes//mail/v3store/example.com/14949_kavish/.INBOX/dovecot.index.log took 133 seconds some process keeps the INBOX locked, but does not touch the file, so it looks like a stale lock. Jul 23 15:34:51 popserver dovecot: pop3(kav...@example.com): Error: Broken file /indexes//mail/v3store/example.com/14949_kavish/.INBOX/dovecot-uidlist line 180: UIDs not ordered (10156 = 10156) Therefore some other process had broken the lock and had appended a message. Jul 23 15:35:01 popserver dovecot: pop3(kav...@example.com): Error: utime(/indexes//mail/v3store/example.com/kavish/.INBOX/dovecot-uidlist.lock) failed: No such file or directory Jul 23 15:35:11 popserver dovecot: pop3(kav...@example.com): Error: utime(/indexes//mail/v3store/example.com/kavish/.INBOX/dovecot-uidlist.lock) failed: No such file or directory then the former process(es) finish and try to clean up, but the some other process already deleted the lock file. Jul 23 15:35:21 popserver dovecot: pop3(kav...@example.com): Warning: Our dotlock file /indexes//mail/v3store/example.com/kavish/.INBOX/dovecot-uidlist.lock was deleted (kept it 30 secs) - So you have to check your system why a process, that as locked INBOX, is stalled for more than 120min. - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUfEY6F3r2wJMiz2NAQICHwf9HJG66UAHGJp1nT8Ql31n1Bk1KWb+wAhA p2nReYZVSbzZOJM84Dkw8xLu3WoHzFxFEIS+CJc7xGtaeWGrwrTik6d7LKjwI9gf HCun1rq9VzfS85sHvn1owVJxMnUrA3YcY90aQZ6SWHNwvrdmmqqIPhQdGx7xc3En N1jJ0wPEd9hbJyi+2MScZt0WxKuRR+Wpkl14gO6ZPcX95uONGzLcSTs071rAXT+c 6RWLxn2jhruk4qUIm+PGnHkwXTnKL2Dqfladj4/ybxTRn2hgNldK8w4piUwwPWIn HW/hN+sDM/hlRtyu0zHVfiFC7MES6s0JonzwDlOKAFt9dUUG4Mcr9Q== =mar+ -END PGP SIGNATURE-
Re: [Dovecot] dbus support in dovecot?
On Thursday 25 July 2013 08:38:33 Steffen Kaiser did opine: there might be a misunderstanding here, Dovecot is an IMAP and POP3 server. It ships tools that replicate messages from other Dovecot servers and in limits from other IMAP servers. If you intend to POP other servers, copy their messages to one local host and view your messages offline, I would keep fetchmail and Co. That is the gist of what I have in mind. Dovecot can I assume, watch the mailfiles in /var/spool/mail? My present method of using inotifywait wrapped in a bash script to tell kmail to go get the new mail via a dbus message has worked well for years. But with no previous experience with imap, I haven't a clue how new mail arrival is handled in that sort of a setup. Or when it suits more, maybe imapsync. If you keep that chain any local mailer should be able to pick up the locally spooled messages. Maybe you could switch to Maildir as backend, in order to minimizes locking issues. Of course, you could serve that local mail spool with Dovecot to other IMAP or POP3 clients. Already pigeonholed or sieved into the usual folder format? Once I get the sorting filter rules re manufactured, that would be great! You also could fetchmail the remote hosts and inject them into a local Dovecot server via LMTP, you can then try to run clamav and spamd from Sieve and you have the other Sieve-capabilities as well. LTMP is a new acronym to me. Sorry. Synonymous to an MTA? Effectively replacing procmail with dovecot and sieve but still using spamd and clamav? Are there any better tutorials than Steve Litt's?, which seem to be getting a tad dated now. Thank you Steffen. Cheers, Gene -- There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) My web page: http://coyoteden.dyndns-free.com:85/gene is up! My views http://www.armchairpatriot.com/What%20Has%20America%20Become.shtml fortune: cpu time/usefulness ratio too high -- core dumped. A pen in the hand of this president is far more dangerous than 200 million guns in the hands of law-abiding citizens.
Re: [Dovecot] dbus support in dovecot?
At 9AM -0400 on 25/07/13 you (Gene Heskett) wrote: On Thursday 25 July 2013 08:38:33 Steffen Kaiser did opine: there might be a misunderstanding here, Dovecot is an IMAP and POP3 server. It ships tools that replicate messages from other Dovecot servers and in limits from other IMAP servers. If you intend to POP other servers, copy their messages to one local host and view your messages offline, I would keep fetchmail and Co. That is the gist of what I have in mind. Dovecot can I assume, watch the mailfiles in /var/spool/mail? My present method of using inotifywait wrapped in a bash script to tell kmail to go get the new mail via a dbus message has worked well for years. But with no previous experience with imap, I haven't a clue how new mail arrival is handled in that sort of a setup. If a mail client (kmail or anything else which supports IDLE) has a logged-in IMAP session which is sitting in IDLE, Dovecot will watch that user's mailspool and notify the client when new mail arrives. What it won't do, however, is try to take that new mail out of the spool, filter it, and put it back. If you want Dovecot to filter mail you have to insert it into the delivery chain, before the mail gets to /var/spool/mail. There are two ways of doing this: with dovecot-lda, or with LMTP. Or when it suits more, maybe imapsync. If you keep that chain any local mailer should be able to pick up the locally spooled messages. Maybe you could switch to Maildir as backend, in order to minimizes locking issues. Of course, you could serve that local mail spool with Dovecot to other IMAP or POP3 clients. Already pigeonholed or sieved into the usual folder format? Once I get the sorting filter rules re manufactured, that would be great! It sounds to me like you *just* want dovecot-lda. dovecot-lda is an MDA, that is, a program which does the same job as procmail or maildrop, and it supports Sieve. It also supports sieve extensions which let you run arbitrary programs, so you can run the mail through clamav/whatever. If you configure Dovecot to keep mail in /var/spool/mail, and to use sieve, and then replace your current call to procmail with an equivalent call to dovecot-lda, I believe this will do what you want. I'm not sure, but I think with Dovecot 2 you will need to run the basic Dovecot daemons in order to make things work, but you can turn off IMAP and POP. Of course, once you've got delivery working you could then turn IMAP back on, and get rid of that inotifywait hack. At that point there's no good reason to stick to an mbox format mailspool, since the only program which ever touches it is Dovecot, so you can switch to Maildir or dbox instead. However, I would strongly recommend changing only one thing at a time, and making sure the new setup works properly before changing anything else. You also could fetchmail the remote hosts and inject them into a local Dovecot server via LMTP, you can then try to run clamav and spamd from Sieve and you have the other Sieve-capabilities as well. LTMP is a new acronym to me. Sorry. Synonymous to an MTA? Effectively replacing procmail with dovecot and sieve but still using spamd and clamav? You mean MDA. An MTA (Mail Transfer Agent) receives mail by SMTP and either hands it to an MDA or sends it out again by SMTP; an MDA takes mail from an MTA and does local delivery. LMTP is a protocol for MTAs to talk to MDAs; that is, instead of the MTA invoking the MDA with command-line arguments and passing the message on stdin, it opens a socket (usually Unix-domain) and talks to the MDA on the other end. (The protocol itself is very nearly the same as SMTP, with one rather important difference.) Using LMTP rather than a command-line MDA means the MDA runs as a daemon, and the MTA has to be configured to use an LMTP client rather than a command for delivery. As far as Dovecot is concerned this is pretty-much the only important difference. Ben
Re: [Dovecot] Duplicate Mails downloding issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 25 Jul 2013, Kavish Karkera wrote: Thanks Steffen for the valuable knowledge. Need to know futher that, how could this lead to mails to get re-downloaded. ?? Because Dovecot detects that the UID list is erroreous and therefore rebuilts it. To prevent data loss, either the complete list of messages or just the conflicting ones [the messages that had been delivered in parallel and caused the while problem] do appear as new to the clients. From: Steffen Kaiser skdove...@smail.inf.fh-brs.de To: Kavish Karkera kavish.kark...@yahoo.com Cc: dovecot@dovecot.org dovecot@dovecot.org Sent: Thursday, 25 July 2013 5:54 PM Subject: Re: [Dovecot] Duplicate Mails downloding issue -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 25 Jul 2013, Kavish Karkera wrote: --- Jul 23 15:34:51 popserver dovecot: pop3(14949_kavish): Warning: Locking transaction log file /indexes//mail/v3store/example.com/14949_kavish/.INBOX/dovecot.index.log took 133 seconds some process keeps the INBOX locked, but does not touch the file, so it looks like a stale lock. Jul 23 15:34:51 popserver dovecot: pop3(kav...@example.com): Error: Broken file /indexes//mail/v3store/example.com/14949_kavish/.INBOX/dovecot-uidlist line 180: UIDs not ordered (10156 = 10156) Therefore some other process had broken the lock and had appended a message. Jul 23 15:35:01 popserver dovecot: pop3(kav...@example.com): Error: utime(/indexes//mail/v3store/example.com/kavish/.INBOX/dovecot-uidlist.lock) failed: No such file or directory Jul 23 15:35:11 popserver dovecot: pop3(kav...@example.com): Error: utime(/indexes//mail/v3store/example.com/kavish/.INBOX/dovecot-uidlist.lock) failed: No such file or directory then the former process(es) finish and try to clean up, but the some other process already deleted the lock file. Jul 23 15:35:21 popserver dovecot: pop3(kav...@example.com): Warning: Our dotlock file /indexes//mail/v3store/example.com/kavish/.INBOX/dovecot-uidlist.lock was deleted (kept it 30 secs) - So you have to check your system why a process, that as locked INBOX, is stalled for more than 120min. - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUfEY6F3r2wJMiz2NAQICHwf9HJG66UAHGJp1nT8Ql31n1Bk1KWb+wAhA p2nReYZVSbzZOJM84Dkw8xLu3WoHzFxFEIS+CJc7xGtaeWGrwrTik6d7LKjwI9gf HCun1rq9VzfS85sHvn1owVJxMnUrA3YcY90aQZ6SWHNwvrdmmqqIPhQdGx7xc3En N1jJ0wPEd9hbJyi+2MScZt0WxKuRR+Wpkl14gO6ZPcX95uONGzLcSTs071rAXT+c 6RWLxn2jhruk4qUIm+PGnHkwXTnKL2Dqfladj4/ybxTRn2hgNldK8w4piUwwPWIn HW/hN+sDM/hlRtyu0zHVfiFC7MES6s0JonzwDlOKAFt9dUUG4Mcr9Q== =mar+ -END PGP SIGNATURE- - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUfE3PV3r2wJMiz2NAQKdzAf9HY90QTSszIhaz7pMHYbQBMMU4XEiNBFU 3beZQLuZpYrw1aKr8xJB87DWcfyeULRgiEdWs6uSWgpYnmXYSBjDWV16HYW6+pY8 LTWr1tSY6AzUOxypx8GZfwQFhAmntwfFpoi/JiU8tDnEx2e1W44+V9hzDS4Kfy9i MQDDHRCOZL0cArAQ1DleXrQGnKY/Haa3clBfR72E/UdnGWzuGYxpORbHe9VUK8IP XrNUX1vV6RuS/cxg0/kLoVHk+0YAJCOk9kT2r2t9ZRSxSFHdzm8L/nTnQAgB+ZCR H9lNQxzi6UsRV8hT5mazMmIctW4BQsrJELV/5iWNoMDNxrYVH3Cqlg== =i01T -END PGP SIGNATURE-
Re: [Dovecot] dbus support in dovecot?
On 7/25/2013 8:02 AM, Gene Heskett wrote: On Thursday 25 July 2013 08:38:33 Steffen Kaiser did opine: there might be a misunderstanding here, Dovecot is an IMAP and POP3 server. It ships tools that replicate messages from other Dovecot servers and in limits from other IMAP servers. If you intend to POP other servers, copy their messages to one local host and view your messages offline, I would keep fetchmail and Co. That is the gist of what I have in mind. Dovecot can I assume, watch the mailfiles in /var/spool/mail? It can be configured to do so. Or it can be configured to directly receive the mail via pipe from Postfix using LDA or LMTP, and then write it to /var/spool/mail in mbox format, or to user maildirs. My present method of using inotifywait wrapped in a bash script to tell kmail to go get the new mail via a dbus message has worked well for years. But with no previous experience with imap, I haven't a clue how new mail arrival is handled in that sort of a setup. Instant notification is built into IMAP4 w/the IDLE command. See: http://en.wikipedia.org/wiki/IMAP_IDLE Or when it suits more, maybe imapsync. If you keep that chain any local mailer should be able to pick up the locally spooled messages. Maybe you could switch to Maildir as backend, in order to minimizes locking issues. Of course, you could serve that local mail spool with Dovecot to other IMAP or POP3 clients. Already pigeonholed or sieved into the usual folder format? Once I get the sorting filter rules re manufactured, that would be great! Not sure what you mean by the usual folder format. Sieve will sort into your IMAP folders. These may or may not have a 1:1 correlation to filesystem folders. Depends on the mailbox storage format you choose. You also could fetchmail the remote hosts and inject them into a local Dovecot server via LMTP, you can then try to run clamav and spamd from Sieve and you have the other Sieve-capabilities as well. LTMP is a new acronym to me. Sorry. Synonymous to an MTA? Effectively replacing procmail with dovecot and sieve but still using spamd and clamav? LMTP, Local Mail Transport protocol, is a subset of SMTP. It can be used locally or over the wire. With the Dovecot LMTP implementation, Sieve takes action on messages when they arrive, and Dovecot's indexes are updated appropriately as well. I'm not sure about spamd and clamav integration here. The vast majority of people using Dovecot deliver the mail via Postfix with LDA or LMTP, and do their AS/AV filtering in Postfix, where SPamassassin and clamav are but two of many possible packages. Many people run both of these via amavisd-new. Are there any better tutorials than Steve Litt's?, which seem to be getting a tad dated now. I'm not familiar with these tutorials. What I would suggest Gene, if possible, is using the 'standard' Postfit/Dovecot config, doing AS/AV in Postfix, have an upstream system gather the mail from your various POP mailboxes and deliver them to an address hosted by Postfix via SMTP. In other words, push all of the non standard IMAP server methodology away from, upstream of, your Dovecot installation. I'd think one of the mailbox collation services could do this. I.e. POP a dozen mailboxes and forward all the mail to a single SMTP address. Maybe fetchmail can do this. I've never used it. You may want to ask about this as OT on SDLU. Hundreds of years of combined mail experience there. -- Stan
Re: [Dovecot] Duplicate Mails downloding issue
Got it ...Thanks a ton Steffen. :) Regards, Kavish Karkera From: Steffen Kaiser skdove...@smail.inf.fh-brs.de To: Kavish Karkera kavish.kark...@yahoo.com Cc: dovecot@dovecot.org dovecot@dovecot.org Sent: Thursday, 25 July 2013 8:03 PM Subject: Re: [Dovecot] Duplicate Mails downloding issue -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 25 Jul 2013, Kavish Karkera wrote: Thanks Steffen for the valuable knowledge. Need to know futher that, how could this lead to mails to get re-downloaded. ?? Because Dovecot detects that the UID list is erroreous and therefore rebuilts it. To prevent data loss, either the complete list of messages or just the conflicting ones [the messages that had been delivered in parallel and caused the while problem] do appear as new to the clients. From: Steffen Kaiser skdove...@smail.inf.fh-brs.de To: Kavish Karkera kavish.kark...@yahoo.com Cc: dovecot@dovecot.org dovecot@dovecot.org Sent: Thursday, 25 July 2013 5:54 PM Subject: Re: [Dovecot] Duplicate Mails downloding issue -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 25 Jul 2013, Kavish Karkera wrote: --- Jul 23 15:34:51 popserver dovecot: pop3(14949_kavish): Warning: Locking transaction log file /indexes//mail/v3store/example.com/14949_kavish/.INBOX/dovecot.index.log took 133 seconds some process keeps the INBOX locked, but does not touch the file, so it looks like a stale lock. Jul 23 15:34:51 popserver dovecot: pop3(kav...@example.com): Error: Broken file /indexes//mail/v3store/example.com/14949_kavish/.INBOX/dovecot-uidlist line 180: UIDs not ordered (10156 = 10156) Therefore some other process had broken the lock and had appended a message. Jul 23 15:35:01 popserver dovecot: pop3(kav...@example.com): Error: utime(/indexes//mail/v3store/example.com/kavish/.INBOX/dovecot-uidlist.lock) failed: No such file or directory Jul 23 15:35:11 popserver dovecot: pop3(kav...@example.com): Error: utime(/indexes//mail/v3store/example.com/kavish/.INBOX/dovecot-uidlist.lock) failed: No such file or directory then the former process(es) finish and try to clean up, but the some other process already deleted the lock file. Jul 23 15:35:21 popserver dovecot: pop3(kav...@example.com): Warning: Our dotlock file /indexes//mail/v3store/example.com/kavish/.INBOX/dovecot-uidlist.lock was deleted (kept it 30 secs) - So you have to check your system why a process, that as locked INBOX, is stalled for more than 120min. - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUfEY6F3r2wJMiz2NAQICHwf9HJG66UAHGJp1nT8Ql31n1Bk1KWb+wAhA p2nReYZVSbzZOJM84Dkw8xLu3WoHzFxFEIS+CJc7xGtaeWGrwrTik6d7LKjwI9gf HCun1rq9VzfS85sHvn1owVJxMnUrA3YcY90aQZ6SWHNwvrdmmqqIPhQdGx7xc3En N1jJ0wPEd9hbJyi+2MScZt0WxKuRR+Wpkl14gO6ZPcX95uONGzLcSTs071rAXT+c 6RWLxn2jhruk4qUIm+PGnHkwXTnKL2Dqfladj4/ybxTRn2hgNldK8w4piUwwPWIn HW/hN+sDM/hlRtyu0zHVfiFC7MES6s0JonzwDlOKAFt9dUUG4Mcr9Q== =mar+ -END PGP SIGNATURE- - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUfE3PV3r2wJMiz2NAQKdzAf9HY90QTSszIhaz7pMHYbQBMMU4XEiNBFU 3beZQLuZpYrw1aKr8xJB87DWcfyeULRgiEdWs6uSWgpYnmXYSBjDWV16HYW6+pY8 LTWr1tSY6AzUOxypx8GZfwQFhAmntwfFpoi/JiU8tDnEx2e1W44+V9hzDS4Kfy9i MQDDHRCOZL0cArAQ1DleXrQGnKY/Haa3clBfR72E/UdnGWzuGYxpORbHe9VUK8IP XrNUX1vV6RuS/cxg0/kLoVHk+0YAJCOk9kT2r2t9ZRSxSFHdzm8L/nTnQAgB+ZCR H9lNQxzi6UsRV8hT5mazMmIctW4BQsrJELV/5iWNoMDNxrYVH3Cqlg== =i01T -END PGP SIGNATURE-
[Dovecot] Case-insensitive detail mailboxes?
We're using sieve with LMTP. We want to have lda_mailbox_autocreate and lmtp_save_to_detail_mailbox. Is there a way to make the detail case-insensitive? If so I have not found it yet. I suppose we could lowercase the input string for the SQL userdb query, but that's not what is wanted. The idea being that if a user makes a mailbox called Test is that user+t...@example.com and user+t...@example.com should both go to that Test mailbox. If it was lowercased, a mailbox called Test would be ignored and test used. With autocreate, this could be a problem if mail is delivered to autocreated case-sensitive mailboxes that the user won't see. Hmmm, maybe a global sieve script? -- http://rob0.nodns4.us/ -- system administration and consulting Offlist GMX mail is seen only if /dev/rob0 is in the Subject:
Re: [Dovecot] Case-insensitive detail mailboxes?
On 25.7.2013, at 19.43, Timo Sirainen t...@iki.fi wrote: On 25.7.2013, at 19.29, /dev/rob0 r...@gmx.co.uk wrote: We're using sieve with LMTP. We want to have lda_mailbox_autocreate and lmtp_save_to_detail_mailbox. Is there a way to make the detail case-insensitive? If so I have not found it yet. I suppose we could lowercase the input string for the SQL userdb query, but that's not what is wanted. The idea being that if a user makes a mailbox called Test is that user+t...@example.com and user+t...@example.com should both go to that Test mailbox. If it was lowercased, a mailbox called Test would be ignored and test used. With autocreate, this could be a problem if mail is delivered to autocreated case-sensitive mailboxes that the user won't see. If you used case-insensitive filesystem, it would already work like that. Maybe a new setting to make mailboxes case-insensitive also with case-sensitive filesystems.. Oh, except then you get into trouble with non-ASCII characters. Which unicode chars should be equal? Maybe i;unicode-casemap would work well enough, since it's also used for other purposes.
Re: [Dovecot] Case-insensitive detail mailboxes?
On 25.7.2013, at 19.29, /dev/rob0 r...@gmx.co.uk wrote: We're using sieve with LMTP. We want to have lda_mailbox_autocreate and lmtp_save_to_detail_mailbox. Is there a way to make the detail case-insensitive? If so I have not found it yet. I suppose we could lowercase the input string for the SQL userdb query, but that's not what is wanted. The idea being that if a user makes a mailbox called Test is that user+t...@example.com and user+t...@example.com should both go to that Test mailbox. If it was lowercased, a mailbox called Test would be ignored and test used. With autocreate, this could be a problem if mail is delivered to autocreated case-sensitive mailboxes that the user won't see. If you used case-insensitive filesystem, it would already work like that. Maybe a new setting to make mailboxes case-insensitive also with case-sensitive filesystems..
Re: [Dovecot] dbus support in dovecot?
On Thursday 25 July 2013 15:13:58 Stan Hoeppner did opine: On 7/25/2013 8:02 AM, Gene Heskett wrote: On Thursday 25 July 2013 08:38:33 Steffen Kaiser did opine: there might be a misunderstanding here, Dovecot is an IMAP and POP3 server. It ships tools that replicate messages from other Dovecot servers and in limits from other IMAP servers. If you intend to POP other servers, copy their messages to one local host and view your messages offline, I would keep fetchmail and Co. That is the gist of what I have in mind. Dovecot can I assume, watch the mailfiles in /var/spool/mail? It can be configured to do so. Or it can be configured to directly receive the mail via pipe from Postfix using LDA or LMTP, and then write it to /var/spool/mail in mbox format, or to user maildirs. My present method of using inotifywait wrapped in a bash script to tell kmail to go get the new mail via a dbus message has worked well for years. But with no previous experience with imap, I haven't a clue how new mail arrival is handled in that sort of a setup. Instant notification is built into IMAP4 w/the IDLE command. See: http://en.wikipedia.org/wiki/IMAP_IDLE Or when it suits more, maybe imapsync. If you keep that chain any local mailer should be able to pick up the locally spooled messages. Maybe you could switch to Maildir as backend, in order to minimizes locking issues. Of course, you could serve that local mail spool with Dovecot to other IMAP or POP3 clients. Already pigeonholed or sieved into the usual folder format? Once I get the sorting filter rules re manufactured, that would be great! Not sure what you mean by the usual folder format. Sieve will sort into your IMAP folders. These may or may not have a 1:1 correlation to filesystem folders. Depends on the mailbox storage format you choose. Where the email client see's the incoming email already sorted into what are subdirs, in the case of kmail, in the users $HOME/Mail dir. I see claws can see the directory tree kmail has built, but cannot see the kmail messages because it doesn't look into kde-pim/cur. Everything I have pulled from /var/spool/mail/gene with clawsmail has been put as individual numbered files, all in the kmail 'inbox'. Where I am the only user here, that is not a problem, but it seems to me this individual directory for each mailing list, really should be another tree in /var/mail, but then somehow is it shared such that if I am at one of the machines that run my cnc milling machine or cnc lathe, 150 feet of cat5 and an 8 port switch, so that what I see from one of those machines is identical to what I would see on this machine? You also could fetchmail the remote hosts and inject them into a local Dovecot server via LMTP, you can then try to run clamav and spamd from Sieve and you have the other Sieve-capabilities as well. There ought to be a tut someplace for this, but in my googling for such, nothing has popped up. And wiki2 doesn't seem to get into adequate 'depth', its TBT, closer to a sales pitch than a users howto manual, or I'm not hitting the right links in my 10,000 monkeys like performance. ;) LTMP is a new acronym to me. Sorry. Synonymous to an MTA? Effectively replacing procmail with dovecot and sieve but still using spamd and clamav? LMTP, Local Mail Transport protocol, is a subset of SMTP. It can be used locally or over the wire. With the Dovecot LMTP implementation, Sieve takes action on messages when they arrive, and Dovecot's indexes are updated appropriately as well. I'm not sure about spamd and clamav integration here. The vast majority of people using Dovecot deliver the mail via Postfix with LDA or LMTP, and do their AS/AV filtering in Postfix, where SPamassassin and clamav are but two of many possible packages. Many people run both of these via amavisd-new. Something else to muddy the waters it seems, but I've not actually looked at it either. Possibly my bad. Are there any better tutorials than Steve Litt's?, which seem to be getting a tad dated now. I'm not familiar with these tutorials. He wrote an escape from kmail' tutorial, 33 pages IIRC, but its a couple years old now. What I would suggest Gene, if possible, is using the 'standard' Postfit/Dovecot config, doing AS/AV in Postfix, have an upstream system gather the mail from your various POP mailboxes and deliver them to an address hosted by Postfix via SMTP. In other words, push all of the non standard IMAP server methodology away from, upstream of, your Dovecot installation. I'd think one of the mailbox collation services could do this. I.e. POP a dozen mailboxes and forward all the mail to a single SMTP address. Maybe fetchmail can do this. I've never used it. I actually do that now, popping 3 servers with fetchmail, 2 of which are actually google-mail since my ISP defaulted on keeping a server that actually worked
Re: [Dovecot] dbus support in dovecot?
On 7/25/2013 2:45 PM, Gene Heskett wrote: However, I would really like to start with some in depth docs, docs I am not having a lot of luck finding. But I am not, as you can see, too bashful to go ask the source. ;) The main problem you're facing right now is that you don't really yet grasp what IMAP is all about. In a nutshell, once you install Dovecot, or any IMAP server, it becomes the single point of control and access to all of your mail. You install an IMAP MUA on each client PC, point these at Dovecot, and you're basically done. They can all be logged into the same account simultaneously, and any new mail will show up in the INBOX on all clients simultaneously, or nearly so. You typically don't need to configure the clients other than telling them where the server is and plugging in login credentials. The rest is pretty much automatic. Any folders the user has access to should display automatically without needing to manually subscribe. At least this is how it works with Thunderbird. In other words, with an IMAP server, you simply ditch most of your old way of doing things with your MUAs. The only program that will write/read your mail files will be the IMAP server, Dovecot in this case. All the clients must access mail through an IMAP connection. -- Stan
Re: [Dovecot] dbus support in dovecot?
On Thursday 25 July 2013 22:45:04 Stan Hoeppner did opine: On 7/25/2013 2:45 PM, Gene Heskett wrote: However, I would really like to start with some in depth docs, docs I am not having a lot of luck finding. But I am not, as you can see, too bashful to go ask the source. ;) The main problem you're facing right now is that you don't really yet grasp what IMAP is all about. Is wiki2 the sum total of the docs for this? If it is the definitive manual, great. In a nutshell, once you install Dovecot, or any IMAP server, it becomes the single point of control and access to all of your mail. You install an IMAP MUA on each client PC, point these at Dovecot, and you're basically done. They can all be logged into the same account simultaneously, and any new mail will show up in the INBOX on all clients simultaneously, or nearly so. This restriction to the INBOX bothers me because the present kmail setup I'm using has about 55 individual folders such that messages from a mailing list are sorted by kmail and placed in the appropriate folder/directory. That includes this mailing list. You typically don't need to configure the clients other than telling them where the server is and plugging in login credentials. The rest is pretty much automatic. Any folders the user has access to should display automatically without needing to manually subscribe. At least this is how it works with Thunderbird. I know t-bird can do this message sorting when it is functioning as its own fetchmail as I have done that on my lappy when I am on the road which in this case might be yet another tv station that needs a consultant engineer, either to clean up the technical messes other engineers have constructed, or in the case of one station in upstate MI that doesn't have engineering staff, so I get flown in with the owners airplane when it upchucks. The market there is way too small to support a local tv station, but the commission put a license there anyway. But back to t-bird, can it be made to look the same in terms of folders vs folder contents, with say 3 local copies, one on this box, and one each on the boxes running the cnc machines? All accomplished hopefully by getting one copy working, and copying its configs to the other 2, or maybe 3 machines. I use the lappy in the shop to ssh into the cnc boxes so I can sit in relative comfort when making more copies of some part. 90% of the stuff I do is one off's, but I might need a 12 pack of a custom bolt or ?? In other words, with an IMAP server, you simply ditch most of your old way of doing things with your MUAs. The only program that will write/read your mail files will be the IMAP server, Dovecot in this case. All the clients must access mail through an IMAP connection. Where does dovecot actually keep the email corpus? I am assuming that is an assignment in 10-master.conf, but there is a quite lengthy list of stuff in the dovecot/conf.d tree that I haven't been able to find in the wiki2 pages. Sure, I can grep for a given variables name, but first, I need to know the name of the variable... Classic new user chicken v egg stuff. My present du -h on /home/gene/Mail is about 4.8Gb, and the databases kmail keeps for indices etc (and there seems to be an ever growing list of etc's, all convinced they have to have their own copies of everything) aren't there, but total another 16Gb at other locations on my HD's, between soprano and virtuoso. That alone is enough to convince me kmail has got to go. And the kde folks simply will not entertain the suggestion they have bloated it out of viability for even a user willing to restart it daily, and reboot the machine on a weekly basis because it gets so laggy. Thank you Stan. Cheers, Gene -- There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) My web page: http://coyoteden.dyndns-free.com:85/gene is up! My views http://www.armchairpatriot.com/What%20Has%20America%20Become.shtml A poet who reads his verse in public may have other nasty habits. A pen in the hand of this president is far more dangerous than 200 million guns in the hands of law-abiding citizens.
Re: [Dovecot] Case-insensitive detail mailboxes?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 25 Jul 2013, Timo Sirainen wrote: On 25.7.2013, at 19.43, Timo Sirainen t...@iki.fi wrote: On 25.7.2013, at 19.29, /dev/rob0 r...@gmx.co.uk wrote: We're using sieve with LMTP. We want to have lda_mailbox_autocreate and lmtp_save_to_detail_mailbox. Is there a way to make the detail case-insensitive? If so I have not found it yet. I suppose we could lowercase the input string for the SQL userdb query, but that's not what is wanted. The idea being that if a user makes a mailbox called Test is that user+t...@example.com and user+t...@example.com should both go to that Test mailbox. If it was lowercased, a mailbox called Test would be ignored and test used. With autocreate, this could be a problem if mail is delivered to autocreated case-sensitive mailboxes that the user won't see. If you used case-insensitive filesystem, it would already work like that. Maybe a new setting to make mailboxes case-insensitive also with case-sensitive filesystems.. Oh, except then you get into trouble with non-ASCII characters. Which unicode chars should be equal? Maybe i;unicode-casemap would work well enough, since it's also used for other purposes. I see two other solvable problems: if a user makes a mailbox called Test is that user+t...@example.com and user+t...@example.com should both go to that Test mailbox. Hence, the delivery process would need some sort of mapping (dict): case-insensitive - real spelling i.e. the user creates teSt or teST a.s.o., in order to find the correct mailbox name in case-sensitive filesystems efficiently. Secondly, what happens, if the user wants to create two mailboxes with different case, say Test and tesT and test ? Either this is forbidden or the delivery process needs to first check, if there is a mailbox with the very exact name, but which one is to choose, if neither matches? Personally, I would forbid two mailboxes that differs in case only, if such mechanism is enabled. - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUfIO/F3r2wJMiz2NAQKUVggAhLSRrCiYvxEP5WKONqa78upQbER78Mo6 hW+7q6MJaGe28Hc7vROgV0pYzr3+zV5jBbWJescYrjAqsJ3Oeao39XQwJM8UWHOJ agfNkzytjyCW/KMtpXrzGdX0H2Cv49ek5bjKDeG8XDLJZuy0azen7aXxsNYXKC0X D31MslQkJ3VSlcyZiu/KTbo0caQyCx4Pyj5exTOp9aoAjL6SGaIyZvzSjfFwrJUx 2TuF7YtPr5PyH2OPG2T8uraw+TNm2St+oM04dG8BgOTo8p5Q0DO2OtuFTTZvVxtu 14bc8fomuYruAvrT0uoGJxSpUU1PID5UNEK2bj4Nw8bAm+C73Z6aAA== =1RLr -END PGP SIGNATURE-
