Re: [Dovecot] HA Dovecot Config?
Quoting Rick Romero : See that last line there??? Want to bet something in the mail setup (MTA, dovecot, system jobs like backup, etc) put an exclusive lock on files from time to time? I thought the entire reason (ok not the _entire_ reason but..) for Maildir was to avoid locks and allow easy concurrent access to a mailbox through many different applications. Okay, so if you are real careful (use maildir instead of some other format like mbox, don't use it for your dovecot index/control files, don't do native backups but use a snapshot, don't involve any other programs which might introduce locks, etc. then you can probably get away with it. But I still wouldn't bet on it. So while I do agree that file locking is a possible problem in an active/active setup with FRP, I think it's possible - as long as the admin is aware of the risks. And the ways to avoid locking... And assuming locking is the only issue (other issues may arise depending on implementation). Yes, there are definitely things to be aware of. I'm not sure if this is the place to hash it out, but I think that while it's not a cheap solution it may fit MY environment - and possibly others who use Maildir. OP didn't specify many details, so assumptions were made... On my system, I share mbox files and dovecot indexes, and they both having locking... I guess everyone is as cheap as I am and hasn't set it up yet :) Uhm, DRBD is free and this suggested alternative isn't AFAIK, so I don't think it is being cheap... I'm thinking it is more about reputation and install bases... Rick -- Eric Rostetter The Department of Physics The University of Texas at Austin Go Longhorns!
Re: [Dovecot] sieve + redirect + as attachment
Jerry wrote: Is it possible to use the 'redirect' function in 'sieve' to forward a message as an attachment rather than in-line? Unfortunately, no. I thought the (draft) enclose extension could provide this new feature, but the specification explicitly excludes redirect from being affected: http://ietfreport.isoc.org/idref/draft-ietf-sieve-mime-loop/#page-11 I am not sure exactly why. To my knowledge this is not provided by any other Sieve feature/extension. Regards, Stephan
Re: [Dovecot] HA Dovecot Config?
On Wed, 2009-10-21 at 15:35 -0500, Rick Romero wrote: > I thought the entire reason (ok not the _entire_ reason but..) for > Maildir was to avoid locks and allow easy concurrent access to a > mailbox through many different applications. > > From DJB's page: http://cr.yp.to/proto/maildir.html > > Why should I use maildir? > Two words: no locks Yeah, right. http://wiki.dovecot.org/MailboxFormat/Maildir#Locking signature.asc Description: This is a digitally signed message part
[Dovecot] sieve + redirect + as attachment
Is it possible to use the 'redirect' function in 'sieve' to forward a message as an attachment rather than in-line? -- Jerry ges...@yahoo.com |=== |=== |=== |=== | A woman was in love with fourteen soldiers, it was clearly platoonic.
Re: [Dovecot] HA Dovecot Config?
Quoting "Eric Rostetter" : Quoting Rick Romero : They claim to be real-time, and with kernel hooks into reads/writes, it seems promising to run on top of the OS.. Yes, but that doesn't mean it will work in the cluster environment... It also says things like: There are different types of file locks. In addition to these differences, each OS has its own set of rules regarding file locks as well. FRP's replication of locked files will vary in relation to the way the OS treats these types. However, one rule is consistent throughout all operating systems in that exclusive file locks will prevent FRP from replicating data. See that last line there??? Want to bet something in the mail setup (MTA, dovecot, system jobs like backup, etc) put an exclusive lock on files from time to time? Again, a fine backup system, and depending on your needs it might be okay for a failover setup, but not for an active-active setup. For that you need a lock manager, which they promise "in the future" but don't deliver yet... I thought the entire reason (ok not the _entire_ reason but..) for Maildir was to avoid locks and allow easy concurrent access to a mailbox through many different applications. From DJB's page: http://cr.yp.to/proto/maildir.html Why should I use maildir? Two words: no locks So while I do agree that file locking is a possible problem in an active/active setup with FRP, I think it's possible - as long as the admin is aware of the risks. So for backup purposes, to avoid locks for example, use ZFS snapshots. I'm not even a user of FRP at this point, but it's something that intrigues me for active/active because of it's OS independence. I want ZFS. I really enjoy ZFS. I already have active/passive with zfs sends, I want to step it up :) Yes, there are definitely things to be aware of. I'm not sure if this is the place to hash it out, but I think that while it's not a cheap solution it may fit MY environment - and possibly others who use Maildir. I guess everyone is as cheap as I am and hasn't set it up yet :) Rick
Re: [Dovecot] [sendmail] deliver+sieve: Destination address (-a) parsing changes
"Frank Behrens" wrote: > Andrzej Adam Filip wrote on 21 Oct 2009 20:02: >> Dovecot's design issues to consider are as follows: >> a) making dovecot support hash/btree/dbm maps for passwd/userdb >>[AFAIR Timo stated it is too complicated to be "cost effective" from >>his perspective] >> b) making dovecot support sendmail's "socket map" protocol for checking >>mailbox existence >>The simple protocol is described in semdmail's doc/op/op.me file >>http://www.sendmail.org/doc/sendmail-current/doc/op/op.pdf >> c) making dovecot support LMTP protocol via unix socket > > If I understand you right, this is a wish for virtual mailboxes, isn't > it? Regular systems users work without problems. What I want is only > the additional envelope receiver address available in dovecot-sieve. I > see see no problems in mailbox selection in sendmail and dovecot. >From your perspective "socket map" support in dovecot may give a way to reject messages to "over quota" recipients in reply to "RCPT TO:". -- [pl>en: Andrew] Andrzej Adam Filip : a...@onet.eu You can't have everything. Where would you put it? -- Steven Wright
Re: [Dovecot] meaning of parameter imap_idle_notify_interval??
Here are the requestet information. It was compiled with inotify which is the default on my system. First I thought, it was the purpose, that the mailbox dirs was on an NFS. Then copied to the local disc. But the same. [r...@mail ~]# /opt/dovecot/sbin/dovecot --build-options Build options: ioloop=epoll notify=inotify ipv6 openssl Mail storages: cydir dbox maildir mbox raw shared SQL drivers: postgresql Passdb: checkpassword pam passwd passwd-file shadow sql Userdb: nss passwd passwd-file prefetch sql static [r...@mail ~]# /opt/dovecot/sbin/dovecot -n # 1.2.6: /opt/dovecot/etc/dovecot.conf # OS: Linux 2.6.18-128.7.1.el5 i686 CentOS release 5.3 (Final) ext3 base_dir: /var/run/dovecot/ listen: *:143 ssl_listen: *:993 ssl_cert_file: /opt/dovecot/etc/ssl/certs/mail.ghostdive.org.crt ssl_key_file: /opt/dovecot/etc/ssl/private/mail.ghostdive.org.key disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /opt/dovecot/libexec/dovecot/imap-login login_greeting: ready. login_processes_count: 10 mail_max_userip_connections: 50 mail_location: maildir:/mnt/mail/%u/Maildir:INDEX=/var/spool/indexes/%u mailbox_idle_check_interval: 2 dbox_rotate_size: 4096 dbox_rotate_days: 30 mail_executable: /opt/dovecot/libexec/dovecot/rawlog -b /opt/dovecot/libexec/dovecot/imap imap_idle_notify_interval: 30 lda: postmaster_address: postmas...@ghostdive.org hostname: mail.ghostdive.org mail_plugins: sieve mail_plugin_dir: /opt/dovecot/lib/dovecot/lda sendmail_path: /opt/postfix26/sbin/sendmail auth default: mechanisms: plain cram-md5 digest-md5 passdb: driver: sql args: /opt/dovecot/etc/dovecot-sql.conf userdb: driver: sql args: /opt/dovecot/etc/dovecot-sql.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: mailaccess group: mailaccess Timo Sirainen schrieb: > On Wed, 2009-10-21 at 21:28 +0200, Ingo Thierack wrote: > >> Hello, >> >> is my understanding of the parameter "imap_idle_notify_interval" right, >> if i say, >> it's the time between two point where dovecot tells the client he is >> here, and >> sould have nothing directly todo with the notification of new mails arrived. >> > > Right. > > >> I played with the values around. And the courios is, in thunderbird the >> folloing. >> >> set to 30 seconds. >> >> Thunderbird pop up around 25 seconds after the message is deliverd to >> the inbox. >> >> set to 60 seconds. >> >> Thunderbird pup up around 50 seconds after the message is deliverd to >> the inbox. >> > > I don't see how that setting would affect either of these. > > Did you build Dovecot with inotify/dnotify/kqueue support? (What does > dovecot --build-options show?) If not, mailbox_idle_check_interval is > what controls how often new mails are checked. >
Re: [Dovecot] Maildir autocreation
Timo Sirainen пишет:
On Oct 21, 2009, at 11:09 AM, Proskurin Kirill wrote:
No. :-(
#fgrep 'mail_location' /usr/local/etc/dovecot.conf | fgrep -v #
mail_location = maildir:/var/spool/dovecot/domains/%d/%n
mail_location = /var/spool/dovecot/domains/%d/%n/
Second hit - it is a sieve rules part.
What do you mean? The second one in plugin {} overrides the first one.
Oh... thanks! I missunderstand it.
I don`t know why but it is seems to work well in 1.1...
--
Best regards,
Proskurin Kirill
Re: [Dovecot] [sendmail] deliver+sieve: Destination address (-a) parsing changes
Andrzej Adam Filip wrote on 21 Oct 2009 20:02: > Dovecot's design issues to consider are as follows: > a) making dovecot support hash/btree/dbm maps for passwd/userdb >[AFAIR Timo stated it is too complicated to be "cost effective" from >his perspective] > b) making dovecot support sendmail's "socket map" protocol for checking >mailbox existence >The simple protocol is described in semdmail's doc/op/op.me file >http://www.sendmail.org/doc/sendmail-current/doc/op/op.pdf > c) making dovecot support LMTP protocol via unix socket If I understand you right, this is a wish for virtual mailboxes, isn't it? Regular systems users work without problems. What I want is only the additional envelope receiver address available in dovecot-sieve. I see see no problems in mailbox selection in sendmail and dovecot. -- Frank Behrens, Osterwieck, Germany PGP-key 0x5B7C47ED on public servers available.
Re: [Dovecot] meaning of parameter imap_idle_notify_interval??
On Wed, 2009-10-21 at 21:28 +0200, Ingo Thierack wrote: > Hello, > > is my understanding of the parameter "imap_idle_notify_interval" right, > if i say, > it's the time between two point where dovecot tells the client he is > here, and > sould have nothing directly todo with the notification of new mails arrived. Right. > I played with the values around. And the courios is, in thunderbird the > folloing. > > set to 30 seconds. > > Thunderbird pop up around 25 seconds after the message is deliverd to > the inbox. > > set to 60 seconds. > > Thunderbird pup up around 50 seconds after the message is deliverd to > the inbox. I don't see how that setting would affect either of these. Did you build Dovecot with inotify/dnotify/kqueue support? (What does dovecot --build-options show?) If not, mailbox_idle_check_interval is what controls how often new mails are checked. signature.asc Description: This is a digitally signed message part
[Dovecot] meaning of parameter imap_idle_notify_interval??
Hello, is my understanding of the parameter "imap_idle_notify_interval" right, if i say, it's the time between two point where dovecot tells the client he is here, and sould have nothing directly todo with the notification of new mails arrived. I played with the values around. And the courios is, in thunderbird the folloing. set to 30 seconds. Thunderbird pop up around 25 seconds after the message is deliverd to the inbox. set to 60 seconds. Thunderbird pup up around 50 seconds after the message is deliverd to the inbox. I switch over from archiveopteryx, where no such delay was. Regards, Ingo
Re: [Dovecot] HA Dovecot Config?
Quoting Rick Romero : They claim to be real-time, and with kernel hooks into reads/writes, it seems promising to run on top of the OS.. Yes, but that doesn't mean it will work in the cluster environment... It also says things like: There are different types of file locks. In addition to these differences, each OS has its own set of rules regarding file locks as well. FRP's replication of locked files will vary in relation to the way the OS treats these types. However, one rule is consistent throughout all operating systems in that exclusive file locks will prevent FRP from replicating data. See that last line there??? Want to bet something in the mail setup (MTA, dovecot, system jobs like backup, etc) put an exclusive lock on files from time to time? Again, a fine backup system, and depending on your needs it might be okay for a failover setup, but not for an active-active setup. For that you need a lock manager, which they promise "in the future" but don't deliver yet... Rick -- Eric Rostetter The Department of Physics The University of Texas at Austin Go Longhorns!
Re: [Dovecot] [sendmail] deliver+sieve: Destination address (-a) parsing changes
"Frank Behrens" wrote: > Andrzej Adam Filip wrote on 21 Oct 2009 9:21: >> It is possible to "significantly" twist sendmail.cf use $h to select >> dovecot's mailbox and $u to pass user+det...@domain (one *or many*). >> [ BTW the way I think about will make sendmail support "aliases with >> domains" instead of current "aliases after domain stripping"] >> >> It is not a big deal if: >> * all dovecot's mailboxes are owned by single non root OS account >> * sendmail is supposed to start dovecot-deliver with root privileges >> >> P.S. >> I have written a few sendmail.cf recipients intended to support more >> than "one and the only" local mailer. > > Fine, it sounds promising. So I will see, what I can do with a > modified rule set. May be it's a good idea to have a special dovecot > local mailer with matching envelope rewriting rules. [ I will continue sendmail related discussion in news:comp.mail.sendmail ] Dovecot's design issues to consider are as follows: a) making dovecot support hash/btree/dbm maps for passwd/userdb [AFAIR Timo stated it is too complicated to be "cost effective" from his perspective] b) making dovecot support sendmail's "socket map" protocol for checking mailbox existence The simple protocol is described in semdmail's doc/op/op.me file http://www.sendmail.org/doc/sendmail-current/doc/op/op.pdf c) making dovecot support LMTP protocol via unix socket -- [pl>en: Andrew] Andrzej Adam Filip : a...@onet.eu Prototype designs always work. -- Don Vonada
Re: [Dovecot] HA Dovecot Config?
Quoting Hugo Monteiro : Anyone used FileReplicationPro? I'm more interested in low bandwidth, 'cheaper', replication. Rick If data consistency isn't a must, you can always perform timed rsyncs. Yes, but if there is a lot of data, FileReplicationPro is more efficient than an rsync. Of course, rsync is cheaper... ;) R's, Hugo Monteiro. -- Eric Rostetter The Department of Physics The University of Texas at Austin Go Longhorns!
Re: [Dovecot] HA Dovecot Config?
Quoting "Eric Jon Rostetter" : Quoting Rick Romero : Anyone used FileReplicationPro? I'm more interested in low bandwidth, 'cheaper', replication. Might work for an active-failover setup, but since I use active-active I need something like DRBD instead. Personally I wouldn't trust it for cluster type situations, and I kind of doubt the authors would either though I could be wrong. Certainly a great choice for backups though... Depending on your needs, it might work for a failover node... They claim to be real-time, and with kernel hooks into reads/writes, it seems promising to run on top of the OS.. http://www.filereplicationpro.com/sol-branch-office-sync.cfm Maybe I should voice my assumption that a Maildir mailbox would only be accessed from one server at a time, not both, and Dovecot indexes would be local and not replicated. And I suppose I'm assuming small files - which is probably the biggest hole in this active/active theory. Rick
Re: [Dovecot] HA Dovecot Config?
Quoting Rick Romero : Anyone used FileReplicationPro? I'm more interested in low bandwidth, 'cheaper', replication. Might work for an active-failover setup, but since I use active-active I need something like DRBD instead. Personally I wouldn't trust it for cluster type situations, and I kind of doubt the authors would either though I could be wrong. Certainly a great choice for backups though... Depending on your needs, it might work for a failover node... Rick -- Eric Rostetter The Department of Physics The University of Texas at Austin This message is provided "AS IS" without warranty of any kind, either expressed or implied. Use this message at your own risk.
Re: [Dovecot] [sendmail] deliver+sieve: Destination address (-a) parsing changes
Andrzej Adam Filip wrote on 21 Oct 2009 9:21: > It is possible to "significantly" twist sendmail.cf use $h to select > dovecot's mailbox and $u to pass user+det...@domain (one *or many*). > [ BTW the way I think about will make sendmail support "alises with > domains" instead > of current "aliases after domain stripping"] > > It is not a big deal if: > * all dovecot's mailboxes are owned by single non root OS account > * sendmail is supposed to start dovecot-deliver with root privileges > > P.S. > I have written a few sendmail.cf recipients intended to support more > than "one and the only" local mailer. Fine, it sounds promising. So I will see, what I can do with a modified rule set. May be it's a good idea to have a special dovecot local mailer with matching envelope rewriting rules. Thanks! Frank -- Frank Behrens, Osterwieck, Germany PGP-key 0x5B7C47ED on public servers available.
Re: [Dovecot] NFS random redirects
On 10/21/09 8:59 AM, "Guy" wrote: > Our current setup uses two NFS mounts accessed simultaneously by two > servers. Our load balancing tries to keep a user on the same server whenever > possible. Initially we just had roundrobin load balancing which led to index > corruption. > The problems we've had with that corruption have simply been that some > messages are displayed twice or not displayed at all in mail clients. > Deletion of the corrupted index allowed Dovecot to recreate it correctly, so > the client can't do anything about it. You'd probably have to do it manually > or have some sort of web interface for users to do it themselves. > > I certainly wouldn't use NFS with multiple servers accessing it again for > Dovecot. Looking at a clustered FS on SAN solution at the moment. As a contrasting data point, we run NFS + random redirects with almost no problems. We host ~7TB of mail for ~45k users with a peak connection count of 10k IMAP connections, and maybe a handful of POP3. We make absolutely no effort to make sure that connections from the same user or IP are routed to the same server. We do occasionally see index corruption, but it is almost always related to the user going over quota, and Dovecot being unable to write to the logs. If we wanted to solve this problem, we could move the indexes off to a second tier of storage. It is a very minor issue though. Locking has not been a problem at all. I will say that this may be a situation where you get what you pay for. We've invested a fair amount of money in our storage system (Netapp), server pool (RHEL5), and networking technology (F5 BigIP LTM). Our mail is spread across 16 volumes on two filers, and we are careful to stress-test the servers and storage backend before rolling out major upgrades. That is not of course to neglect the value of things that are free - like Dovecot! Many thanks to Timo for maintaining such a wonderful piece of software! -Brad
Re: [Dovecot] NFS random redirects
2009/10/21 Timo Sirainen > On Oct 20, 2009, at 4:47 AM, Thomas Hummel wrote: > > If you do it, you'll most likely see some random index related errors. >>> >> >> But are index related errors recoverable (does dovecot notice and fix it >> dynamically ?) or will they cause client-side corruption ? >> >> How bad would that corruption be ? (like fetching wrong message, since >> index >> store nextuid as well ? setting wrong flag ? ...) and how could a client >> fix it ? >> > > It's unlikely that anything bad happens, but who knows. Random unnoticed > corruption can do pretty much anything. > Our current setup uses two NFS mounts accessed simultaneously by two servers. Our load balancing tries to keep a user on the same server whenever possible. Initially we just had roundrobin load balancing which led to index corruption. The problems we've had with that corruption have simply been that some messages are displayed twice or not displayed at all in mail clients. Deletion of the corrupted index allowed Dovecot to recreate it correctly, so the client can't do anything about it. You'd probably have to do it manually or have some sort of web interface for users to do it themselves. I certainly wouldn't use NFS with multiple servers accessing it again for Dovecot. Looking at a clustered FS on SAN solution at the moment. Cheers Guy -- Don't just do something...sit there!
Re: [Dovecot] NFS random redirects
On Oct 20, 2009, at 4:47 AM, Thomas Hummel wrote: If you do it, you'll most likely see some random index related errors. But are index related errors recoverable (does dovecot notice and fix it dynamically ?) or will they cause client-side corruption ? How bad would that corruption be ? (like fetching wrong message, since index store nextuid as well ? setting wrong flag ? ...) and how could a client fix it ? It's unlikely that anything bad happens, but who knows. Random unnoticed corruption can do pretty much anything. caches.. So I've added some highly OS-specific code that works most of the time, but not perfectly. It works best with Linux. Ouch! I run dovecot on FreeBSD ;-( FreeBSD's NFS seems to be among the worst.. imaptest exists now in http://imapwiki.org/ImapTest Thanks. Sorry I didn't find it. Do you have any suggestion to test specifically nfs corruption chances ? Not really. Just running the stress test on the same mailbox in 2+ NFS clients should start showing the problems somewhat soon if they are any. Actual mail content should be safe. Unless you just happen to get such a cache file corruption that Dovecot doesn't notice it and sends some broken headers to IMAP client. If that happened, with Maildir, the actual content on disk on server wouldn't be corrupted I guess, Right. so I would that be recoverable on the client ? If anything else fails, clearing client caches (or recreating the account on client side) should work, yes.
Re: [Dovecot] Maildir autocreation
On Oct 21, 2009, at 11:09 AM, Proskurin Kirill wrote:
No. :-(
#fgrep 'mail_location' /usr/local/etc/dovecot.conf | fgrep -v #
mail_location = maildir:/var/spool/dovecot/domains/%d/%n
mail_location = /var/spool/dovecot/domains/%d/%n/
Second hit - it is a sieve rules part.
What do you mean? The second one in plugin {} overrides the first one.
Re: [Dovecot] Maildir autocreation
Hugo Monteiro wrote: Proskurin Kirill wrote: Pascal Volk wrote: On 10/21/2009 01:08 PM Proskurin Kirill wrote: Hello. Today i found what maildir autocreation stop work. May be after upgrade to 1.2. Here logs: … Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: maildir autodetect: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa//cur) failed: No such file or directory Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: mbox autodetect: data=/var/spool/dovecot/domains/fxclub.org/shershov-oa/ Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: mbox autodetect: INBOX file: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa/) failed: No such file or directory Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: mbox autodetect: has .imap/: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa//.imap) failed: No such file or directory Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: mbox autodetect: has inbox: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa//inbox) failed: No such file or directory Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: mbox autodetect: has mbox: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa//mbox) failed: No such file or directory Oct 21 11:01:25 deliver(shershov...@fxclub.org): Error: mail_location: Ambiguous mail location setting, don't know what to do with it: /var/spool/dovecot/domains/fxclub.org/shershov-oa/ (try prefixing it with mbox: or maildir:) Oct 21 11:01:25 deliver(shershov...@fxclub.org): Fatal: Namespace initialization failed dovecot -n # 1.2.4: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.1-RELEASE-p7 i386 ufs base_dir: /var/run/dovecot/ … login_process_size: 128 login_processes_count: 20 login_max_processes_count: 512 mail_location: ??? mail_max_userip_connections(default): 256 mail_max_userip_connections(imap): 256 mail_max_userip_connections(pop3): 20 mail_max_userip_connections(managesieve): 10 … mail_plugins(default): quota imap_quota autocreate mail_log mail_plugins(imap): quota imap_quota autocreate mail_log … plugin: … autocreate: Trash autocreate2: Sent autocreate3: Spam autosubscribe: Trash autosubscribe2: Sent autosubscribe3: Spam Your log excerpt shows excellently how hard Dovecot tries the figure out the mail_location. But that's not all. There is a very useful suggestion: try prefixing it with mbox: or maildir: It looks like your ldap userdb is returning a home field. So set for example mail_location = mailldir:~/Maildir in your dovecot.conf I have in Dovecot.conf: mail_location: maildir:/var/spool/dovecot/domains/%d/%n mail_location = maildir:/var/spool/dovecot/domains/%d/%n Can you see the difference? No. :-( #fgrep 'mail_location' /usr/local/etc/dovecot.conf | fgrep -v # mail_location = maildir:/var/spool/dovecot/domains/%d/%n mail_location = /var/spool/dovecot/domains/%d/%n/ Second hit - it is a sieve rules part. -- Best regards, Proskurin Kirill
Re: [Dovecot] Maildir autocreation
Proskurin Kirill wrote: Pascal Volk wrote: On 10/21/2009 01:08 PM Proskurin Kirill wrote: Hello. Today i found what maildir autocreation stop work. May be after upgrade to 1.2. Here logs: … Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: maildir autodetect: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa//cur) failed: No such file or directory Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: mbox autodetect: data=/var/spool/dovecot/domains/fxclub.org/shershov-oa/ Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: mbox autodetect: INBOX file: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa/) failed: No such file or directory Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: mbox autodetect: has .imap/: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa//.imap) failed: No such file or directory Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: mbox autodetect: has inbox: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa//inbox) failed: No such file or directory Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: mbox autodetect: has mbox: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa//mbox) failed: No such file or directory Oct 21 11:01:25 deliver(shershov...@fxclub.org): Error: mail_location: Ambiguous mail location setting, don't know what to do with it: /var/spool/dovecot/domains/fxclub.org/shershov-oa/ (try prefixing it with mbox: or maildir:) Oct 21 11:01:25 deliver(shershov...@fxclub.org): Fatal: Namespace initialization failed dovecot -n # 1.2.4: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.1-RELEASE-p7 i386 ufs base_dir: /var/run/dovecot/ … login_process_size: 128 login_processes_count: 20 login_max_processes_count: 512 mail_location: ??? mail_max_userip_connections(default): 256 mail_max_userip_connections(imap): 256 mail_max_userip_connections(pop3): 20 mail_max_userip_connections(managesieve): 10 … mail_plugins(default): quota imap_quota autocreate mail_log mail_plugins(imap): quota imap_quota autocreate mail_log … plugin: … autocreate: Trash autocreate2: Sent autocreate3: Spam autosubscribe: Trash autosubscribe2: Sent autosubscribe3: Spam Your log excerpt shows excellently how hard Dovecot tries the figure out the mail_location. But that's not all. There is a very useful suggestion: try prefixing it with mbox: or maildir: It looks like your ldap userdb is returning a home field. So set for example mail_location = mailldir:~/Maildir in your dovecot.conf I have in Dovecot.conf: mail_location: maildir:/var/spool/dovecot/domains/%d/%n mail_location = maildir:/var/spool/dovecot/domains/%d/%n Can you see the difference? R's, Hugo Monteiro. -- ci.fct.unl.pt:~# cat .signature Hugo Monteiro Email: hugo.monte...@fct.unl.pt Telefone : +351 212948300 Ext.15307 Web : http://hmonteiro.net Centro de Informática Faculdade de Ciências e Tecnologia da Universidade Nova de Lisboa Quinta da Torre 2829-516 Caparica Portugal Telefone: +351 212948596 Fax: +351 212948548 www.ci.fct.unl.pt ap...@fct.unl.pt ci.fct.unl.pt:~# _
Re: [Dovecot] Maildir autocreation
Pascal Volk wrote: On 10/21/2009 01:08 PM Proskurin Kirill wrote: Hello. Today i found what maildir autocreation stop work. May be after upgrade to 1.2. Here logs: … Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: maildir autodetect: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa//cur) failed: No such file or directory Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: mbox autodetect: data=/var/spool/dovecot/domains/fxclub.org/shershov-oa/ Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: mbox autodetect: INBOX file: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa/) failed: No such file or directory Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: mbox autodetect: has .imap/: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa//.imap) failed: No such file or directory Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: mbox autodetect: has inbox: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa//inbox) failed: No such file or directory Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: mbox autodetect: has mbox: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa//mbox) failed: No such file or directory Oct 21 11:01:25 deliver(shershov...@fxclub.org): Error: mail_location: Ambiguous mail location setting, don't know what to do with it: /var/spool/dovecot/domains/fxclub.org/shershov-oa/ (try prefixing it with mbox: or maildir:) Oct 21 11:01:25 deliver(shershov...@fxclub.org): Fatal: Namespace initialization failed dovecot -n # 1.2.4: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.1-RELEASE-p7 i386 ufs base_dir: /var/run/dovecot/ … login_process_size: 128 login_processes_count: 20 login_max_processes_count: 512 mail_location: ??? mail_max_userip_connections(default): 256 mail_max_userip_connections(imap): 256 mail_max_userip_connections(pop3): 20 mail_max_userip_connections(managesieve): 10 … mail_plugins(default): quota imap_quota autocreate mail_log mail_plugins(imap): quota imap_quota autocreate mail_log … plugin: … autocreate: Trash autocreate2: Sent autocreate3: Spam autosubscribe: Trash autosubscribe2: Sent autosubscribe3: Spam Your log excerpt shows excellently how hard Dovecot tries the figure out the mail_location. But that's not all. There is a very useful suggestion: try prefixing it with mbox: or maildir: It looks like your ldap userdb is returning a home field. So set for example mail_location = mailldir:~/Maildir in your dovecot.conf I have in Dovecot.conf: mail_location: maildir:/var/spool/dovecot/domains/%d/%n And in dovecot-ldap.conf: user_attrs = mailQuotaSize=quota_rule=*:storage=%$M ,=uid=1002,=gid=1002,=home=/var/spool/dovecot/domains/%d/%n -- С уважением, Проскурин Кирилл +7(495)727-06-26 доб. 1070
Re: [Dovecot] Maildir autocreation
On 10/21/2009 01:08 PM Proskurin Kirill wrote: > Hello. > > Today i found what maildir autocreation stop work. > May be after upgrade to 1.2. Here logs: > … > Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: maildir autodetect: > stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa//cur) failed: No such > file or directory > Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: mbox autodetect: > data=/var/spool/dovecot/domains/fxclub.org/shershov-oa/ > Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: mbox autodetect: INBOX > file: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa/) failed: No > such file or directory > Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: mbox autodetect: has > .imap/: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa//.imap) > failed: No such file or directory > Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: mbox autodetect: has > inbox: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa//inbox) failed: > No such file or directory > Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: mbox autodetect: has > mbox: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa//mbox) failed: > No such file or directory > Oct 21 11:01:25 deliver(shershov...@fxclub.org): Error: mail_location: > Ambiguous mail location setting, don't know what to do with it: > /var/spool/dovecot/domains/fxclub.org/shershov-oa/ (try prefixing it with > mbox: or maildir:) > Oct 21 11:01:25 deliver(shershov...@fxclub.org): Fatal: Namespace > initialization failed > > dovecot -n > # 1.2.4: /usr/local/etc/dovecot.conf > # OS: FreeBSD 7.1-RELEASE-p7 i386 ufs > base_dir: /var/run/dovecot/ > … > login_process_size: 128 > login_processes_count: 20 > login_max_processes_count: 512 mail_location: ??? > mail_max_userip_connections(default): 256 > mail_max_userip_connections(imap): 256 > mail_max_userip_connections(pop3): 20 > mail_max_userip_connections(managesieve): 10 > … > mail_plugins(default): quota imap_quota autocreate mail_log > mail_plugins(imap): quota imap_quota autocreate mail_log > … > plugin: >… >autocreate: Trash >autocreate2: Sent >autocreate3: Spam >autosubscribe: Trash >autosubscribe2: Sent >autosubscribe3: Spam Your log excerpt shows excellently how hard Dovecot tries the figure out the mail_location. But that's not all. There is a very useful suggestion: try prefixing it with mbox: or maildir: It looks like your ldap userdb is returning a home field. So set for example mail_location = mailldir:~/Maildir in your dovecot.conf Regards, Pascal -- The trapper recommends today: deadbeef.0929...@localdomain.org
Re: [Dovecot] HA Dovecot Config?
Original-Nachricht > Datum: Wed, 21 Oct 2009 07:42:14 -0500 > Von: "Rick Romero" > An: "Dovecot Mailing List" , "Seth Mattinen" > > CC: dovecot@dovecot.org > Betreff: Re: [Dovecot] HA Dovecot Config? > Quoting "Seth Mattinen" : > > > Eric Rostetter wrote: > >> > >> For IMAP to be truely HA, you will need shared storage of some sort. > >> > >> > >> You can "emulate" a SAN with something like DRBD if budget doesn't > allow a > >> real SAN (that is what I do). > >> > > > > I can vouch for DRBD too. It works quite well. > > > > ~Seth > > > > > > Anyone used FileReplicationPro? I'm more interested in low > bandwidth, 'cheaper', replication. > I have never used FileReplicationPro but looking at what it offers it reminds me of GlusterFS. I use GlusterFS for all www data of the domains I host. I don't use jet GlusterFS for IMAP/POP storage for all domains I host. Only a small subset of the domains I host have GlusterFS for IMAP/POP but so far it works without issues and I will soon or later migrate the other domains to be on GlusterFS as well. The setup of GlusterFS is ultra easy (compared to other clustering FS solution I have seen) and it offers some very nice functions. In the past I have burned my fingers with older GlusterFS releases when I have tried to use it as storage for IMAP/POP but the later 2.0.x releases of GlusterFS are more stable. > Rick > Steve -- Neu: GMX DSL bis 50.000 kBit/s und 200,- Euro Startguthaben! http://portal.gmx.net/de/go/dsl02
Re: [Dovecot] HA Dovecot Config?
Rick Romero wrote: Quoting "Seth Mattinen" : Eric Rostetter wrote: For IMAP to be truely HA, you will need shared storage of some sort. You can "emulate" a SAN with something like DRBD if budget doesn't allow a real SAN (that is what I do). I can vouch for DRBD too. It works quite well. ~Seth Anyone used FileReplicationPro? I'm more interested in low bandwidth, 'cheaper', replication. Rick If data consistency isn't a must, you can always perform timed rsyncs. R's, Hugo Monteiro. -- ci.fct.unl.pt:~# cat .signature Hugo Monteiro Email: hugo.monte...@fct.unl.pt Telefone : +351 212948300 Ext.15307 Web : http://hmonteiro.net Centro de Informática Faculdade de Ciências e Tecnologia da Universidade Nova de Lisboa Quinta da Torre 2829-516 Caparica Portugal Telefone: +351 212948596 Fax: +351 212948548 www.ci.fct.unl.pt ap...@fct.unl.pt ci.fct.unl.pt:~# _
Re: [Dovecot] HA Dovecot Config?
Quoting "Seth Mattinen" : Eric Rostetter wrote: For IMAP to be truely HA, you will need shared storage of some sort. You can "emulate" a SAN with something like DRBD if budget doesn't allow a real SAN (that is what I do). I can vouch for DRBD too. It works quite well. ~Seth Anyone used FileReplicationPro? I'm more interested in low bandwidth, 'cheaper', replication. Rick
[Dovecot] Maildir autocreation
Hello. Today i found what maildir autocreation stop work. May be after upgrade to 1.2. Here logs: Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: Loading modules from directory: /usr/local/lib/dovecot/lda Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: Module loaded: /usr/local/lib/dovecot/lda/lib10_quota_plugin.so Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: Module loaded: /usr/local/lib/dovecot/lda/lib90_sieve_plugin.so Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: auth input: quota_rule=*:storage=2046M Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: auth input: uid=1002 Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: auth input: gid=1002 Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: auth input: home=/var/spool/dovecot/domains/fxclub.org/shershov-oa Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: Home dir not found: /var/spool/dovecot/domains/fxclub.org/shershov-oa Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: Quota root: name= backend=maildir args= Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: Quota rule: root= mailbox=* bytes=2145386496 messages=0 Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: Quota rule: root= mailbox=Trash bytes=1317011456 messages=0 Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: Quota rule: root= mailbox=SPAM ignored Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: Quota warning: bytes=2038117171 (95%) messages=0 command=/usr/local/bin/quota-warning.sh 95 Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: Quota warning: bytes=1716309196 (80%) messages=0 command=/usr/local/bin/quota-warning.sh 80 Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: maildir autodetect: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa//cur) failed: No such file or directory Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: mbox autodetect: data=/var/spool/dovecot/domains/fxclub.org/shershov-oa/ Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: mbox autodetect: INBOX file: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa/) failed: No such file or directory Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: mbox autodetect: has .imap/: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa//.imap) failed: No such file or directory Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: mbox autodetect: has inbox: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa//inbox) failed: No such file or directory Oct 21 11:01:25 deliver(shershov...@fxclub.org): Info: mbox autodetect: has mbox: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa//mbox) failed: No such file or directory Oct 21 11:01:25 deliver(shershov...@fxclub.org): Error: mail_location: Ambiguous mail location setting, don't know what to do with it: /var/spool/dovecot/domains/fxclub.org/shershov-oa/ (try prefixing it with mbox: or maildir:) Oct 21 11:01:25 deliver(shershov...@fxclub.org): Fatal: Namespace initialization failed dovecot -n # 1.2.4: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.1-RELEASE-p7 i386 ufs base_dir: /var/run/dovecot/ log_path: /var/log/dovecot/dovecot.log info_log_path: /var/log/dovecot/dovecot-debug.log protocols: imap imaps pop3 pop3s managesieve listen(default): * listen(imap): * listen(pop3): * listen(managesieve): *:2000 ssl_ca_file: /usr/local/etc/certs/GlobalSignCA.crt ssl_cert_file: /usr/local/etc/certs/fxclub_org.crt ssl_key_file: /usr/local/etc/certs/fxclub_org.key ssl_cipher_list: ALL:!LOW:!SSLv2 login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_executable(managesieve): /usr/local/libexec/dovecot/managesieve-login login_process_size: 128 login_processes_count: 20 login_max_processes_count: 512 mail_max_userip_connections(default): 256 mail_max_userip_connections(imap): 256 mail_max_userip_connections(pop3): 20 mail_max_userip_connections(managesieve): 10 verbose_proctitle: yes first_valid_gid: 0 mail_privileged_group: mail mail_uid: dmail mail_gid: dmail mail_location: maildir:/var/spool/dovecot/domains/%d/%n mail_debug: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_executable(managesieve): /usr/local/libexec/dovecot/managesieve mail_process_size: 512 mail_plugins(default): quota imap_quota autocreate mail_log mail_plugins(imap): quota imap_quota autocreate mail_log mail_plugins(pop3): quota mail_plugins(managesieve): mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 mail_plugin_dir(managesieve): /usr/local/lib/dovecot/managesieve imap_client_workarounds(default): delay-newmail tb-extra-mailbox-sep imap_client_workarounds(imap): d
Re: [Dovecot] Courier to dovecot migration issue
Problem was solve Thank you.
Re: [Dovecot] NFS random redirects
On Tue, Oct 20, 2009 at 10:47:25AM +0200, Thomas Hummel wrote: > > Actual mail content should be safe. So you seem to say that indexes files would probably get "corrupted" but that clients wouldn't notice it ? I'm trying to figure out how to use imap-test test script-ing to test this. Any suggestion what the test file should look like ? Thanks. -- Thomas Hummel | Institut Pasteur | Pôle informatique - systèmes et réseau
Re: [Dovecot] [sendmail] deliver+sieve: Destination address (-a) parsing changes
"Frank Behrens" wrote: > When I upgraded my old, long running dovecot 1.1 to newer dovecot-1.2.4 + > doevecot-sieve- > 0.1.12 I observed a change in destination address (-a) parsing. > > Old behaviour: > When Timo introduced this feature > (http://www.dovecot.org/list/dovecot/2007-September/025813.html) > it was possible to hand over only the detail part. In my sendmail > configuration I used "-a +$h", > where $h contains the detail part and may be empty. By default sendmail can > call the delivery > agent with the following information: > $u: The recipient user (always set) > $h: Detail part, may be empty > $g: The sender address (relative to the recipient). > > New behaviour: > The current sieve version needs a complete address with local- and > domain-part. Otherwise we get a warning like > deliver(user): sieve: envelope recipient address 'user' is unparseable. > > The problem is, that the domain part is not always available, e.g. for > local delivered emails. This is the main problem, although the setup > could be simplified if deliver would accept the old syntax. I'm going > to make modifications to sendmail to be able to have all address > information available, but this will not solve the problem with > missing domain. > > Now comes my question: Is it better to enhance the address parsing in > sieve plugin or should I use a wrapper around deliver? The latter is > not very difficult, but introduces an additional process (that may > fail). It is possible to "significantly" twist sendmail.cf use $h to select dovecot's mailbox and $u to pass user+det...@domain (one *or many*). [ BTW the way I think about will make sendmail support "alises with domains" instead of current "aliases after domain stripping"] It is not a big deal if: * all dovecot's mailboxes are owned by single non root OS account * sendmail is supposed to start dovecot-deliver with root privileges P.S. I have written a few sendmail.cf recipients intended to support more than "one and the only" local mailer. -- [pl>en: Andrew] Andrzej Adam Filip : a...@onet.eu CF&C stole it, fair and square. -- Tim Hahn
Re: [Dovecot] HA Dovecot Config?
Eric Rostetter wrote: > > For IMAP to be truely HA, you will need shared storage of some sort. > > > You can "emulate" a SAN with something like DRBD if budget doesn't allow a > real SAN (that is what I do). > I can vouch for DRBD too. It works quite well. ~Seth
Re: [Dovecot] testing needed
On Tue, Oct 20, 2009 at 12:55 AM, Timo Sirainen wrote: > Can someone find an OS where the attached program doesn't work? It > should print "success". So far tested for success: Linux 2.6, Solaris > 10, FreeBSD 7.2, OpenBSD 4.2. > > FreeBSD 6.4 --> success -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ "If you have nothing good to say about someone, just shut up!." -- Lucky Dube
