Re: [Dovecot] v2.0 configuration parsing
On Aug 10, 2009, at 11:57 AM, Timo Sirainen wrote:
I'm trying to figure out how exactly v2.0 should be parsing
configuration files. The most annoying part is if it should always
just
use whatever comes first in config or try some kind of a use most
specific rule. The most specific kind of makes more sense
initially,
but then you start wondering how to handle e.g.:
1) User logs in to imap from 192.168.0.1. What is foo's value?
protocol imap {
remote_ip 192.168.0.0/16 {
foo = foo
}
}
remote_ip 192.168.0.0/24 {
foo = bar
}
2) User logs in from 192.168.0.1 to 10.1.2.3. What is foo's value?
local_ip 192.168.0.1 {
remote_ip 10.1.2.0/24 {
foo = foo
}
}
remote_ip 10.1.2.3 {
local_ip 192.168.0.0/24 {
foo = bar
}
}
Any thoughts?
Figure out that they intersect and return an error!
Aria Stewart
aredri...@nbtsc.org
Re: [Dovecot] v3.0 architecture
The big problem is what the protocol should be. Use some existing RPC protocol? It should be something extensible so that a plugin in imap process can talk to a plugin in storage process, without the base processes knowing anything about the details (e.g. imap-quota plugin asking quota usage from storage's quota plugin). In any case the client side API should be asynchronous. That can make it annoyingly difficult to use though. Wonder if I could switch to erlang or something for the imap/pop3 processes :) process-to-process D-Bus! smime.p7s Description: S/MIME cryptographic signature
Re: [Dovecot] GlusterFS
On Aug 11, 2008, at 10:22 AM, Timo Sirainen wrote: On Aug 7, 2008, at 3:57 AM, Jeroen Koekkoek wrote: I receive the following error message. Aug 7 09:38:51 mta2 dovecot: POP3([EMAIL PROTECTED]): nfs_flush_fcntl: fcntl(/var/vmail/domain.tld/somebody/Maildir/dovecot.index, F_RDLCK) failed: Function not implemented Dovecot tries to flush kernel's data cache. You might need volume plocks type features/posix-locks subvolumes posix end-volume Or equivalent in your glusterfs configuration I think that I can disable mail_nfs_index to fix these messages. Has anybody had the same problem, if so, how did you solve it? You could disable mail_nfs_index, but that if the same mailbox is accessed concurrently from multiple servers that will probably cause index corruption. Aria Stewart [EMAIL PROTECTED]
[Dovecot] Bug handling zero-byte files in maildirs
I managed to get a bunch of zero-byte files in my maildirs today, and Dovecot choked completely (at least for pop3 users); It wouldn't download any messages at all, and the mailbox would often say -ERR [IN-USE] when doing a STAT Aria
Re: [Dovecot] [OT] Webmail Recommendation
On Jan 10, 2008, at 9:16 PM, Timo Sirainen wrote: So I wrote my own. http://dinhe.net/~aredridel/projects/ruby/camping-at-the-mailbox Missing screenshots. :) http://dinhe.net/~aredridel/projects/ruby/camping-at-the-mailbox-screenshots Cheers!
Re: [Dovecot] [OT] Webmail Recommendation
On Jan 11, 2008, at 4:50 AM, Chris Wakelin wrote: Charles Marcus wrote: On 1/10/2008, Timo Sirainen ([EMAIL PROTECTED]) wrote: No-one mentioned WebAlpine yet, which also uses persistent connections. I haven't tried it myself though. I though this is what imapproxy did for webmail? We only have one or two people who actually use ours (Squirrelmail), so it isn't an issue on our dual opteron server, but I've thought about installing it anyway... Last time I looked at it, imapproxy cached authentication (but so can Dovecot!) but not SELECTs (i.e. opening a mailbox), which is why I wondered how useful it would be. It's not all its cracked up to be. Honestly, a webmail client that truly takes advantage of IMAP's features is a stronger win.
Re: [Dovecot] [OT] Webmail Recommendation
OK, let's try to get a bit more on topic and go back to the original question of what's a good webmail client for Dovecot? We went with Prayer Webmail (written by the University of Cambridge) as it's killer feature was *persistent* IMAP connections. Persistence is a total win for webmail. It's among the issues I had with everything written in PHP. So I wrote my own. http://dinhe.net/~aredridel/projects/ruby/camping-at-the-mailbox It uses the ruby Camping framework, and runs as its own daemon or fastcgi process. It's working relatively well, and has a sparse, low-fi but pretty usable interface. I'm actively taking patches, too, and am interested in grafting on an AJAX-additional interface. Aria
Re: [Dovecot] Please solve my query
On Dec 3, 2007, at 11:59 AM, bhagwat swarup wrote: hi my question is Start a POP3 server on rhel5 with a matching criteria 1) user jack must get mail 2 Allow your network lw.com 3)my133.org domain can not access your server Deny by reverse DNS lookup, so that hosts that reverse to *.my133.org? What do you mean by a domain accessing a server? A domain label is just a record, so some clarification is neccesary
Re: [Dovecot] append bug in 1.1beta4?
On Fri, 2007-10-26 at 10:35 +0200, Daniel wrote: Hi! I'm guessing this is the append bug which is still present in dovecot-1.1beta4?: Info: IMAP(leva): Disconnected: EOF while appending bytes=31665/119125 This happens after sending a mail, and trying upload/copy that mail from my local Sent folder to my IMAP server's Sent folder. Daniel Ditto signature.asc Description: This is a digitally signed message part
Re: [Dovecot] plugin problem
I don't see this as a problem at all (why create one when there's none to be found:): * Move message into Spam: it's a spam that should be reclassified. * Move message out of Spam: it's a ham that should be reclassified. Don't really care where the mail comes from or where it is moved. This is the beauty of it all, count the key or mouse clicks, can't be less than this:) * Using the expire plugin, the Spam folder will be emptied auto- matically in due time (typically 30 days maybe) without user intervention. All close to zero maintenance for sysadmin as well as end-user. This is the part that's made me really excited about the plugin too. I've needed a new spam solution -- my old spamassassin setup was too hard to control for my users. This sounds truly wonderful. (haven't gotten the plugin to work yet, and haven't made time to) Aria signature.asc Description: This is a digitally signed message part
Re: [Dovecot] 1.0.rc29 released
On Fri, 2007-03-30 at 16:05 -0700, Kenneth Porter wrote: --On Friday, March 30, 2007 3:24 PM -0700 Frank Cusack [EMAIL PROTECTED] wrote: This is why I'm still using 0.99. The RC's still look like betas and I have no idea which one (if any) is less a regression than any other. They ARE betas. That's no reason to stay with 0.99. It's effectively beta as well. In principle, a release candidate should be a gamma. It should be effectively ready for release, and distributed to check for awful show-stoppers. Is 1.0rc29 stable enough to replace 0.99 from Fedora? Will I suddenly have a bunch of angry users seeing things break? It is stable enough. I've been using it in production, and each RC, with no issues. Really damn good software. 1.0.rc1 was released in June. Here's a quote from the release message for rc11 (November 4): Hopefully the last RC release? As far as I know there are no major problems left now. If nothing big shows up, v1.0 should be out in a couple of weeks. In rc27: A few new small features and lots of index/mbox fixes. I've been heavily stress testing this release, so I think it should be about perfect. :) *Features*?! In an rc?! No wonder there's no convergence. Oddly, the new features don't seem to act up. Just little issues keep coming up.
