[Dovecot] behavior of dovecot with Openldap
Dear team, I'm sorry if this is a stupid question, but I'd like to know the behavior of dovecot in a particular stuation. My questions are as follows. In /etc/dovecot-ldap.conf, 'hosts=' field is the one which can be used to specify availabled ldap server to access from the clients to authorize. And also sevral ldap servers can be specified in 'hosts =' field as shown like below. hosts = ldap-server1.example.com ldap-server2.example.com ※both server have the same configuration and available to replication ldap-server1(master) to ldap-server2(slave). If this is right, how does dovecot know which ldap server is currently used? and if the master dies, how does dovecot know and switch to slave one? In addition, which one is the exact behavior of dovecot in case master server dies? 1. only swithcing to the slave server 2. switching to the slave server, and once the master server is reactive then switch back to the master server automatically OS：RHEL4 U3 kernel 2.6.9-34.ELsmp openldap-2.2.13-12.el4 Thanks in advance, Masaharu Kawada --- Masaharu Kawada Associate Global Support Engineer Red Hat K K Ebisu Neonato 8F 1-18 Ebisu 4-chome, Shibuya-ku Tokyo 150-0013, Japan Direct: +81-3-5798-8482
Re: [Dovecot] autocreate bug with 1.2 solved
Timo Sirainen schrieb: On Jan 18, 2009, at 7:45 PM, Robert Schetterer wrote: Hi Timo i found the bug with autocreate in dovecot 1.2 last weeks i tested a lot with namespaces i finally declared shared namespace before private namespace in dovecot.conf by doing a lot of copy paste namespace test variants getting autocreate to work i finally copied my private namespace declaration above the shared namespace in dovecot.conf and now its working. Fixed: http://hg.dovecot.org/dovecot-1.2/rev/8b3af54b4dc3 Also fixed the listescape plugin breaking it: http://hg.dovecot.org/dovecot-1.2/rev/a498c440eef2 Hi Timo, youre great , i will test this soon -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria
Re: [Dovecot] deliver rejection bounces
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 18 Jan 2009, Seth Mattinen wrote: As a mail admin, I never want to see deliver generating its own messages to potentially forged addresses and spamming innocent people. The MTA should do this during the SMTP transaction. Which MTA tries to deliver the mail during the SMTP dialogue? Neither Postfix nor sendmail does, unfortunately. Well, one would open yet another can of worms, if doing so, I guess. Bye, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSXRG03WSIuGy1ktrAQIgyQf/Y4d/ofYXk4J+NbfEc3I7/ixz+nL0desO /k1lGLP+NrUcEOFFEXArA0HXVt+1qv83fY47MkeZNb6qem0v8s7Ywz09TEzO+jc+ fm0MZIZ+MsR/UnwSEoIrqmnUhatNz7hcHQ0I1RZ/JYWTfY0sVqADvuN6U61GbhE8 4TlRiNQ5S2iIFoWki15++KRZoHKjjJPbBrQxDe8GIC8VnnkbIocMvABZcYxGl2UB 9UXGY/2OLfd3L6Z5a/3E/gZ8KvUjwykb2aHjMcFdY+jLnuWR97lD1FK02dUBczpr ja4Hq1R2X/RwoikUkjeP6O0QBxDLojHxkOCOxlGLmstPKOPC8JRQxQ== =vN28 -END PGP SIGNATURE-
Re: [Dovecot] deliver rejection bounces
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 18 Jan 2009, Timo Sirainen wrote: Is there any reason not to make (for v1.2) 1) deliver -e behavior the defaut? 2) not even provide the option for the current default (have deliver send bounces itself)? I have no objections again 1) and 2). But as others said, to remove 2) removes flexibility, e.g. to localize bounce messages :) And you would need to rewrite lots of advices and documentation. I would defer 1) til v2.0 and add a mandatory option for the operation mode, e.g. if none is specified, deliver could comlpain with 'missing operation mode, did you forgot to specify --operation-mode bounce-self?' or something like that. Bye, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSXRIn3WSIuGy1ktrAQKbugf/cCYrWEOYTrLuBi3njWowrJCNAEa9A9Ut awwUm1B+NmfazJttabt0acW12MDmI85G/ZeOrZE/eUEBHmwBVzFoFcrukDp/Za0t bWWBeDkNZtN+hj5g5M/aTR2A3ycrMg1DLSm78WM9rmGh1ubGNFOigSXJ7VUXbgjo UcqWt2PjoTWUGJAFZE8PgHxX25EFt5cQkr7U7PoXUS/d8BqTzcI1/+SnscYH5XcJ cHMHP8Ere8+SWZIpedsaxnQuJ+9FtcsXHnUmQ7VRnMnj0aK47LOV4KYjell2fY2z lUDuo/r9lKLCxUQQKqjMVgjZV6dt9O7Sk+E9xqO64noeSh4azZIF8w== =gn7B -END PGP SIGNATURE-
Re: [Dovecot] deliver rejection bounces
On 1/18/2009 2:58 PM, Timo Sirainen wrote: 2) not even provide the option for the current default (have deliver send bounces itself)? I assume you mean respond with an smtp-reject? My understanding of 'bounces' is they should only ever be generated by the SENDERS MTA? -- Best regards, Charles
Re: [Dovecot] Dovecot discards mail over quota
On 1/18/2009 5:47 PM, Gary V wrote: The only functional difference I can see (at least as far as 'over quota' is concerned) is who sends the bounce (and subsequently - what message the bounce contains). If that's the case, it's a matter of which notification the mail admin prefers. Again... the only unit responsible for sending actual bounce messages is the SENDERS MTA. Your (receiving) MTA should only either ACCEPT (if so, NEVER generate a 'bounce' later), DEFER or REJECT. -- Best regards, Charles
Re: [Dovecot] deliver rejection bounces
You message was rejected by... no thank you, I do not want ever to see this: On M 19 Jan, 2009, at 10:24 , Steffen Kaiser wrote: On Sun, 18 Jan 2009, Seth Mattinen wrote: As a mail admin, I never want to see deliver generating its own messages to potentially forged addresses and spamming innocent people. The MTA should do this during the SMTP transaction. Which MTA tries to deliver the mail during the SMTP dialogue? Neither Postfix nor sendmail does, unfortunately. Well, one would open yet another can of worms, if doing so, I guess. he meant SMTP time reject, not bounces or NDR or whatever. Giuliano
Re: [Dovecot] Dovecot discards mail over quota
On Sun, Jan 18, 2009 at 12:26:46PM -0700, Gary V wrote: Just as a matter of interest. On my Postfix system: a) Using deliver -e, Postfix bounces the message immediately 5.7.0 - Subject: Undelivered Mail Returned to Sender. Partial body: t...@example.com: permission denied. Command output: Quota exceeded (mailbox for user is full). Postfix does not retain the message. b) quota_full_tempfail=yes: defers the message with 4.3.0. If the user makes room for the message, then it will eventually be delivered. If they don't, then _eventually_ a bounce will be sent. In this case the bounce is less informative. Partial body: t...@example.com: temporary failure. In the case where the message is not delivered, using default settings in Postfix, the sender will be notified 5 days after they sent the message. c) For over quota with a+b, it behaves the same way as b, but the bounce notice will be more informative: Partial body: t...@example.com: temporary failure. Command output: Quota exceeded (mailbox for user is full). I would say this is expected. You can also quota_exceeded_message to something like 4.2.2 Mailbox full (or 5.2.2 ...). This works whenever -e is specified, i.e. for a) and c), and you use Postfix 2.3 or later (see pipe(8)). Each of the four possibilites has advantages and disadvantages, and personally I think a) might be closest to doing the right thing, but it would be cool to have the option of deferring the mail (using option a+b) and additionally have deliver immediately send a message to the sender notifying them that their mail has been delayed due to the recipient being over quota. Something like: This is also easy with Postfix, if you use delay_warning_time (see postconf(5)).
[Dovecot] Coding question again...
Hello again,
I have a coding question again:
I can obtain the path of the current user's mailbox with the function
mail_storage_get_mailbox_path(...) - so far so good. But is it possible to get
this mailbox path for another user than the logged in one?
Thanks in advance.
Best regards.
Stefan
--
SIEGNETZ.IT GmbH
{ w3o-services }
Schneppenkauten 1a
D-57076 Siegen
Tel.: 0271 68193-0
Fax: 0271 68193-29
Geschäftsführer: Oliver Seitz
Handelsregister-Nummer: HRB4838
Registergericht: Amtsgericht Siegen
Das Wort “WINDOWS” stammt aus
einem alten Sioux-Dialekt und
bedeutet:
“Weißer Mann starrt durch
Glasscheibe auf Sanduhr.”
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Re: [Dovecot] deliver rejection bounces
Steffen Kaiser schrieb: On Sun, 18 Jan 2009, Seth Mattinen wrote: As a mail admin, I never want to see deliver generating its own messages to potentially forged addresses and spamming innocent people. The MTA should do this during the SMTP transaction. Which MTA tries to deliver the mail during the SMTP dialogue? Neither Postfix nor sendmail does, unfortunately. Well, one would open yet another can of worms, if doing so, I guess. Bye, -- Steffen Kaiser Depends what kind of bounce you mean i.e quota full bounce can be avoided by postfix with vda patch ( which isnt official supported by postfix hackers ) but you cant use an additional lda then ( so you may loose filter stuff ) but in fact if you look in your logs daily and have good Anitvirus and Antispam stuff integrated and setuped ,backscatters by lda are very rare, and mostly have easy solutions, like expand quota, deleting mailboxes etc so its like others said avoid to bounce to spam mails is the most stuff, i.e clamav-milter helps a lot killing worms etc on smtp income level, if sanesecurity is up again this will work again for known spam -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria
[Dovecot] losing emails in dovecot-uidlist
hi,
I have problems with the dovecot-uidlist in version 1.1.4 and 1.1.8.
I was using dovecot 1.1.4 and think, I fix it with new dovecot 1.1.8, but
still the same problem.
Here a discription to reconstruct the problem:
I have an fit dovecot-uidlist with one email in cur/ folder.
Now I try to append an email in this way:
A001 LOGIN USER PASSWORD
A001 OK Logged in.
A002 EXAMINE INBOX
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
* OK [PERMANENTFLAGS ()] Read-only mailbox.
* 1 EXISTS
* 0 RECENT
* OK [UIDVALIDITY 1232360001] UIDs valid
* OK [UIDNEXT 2] Predicted next UID
A002 OK [READ-ONLY] Select completed.
A003 APPEND INBOX {147}
+ OK
MIME-Version: 1.0
From: EMAIL
To: EMAIL
Subject: SDI1
Content-Type: text/plain; charset: ascii
Ignore.
* 1 EXPUNGE
* 2 EXISTS
* 2 RECENT
A003 OK [APPENDUID 1232360001 2] Append completed.
A004 LOGOUT
* BYE Logging out
A004 OK Logout completed.
After this I look into the dovecot-uidlist and I see this new email only!
The dovecot-uidlist is rewritten, but only this this new incoming email.
After login into mailbox, make a SELECT INBOX and NOOP, the
dovecot-uidlist is rewritten angain and add the old emails AT THE END of
the dovecot-uidlist.
And my question is, why dovecot EXPANGE the email in cur/ folder, remove
it from dovecot-uidlist and rewrite the dovecot-uidlist with the new
incoming email only.
So I lost the old email in the cur/ folder.
Thanks...
STEPHAN
Re: [Dovecot] imap-login: memory corruption
* Ralf Hildebrandt ralf.hildebra...@charite.de: Did that and recompiled, deactivated valgrind, let's see what happens. Right now I don't see any more libc related crashes. -- Ralf Hildebrandt (ralf.hildebra...@charite.de) snick...@charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de What's the most effective Windows NT remote management tool? A car.
Re: [Dovecot] deleted-to-trash plugin
Outlook 2007 allows you to change the destination of deleted items Check your outlook settings... On Jan 16, 2009, at 3:06 AM, Proskurin Kirill wrote: Hello. Our clients use damn Outlook 2007 and it is can not move deleted messages to Trash folder. As I see dovecot have a experemental plugin deleted-to-trash right for this thing. Im aware of word experemental. Could some one say - does it work good? Does it work with latest Dovecot? -- Best regards, Proskurin Kirill
Re: [Dovecot] deleted-to-trash plugin
Romer Ventura пишет: Outlook 2007 allows you to change the destination of deleted items Check your outlook settings... Well I search it but not found anything. I can do 2 things: Expunge all deleted on exit Expunge all deleted on folder change. On Jan 16, 2009, at 3:06 AM, Proskurin Kirill wrote: Hello. Our clients use damn Outlook 2007 and it is can not move deleted messages to Trash folder. As I see dovecot have a experemental plugin deleted-to-trash right for this thing. Im aware of word experemental. Could some one say - does it work good? Does it work with latest Dovecot? -- Best regards, Proskurin Kirill
Re: [Dovecot] Coding question again...
On Jan 19, 2009, at 7:30 AM, Stefan Jurisch wrote: I have a coding question again: I can obtain the path of the current user's mailbox with the function mail_storage_get_mailbox_path(...) - so far so good. But is it possible to get this mailbox path for another user than the logged in one? Only with v1.2 code. There you can create multiple users with mail_user_init().
Re: [Dovecot] Autocreate plugin
On Jan 19, 2009, at 7:12 AM, Proskurin Kirill wrote: I found what if you have a something like this: autocreate = Trash autocreate2 = Sent autocreate3 = Spam *Then I delete autocreate2 string* and... autocreate3 will not work. If I add autocreate2 - all work well. Yes it is seems to be right what they all must go after each otherm but if i have a 20 or 30 autocreate folders and i want to delete autocreate2 for example - all other from 3-20 will not work. For me it is seems like a bug. I think better to remove numbers from this plugin at all. The way it's currently coded doesn't make it easy to fix. The same problem exists for other plugins as well, such as quota. Fixing this will probably have to wait for configuration handling rewrite (v2.0).
Re: [Dovecot] behavior of dovecot with Openldap
On Jan 19, 2009, at 3:04 AM, Masaharu Kawada wrote: In /etc/dovecot-ldap.conf, 'hosts=' field is the one which can be used to specify availabled ldap server to access from the clients to authorize. And also sevral ldap servers can be specified in 'hosts =' field as shown like below. hosts = ldap-server1.example.com ldap-server2.example.com Dovecot simply passes these servers to the OpenLDAP library. It doesn't do anything with them itself. ※both server have the same configuration and available to replication ldap-server1(master) to ldap-server2(slave). If this is right, how does dovecot know which ldap server is currently used? and if the master dies, how does dovecot know and switch to slave one? I'm pretty sure that configuration will simply use both the servers all the time more or less randomly. Unless OpenLDAP library has some code that does something similar to what you're talking about, but somehow I doubt that.
Re: [Dovecot] deleted-to-trash plugin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Proskurin Kirill said the following on 19/01/09 16:06: Well I search it but not found anything. Outlook settings are a mess! In some tab of the Options menu, you should find a button that opens a window where you can specify the location of Special folders Ciao, luigi - -- / +--[Luigi Rosa]-- \ E` strano che per smettere di lavorare con Windows si debba premere 'start'. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkl0nqAACgkQ3kWu7Tfl6ZRx1ACeNPrDRFJYFp7bsQWrGXIyu408 YywAnioMaDqRsadBoLmqvAmz2pYoTMmb =EDoP -END PGP SIGNATURE-
Re: [Dovecot] losing emails in dovecot-uidlist
On Jan 19, 2009, at 9:39 AM, Stephan Dietrich wrote: After this I look into the dovecot-uidlist and I see this new email only! The dovecot-uidlist is rewritten, but only this this new incoming email. After login into mailbox, make a SELECT INBOX and NOOP, the dovecot-uidlist is rewritten angain and add the old emails AT THE END of the dovecot-uidlist. Do you see any errors logged? http://wiki.dovecot.org/Logging
Re: [Dovecot] Coding question again...
Hmm, okay... thanks. :-)
But this brings me to the following short question: is the 1.2 code stable
enough to be used productive? And when do you think might the first stable
release of the 1.2 come up?
On Mon, Jan 19, 2009 at 10:32:12AM -0500, Timo Sirainen wrote:
On Jan 19, 2009, at 7:30 AM, Stefan Jurisch wrote:
I have a coding question again:
I can obtain the path of the current user's mailbox with the function
mail_storage_get_mailbox_path(...) - so far so good. But is it possible to
get this mailbox path for another user than the logged in one?
Only with v1.2 code. There you can create multiple users with
mail_user_init().
--
SIEGNETZ.IT GmbH
{ w3o-services }
Schneppenkauten 1a
D-57076 Siegen
Tel.: 0271 68193-0
Fax: 0271 68193-29
Geschäftsführer: Oliver Seitz
Handelsregister-Nummer: HRB4838
Registergericht: Amtsgericht Siegen
Das Wort “WINDOWS” stammt aus
einem alten Sioux-Dialekt und
bedeutet:
“Weißer Mann starrt durch
Glasscheibe auf Sanduhr.”
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Re: [Dovecot] odd epoll() errors
Try to run 'cat /proc/sys/fs/epoll/max_user_instances' . It will propablly print 128 which is default on recent kernels. You need to raise to say 1024 using 'echo 1204 /proc/sys/fs/epoll/max_user_instances' or via sysctl. -- View this message in context: http://www.nabble.com/odd-epoll%28%29-errors-tp21208378p21542790.html Sent from the Dovecot mailing list archive at Nabble.com.
Re: [Dovecot] deliver rejection bounces
Steffen Kaiser wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 18 Jan 2009, Seth Mattinen wrote: As a mail admin, I never want to see deliver generating its own messages to potentially forged addresses and spamming innocent people. The MTA should do this during the SMTP transaction. Which MTA tries to deliver the mail during the SMTP dialogue? Neither Postfix nor sendmail does, unfortunately. Well, one would open yet another can of worms, if doing so, I guess. Postfix. Will it do it out of the box? No. You can add hooks to Postfix using the pre-queue content filter, milter, access policy delegation or patches so that it can respond with a defer/reject during the SMTP session. http://www.postfix.org/SMTPD_PROXY_README.html http://www.postfix.org/MILTER_README.html http://www.postfix.org/SMTPD_POLICY_README.html I'm sure there are tools out there developed to take advantage of these interfaces that do what I'm alluding to, but I don't know any off the top of my head and I can't share mine. ~Seth
Re: [Dovecot] deliver rejection bounces
Robert Schetterer wrote: Steffen Kaiser schrieb: On Sun, 18 Jan 2009, Seth Mattinen wrote: As a mail admin, I never want to see deliver generating its own messages to potentially forged addresses and spamming innocent people. The MTA should do this during the SMTP transaction. Which MTA tries to deliver the mail during the SMTP dialogue? Neither Postfix nor sendmail does, unfortunately. Well, one would open yet another can of worms, if doing so, I guess. Bye, -- Steffen Kaiser Depends what kind of bounce you mean i.e quota full bounce can be avoided by postfix with vda patch ( which isnt official supported by postfix hackers ) but you cant use an additional lda then ( so you may loose filter stuff ) but in fact if you look in your logs daily and have good Anitvirus and Antispam stuff integrated and setuped ,backscatters by lda are very rare, and mostly have easy solutions, like expand quota, deleting mailboxes etc so its like others said avoid to bounce to spam mails is the most stuff, i.e clamav-milter helps a lot killing worms etc on smtp income level, if sanesecurity is up again this will work again for known spam http://vda.sourceforge.net/ ~Seth
Re: [Dovecot] Coding question again...
On Mon, 2009-01-19 at 17:06 +0100, Stefan Jurisch wrote: Hmm, okay... thanks. :-) But this brings me to the following short question: is the 1.2 code stable enough to be used productive? It should be pretty good, but I don't know if there are many real world users yet. And when do you think might the first stable release of the 1.2 come up? The first beta will be released soon, I'm just waiting for one thing. When the v1.2.0 final is released depends on how much people will test v1.2 and how many bugs they find. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Coding question again...
Well, that sounds good. If this version is stable enough and the beta will come
soon, then it should be enough for us at the moment.
Perhaps you should know: we implement groupware servers for our customers, and
we like dovecot because it is quite easy to implement multidomain virtual
mailbox servers. But some of these customers want to use mailbox sharing (user
driven). The groupware supports this, and my work is to implement a plugin for
dovecot which provides this functionality. So we surely will try to do some
testing of the 1.2 on our own and hopefully help the product to become stable
soon.
So, I think we will try the 1.2... :-)
Thanks a lot for your advice! :-))
On Mon, Jan 19, 2009 at 11:53:18AM -0500, Timo Sirainen wrote:
On Mon, 2009-01-19 at 17:06 +0100, Stefan Jurisch wrote:
Hmm, okay... thanks. :-)
But this brings me to the following short question: is the 1.2 code
stable enough to be used productive?
It should be pretty good, but I don't know if there are many real world
users yet.
And when do you think might the first stable release of the 1.2 come
up?
The first beta will be released soon, I'm just waiting for one thing.
When the v1.2.0 final is released depends on how much people will test
v1.2 and how many bugs they find.
--
SIEGNETZ.IT GmbH
{ w3o-services }
Schneppenkauten 1a
D-57076 Siegen
Tel.: 0271 68193-0
Fax: 0271 68193-29
Geschäftsführer: Oliver Seitz
Handelsregister-Nummer: HRB4838
Registergericht: Amtsgericht Siegen
Das Wort “WINDOWS” stammt aus
einem alten Sioux-Dialekt und
bedeutet:
“Weißer Mann starrt durch
Glasscheibe auf Sanduhr.”
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Re: [Dovecot] Coding question again...
On Mon, 2009-01-19 at 18:16 +0100, Stefan Jurisch wrote: Well, that sounds good. If this version is stable enough and the beta will come soon, then it should be enough for us at the moment. Perhaps you should know: we implement groupware servers for our customers, and we like dovecot because it is quite easy to implement multidomain virtual mailbox servers. But some of these customers want to use mailbox sharing (user driven). The groupware supports this, and my work is to implement a plugin for dovecot which provides this functionality. So we surely will try to do some testing of the 1.2 on our own and hopefully help the product to become stable soon. So, I think we will try the 1.2... :-) v1.2 already has most of the shared mailbox functionality implemented (although not really documented outside this mailing list). Do you need more than it provides? signature.asc Description: This is a digitally signed message part
[Dovecot] Shared Mailboxes (symlink) and kmail: known issues?
Hi, are there any known issues with symlinked-shared-mailboxes and kmail? I use virtual users (LDAP), so there are no unix-permissions related problems here: all mailboxes are owned by the local user vmail. Each user maildir has some symlinks to shared mailboxes. This works fine if I use squirrelmail as a MUA. kmail instead seems to have some problems: if I save a mail into the shared-folder, the other users are seeing this new mail almost immediately. But if I delete(!) a mail from the shared-folder, the list of the other kmails remains untouch. Refreshing does nothing. I have to close kmail and restart. Is this related to some sort of wrong config of the shared mailboxes or is this a (known) dovecot - kmail problem? -- Wilhelm
Re: [Dovecot] deleted-to-trash plugin
Outlook 2007 allows you to change the destination of deleted items Check your outlook settings... On Jan 16, 2009, at 3:06 AM, Proskurin Kirill wrote: Hello. Our clients use damn Outlook 2007 and it is can not move deleted messages to Trash folder. As I see dovecot have a experemental plugin deleted-to-trash right for this thing. Im aware of word experemental. Could some one say - does it work good? Does it work with latest Dovecot? I don't think you are correct. In Outlook 2007 Microsoft added the ability to save your Sent Items to a server folder, but they have not added the ability to save your Deleted Items to a server folder. Jeff
Re: [Dovecot] deleted-to-trash plugin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Proskurin Kirill said the following on 19/01/09 16:06: Well I search it but not found anything. Outlook settings are a mess! In some tab of the Options menu, you should find a button that opens a window where you can specify the location of Special folders You are thinking of Outlook Express or Windows Mail. Outlook does not have a Special Folders setting. Jeff
[Dovecot] donations
Just wondering if you don't respond to donations or don't get notified?
Re: [Dovecot] deliver rejection bounces
On 1/19/2009 11:51 AM, Seth Mattinen wrote: http://vda.sourceforge.net/ Just realize using this patch will void the postfix warranty (you won't get much help on the postfix list)... -- Best regards, Charles
Re: [Dovecot] deliver rejection bounces
Charles Marcus wrote: On 1/19/2009 11:51 AM, Seth Mattinen wrote: http://vda.sourceforge.net/ Just realize using this patch will void the postfix warranty (you won't get much help on the postfix list)... I've never personally used it so i can't vouch for it (I prefer using a pre-queue interface) but just pointing it out. ~Seth
[Dovecot] checkpassword auth issues
Hi, ok, I'm am developing a new solution that includes dovecot, and will be wanting to use the latest sieve implementation, so I have chosen to start with 1.2 as the base. I had a working install of 1.1.8 installed, and got a checkpassword setup working properly with it to authenticate a user. I used the passdb to call checkpassword, and the prefetch userdb to tell it to use the values that I sent back from the checkpassword script... I compiled and installed 1.2.alpha5, and now my checkpassword does not seem to be working, and I can't figure out why. If I go back and install 1.1.8, it all works again... here is the dovecot -n : [r...@mta3 /local/logs]# dovecot -n # 1.2.alpha5: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.0-STABLE i386 log_path: /local/logs/dovecot.errors protocols: imap imaps pop3 pop3s disable_plaintext_auth: no login_dir: /usr/local/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 verbose_proctitle: yes first_valid_uid: 100 mail_uid: 100 mail_gid: 100 mail_location: maildir:%h/Maildir mail_debug: yes mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: 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_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 pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: username_translation: %@ username_format: %Lu verbose: yes debug: yes debug_passwords: yes passdb: driver: checkpassword args: /bin/checkpassword userdb: driver: prefetch and here is a snip of the logs that I get when trying to log in : dovecot: Jan 19 11:37:47 Info: auth(default): client in: AUTH 1 PLAIN service=imapsecured lip=209.132.1.203 rip=209.132.9.162 lport=993 rport=1053 dovecot: Jan 19 11:37:47 Info: auth(default): client out: CONT 1 dovecot: Jan 19 11:37:47 Info: auth(default): client in: CONT 1 AHRpbUBtdGEzLnNjYWxlZHN5c3RlbXMuY29tAENvbGRTdW4x dovecot: Jan 19 11:37:47 Info: auth(default): checkpassword(t...@mta3.scaledsystems.com,209.132.9.162): execute: /bin/checkpassword /usr/local/libexec/dovecot/checkpassword-reply dovecot: Jan 19 11:37:47 Info: auth(default): checkpassword(t...@mta3.scaledsystems.com,209.132.9.162): Received input: user=...@mta3.scaledsystems.com userdb_home=/home/mailboxes/data/30/t...@mta3.scaledsystems.com userdb_uid=100 userdb_gid=100 dovecot: Jan 19 11:37:47 Info: auth(default): checkpassword(t...@mta3.scaledsystems.com,209.132.9.162): Received no input dovecot: Jan 19 11:37:47 Info: auth(default): checkpassword(t...@mta3.scaledsystems.com,209.132.9.162): exit_status=2 dovecot: Jan 19 11:37:47 Error: auth(default): checkpassword(t...@mta3.scaledsystems.com,209.132.9.162): Child 43345 exited with status 2 As you can see, the checkpassword routine is indeed sending outthe userdb_home variable as well as the other necessary variables. Is it possible that checks for the return code from calling the checkpassword script have changed between the versions??? I currently exit the checkpassword script with _exit(0); to make the status 0 when it is successful, and I also set the AUTHORIZED environment variable to 2 as told... wierd thing is that it works in 1.1.8, but not in 1.2 Thanks, Tim.
[Dovecot] Reject message if user is over quota. 2/3 solution for Postfix w/ PostgreSQL
Hi,
according to the both discussions in the last few days I've tried to
find a solution for Postfix with a PostgreSQL back-end.
Its working nice for regular recipient addresses like u...@example.com
and addresses with an extension like user+...@example.com.
Alias addresses are currently ignored.
* An alias may expand into multiple destinations. If one of this
destinations is over quota Postfix will expose the destination
address from the alias
* An alias address may point to an external destination.
* Aliases, with just one internal destination maybe simple to expand
(homework ;-))
Maybe someone of you would provide ideas for handling alias addresses.
The procedure is designed for global quota settings. If one of you is
using quota settings per user, you have to modify the procedure.
Integrating in main.cf:
smtpd_recipient_restrictions =
...
reject_unlisted_recipient
check_recipient_access pgsql:/etc/postfix/virtual_global_quota_check.cf
...
virtual_global_quota_check.cf:
# The hosts that Postfix will try to connect to
hosts = localhost
# The user name and password to log into the pgsql server.
user = $Your_Postfix_database_user
password = $PASSWORD
# The database name on the servers.
dbname = mailsys
# The query
query = SELECT postfix_global_quota_check('%u', '%d', 10485760, 1000)
#quota limit in bytes ^
#quota limit in messages ---^
SQL:
CREATE OR REPLACE FUNCTION postfix_global_quota_check(
IN localpart varchar, IN the_domain varchar,
IN q_storbigint, IN q_msgs bigint) RETURNS TEXT
AS $$
DECLARE
result text := 'DUNNO';
-- remove extenstion from localpart (user+foo - user)
lpart varchar := (SELECT regexp_replace(localpart, E'\\+.*$', ''));
-- XXX how to handle alias addresses?
-- stop here if the destination is an external address
-- how to handle aliases with multiple destinations???
address varchar := lpart||'@'||the_domain;
storage bigint := (SELECT current FROM quota
WHERE username = address
AND path = 'quota/storage');
messages bigint := (SELECT current FROM quota
WHERE username = address
AND path = 'quota/messages');
BEGIN
--RAISE NOTICE 'users storage: % bytes', storage;
--RAISE NOTICE 'users message count: %', messages;
IF storage = q_stor THEN
result := '552 5.2.2 Quota exceeded (mailbox for user is full)';
ELSE
IF messages = q_msgs THEN
result := '552 5.2.2 Quota exceeded (mailbox for user is full)';
END IF;
END IF;
RETURN result;
END;
$$ LANGUAGE plpgsql STABLE
RETURNS NULL ON NULL INPUT
EXTERNAL SECURITY INVOKER;
GRANT SELECT ON quota TO $Your_Postfix_database_user;
Regards,
Pascal
--
Ubuntu is an ancient African word meaning “I can’t install Debian.”
-- unknown
Re: [Dovecot] deleted-to-trash plugin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeff Grossman said the following on 19/01/09 18:43: You are thinking of Outlook Express or Windows Mail. Outlook does not have a Special Folders setting. http://www.howtogeek.com/howto/microsoft-office/use-gmail-imap-in-microsoft-outlook-2007/ The settings are in the Account Settings / More settings / Folders That only allows you to select a server folder for the Sent Items. There is no way in Outlook to select a Deleted Items server folder. Jeff
Re: [Dovecot] donations
On Mon, 2009-01-19 at 11:44 -0800, Ed Ewing wrote: Just wondering if you don't respond to donations or don't get notified? I haven't even thought about it before. Maybe I should start doing it. Anyway: I did see a donation from you, thanks! signature.asc Description: This is a digitally signed message part
Re: [Dovecot] checkpassword auth issues
On Mon, 2009-01-19 at 12:17 -0800, Tim Traver wrote: Is it possible that checks for the return code from calling the checkpassword script have changed between the versions??? I currently exit the checkpassword script with _exit(0); to make the status 0 when it is successful, and I also set the AUTHORIZED environment variable to 2 as told... Don't set AUTHORIZED environment. It's only if you're using it as a userdb (but you're using prefetch). signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Shared Mailboxes (symlink) and kmail: known issues?
On Mon, 2009-01-19 at 18:32 +0100, Wilhelm Meier wrote: kmail instead seems to have some problems: if I save a mail into the shared-folder, the other users are seeing this new mail almost immediately. But if I delete(!) a mail from the shared-folder, the list of the other kmails remains untouch. Refreshing does nothing. I have to close kmail and restart. Is this related to some sort of wrong config of the shared mailboxes or is this a (known) dovecot - kmail problem? My guess is that kmail assumes it's the only client accessing the mailbox and doesn't bother handling IMAP notifications about expunged messages. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] redirecting temp email files to another directory
On Sun, 2009-01-18 at 23:32 -0800, JANE CUA wrote: sample temp files that gets create in /var/spool/mail -rw-- jane mail _43398509485894865jane I'm certain Dovecot didn't create this file at least directly. -rw-- jane mail jane.lock This is a dotlock and it can be created by Dovecot. You could also probably disable it. http://wiki.dovecot.org/MboxLocking http://wiki.dovecot.org/MailboxFormat/mbox I have put the squirrelmail+dovecot offline now. It's hard to simulate the problem when I am the only one testing it. The issues came about, when I put it up online and the users started to use it. Disabling it meaning remarking the following? #mbox_read_locks = fcntl #mbox_write_locks = dotlock fcntl You can disable dotlocks by setting: mbox_write_locks = fcntl But like the MboxLocking page says, you should make sure that the other software that accesses the mbox files also use fcntl locking. Otherwise you'll get corrupted files. other users create these files randomly as well in /var/spool/mail, / var/spool/mail is an NFS mount. Hmm. NFS is a pretty good suspect here. I know that in some situations it creates such temp files, although they're usually named .nfs.something. Are those files deleted or are they just lying around? What size do they have? The _* files go away but for the .lock files, some of them don't go away and if they don't go, users no longer receives new emails, but can still send out emails. The temp file with _* has 0 file size, I don't remember what the .lock size it, I will see if I can simulate this again. I guess the _* files are written when .lock file is deleted but another process still has the file open. But like I said, normally Linux uses .nfs prefix for them. I guess your kernel doesn't for some reason. Anyway you shouldn't have .lock files lying around. Sounds like Dovecot (or something else) is crashing which leaves them. Have you looked if there are error messages in logs? http://wiki.dovecot.org/Logging signature.asc Description: This is a digitally signed message part
Re: [Dovecot] checkpassword auth issues
Timo Sirainen wrote: On Mon, 2009-01-19 at 12:17 -0800, Tim Traver wrote: Is it possible that checks for the return code from calling the checkpassword script have changed between the versions??? I currently exit the checkpassword script with _exit(0); to make the status 0 when it is successful, and I also set the AUTHORIZED environment variable to 2 as told... Don't set AUTHORIZED environment. It's only if you're using it as a userdb (but you're using prefetch). Timo, Thanks. That did it...although I'm not sure why it worked ok in 1.1.8, but all fixed... Tim.
Re: [Dovecot] checkpassword auth issues
On Mon, 2009-01-19 at 14:51 -0800, Tim Traver wrote: Timo Sirainen wrote: On Mon, 2009-01-19 at 12:17 -0800, Tim Traver wrote: Is it possible that checks for the return code from calling the checkpassword script have changed between the versions??? I currently exit the checkpassword script with _exit(0); to make the status 0 when it is successful, and I also set the AUTHORIZED environment variable to 2 as told... Don't set AUTHORIZED environment. It's only if you're using it as a userdb (but you're using prefetch). Timo, Thanks. That did it...although I'm not sure why it worked ok in 1.1.8, but all fixed... v1.1 doesn't support userdb checkpassword at all and just ignores the AUTHORIZED environment. I improved the error message now: Child %s exited with status 2 (tried to use userdb-only checkpassword program for passdb?) signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Dovecot discards mail over quota
On 1/19/09, Ulrich Zehl wrote: On Sun, Jan 18, 2009 at 12:26:46PM -0700, Gary V wrote: Just as a matter of interest. On my Postfix system: a) Using deliver -e, Postfix bounces the message immediately 5.7.0 - Subject: Undelivered Mail Returned to Sender. Partial body: t...@example.com: permission denied. Command output: Quota exceeded (mailbox for user is full). Postfix does not retain the message. b) quota_full_tempfail=yes: defers the message with 4.3.0. If the user makes room for the message, then it will eventually be delivered. If they don't, then _eventually_ a bounce will be sent. In this case the bounce is less informative. Partial body: t...@example.com: temporary failure. In the case where the message is not delivered, using default settings in Postfix, the sender will be notified 5 days after they sent the message. c) For over quota with a+b, it behaves the same way as b, but the bounce notice will be more informative: Partial body: t...@example.com: temporary failure. Command output: Quota exceeded (mailbox for user is full). I would say this is expected. You can also quota_exceeded_message to something like 4.2.2 Mailbox full (or 5.2.2 ...). This works whenever -e is specified, i.e. for a) and c), and you use Postfix 2.3 or later (see pipe(8)). Each of the four possibilites has advantages and disadvantages, and personally I think a) might be closest to doing the right thing, but it would be cool to have the option of deferring the mail (using option a+b) and additionally have deliver immediately send a message to the sender notifying them that their mail has been delayed due to the recipient being over quota. Something like: This is also easy with Postfix, if you use delay_warning_time (see postconf(5)). Right, thank you so much. I thought there was something like delay_warning_time that could make c) a workable choice. In fact, now I remember setting that up on my production server (when I had one a year ago) so senders would get notified their mail was still queued: This is the mail system at host msa.example.com. # THIS IS A WARNING ONLY. YOU DO NOT NEED TO RESEND YOUR MESSAGE. # Your message could not be delivered for more than 1 hour(s). It will be retried until it is 3 day(s) old. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system t...@example.com: temporary failure. Command output: Quota exceeded (mailbox for user is full) -- Gary V
Re: [Dovecot] Dovecot discards mail over quota
Right, thank you so much. I thought there was something like delay_warning_time that could make c) a workable choice. In fact, now I remember setting that up on my production server (when I had one a year ago) so senders would get notified their mail was still queued: But then this creates an additional bounce message and Charles makes a valid point: Again... the only unit responsible for sending actual bounce messages is the SENDERS MTA. Your (receiving) MTA should only either ACCEPT (if so, NEVER generate a 'bounce' later), DEFER or REJECT. However, I remember setting delay_warning_time for the benefit of local domain senders, so they would get notification of delayed delivery. If this is added, bounces to non-local domain sender would be a side effect of deferring over-quota messages. At any rate, thanks. I now have a good picture of what all the options are. -- Gary V
Re: [Dovecot] behavior of dovecot with Openldap
Dear list, Thank you very much for your quick answer. This question is actually due to a phenomenon that the customer got about a month ago. For the detail of the phenomenon, please see bellow. ** -2008/11/16 The customer updated openldap package openldap-2.2.13-6.4E ⇒ openldap-2.2.13-12.el4 -2008/12/22 A problem happened, which doesn't need to be investigated this time, to the ldap server(server1), so that ldap service on server1 is temporary stopped and restarted. -2008/01/06 The customer rearized that authorize requests by dovecot clients was all failed, and to know the reason the customer did some investigation. As a result, it was because of that dovecot accessed to only another server(server2) to authorize and server2 had not been replicated any data from server1 since 2008/11/16 which was shown by the replication log on server2(the last update was 2008/11/16). The server2 was supposed to have the same data as server1's which was latest data at that time by replication. * For this reason, the customer wants to know why dovecot accessed only server2 since ldap package was updated on 2008/11/16 and also wants to know why replication had been failed after updating the package. However, since the customer is not able to provide ehough information for this phenomenon because of their security policy, the customer said that only he wants to know this time is what the trigger to switch to another ldap server(between server1 and server2) and the way to specify which ldap server to access from the client as he wants if possible, or the specification of dovecot for accessing ldap servers in case there are more than one ldap servers pointed on 'hosts=' field in /etc/dovecot-ldap.conf As you said, if both ldap servers are used ramdomly, it seems to be unusuall action that authorize request is failed all the time, it should be at least successful when authorizing by server1 since server1 has no problems after rebooting ldap service on 2008/12/22. I'm afraid, anything else that might be help or useful info to know the specification of dovecot? Thanks, Timo Sirainen さんは書きました: On Jan 19, 2009, at 3:04 AM, Masaharu Kawada wrote: In /etc/dovecot-ldap.conf, 'hosts=' field is the one which can be used to specify availabled ldap server to access from the clients to authorize. And also sevral ldap servers can be specified in 'hosts =' field as shown like below. hosts = ldap-server1.example.com ldap-server2.example.com Dovecot simply passes these servers to the OpenLDAP library. It doesn't do anything with them itself. ※both server have the same configuration and available to replication ldap-server1(master) to ldap-server2(slave). If this is right, how does dovecot know which ldap server is currently used? and if the master dies, how does dovecot know and switch to slave one? I'm pretty sure that configuration will simply use both the servers all the time more or less randomly. Unless OpenLDAP library has some code that does something similar to what you're talking about, but somehow I doubt that. -- --- Masaharu Kawada Associate Global Support Engineer Red Hat K K Ebisu Neonato 8F 1-18 Ebisu 4-chome, Shibuya-ku Tokyo 150-0013, Japan Direct: +81-3-5798-8482
[Dovecot] userdb didn't return a home directory with v1.1.7
Hi all, I am running Dovecot v1.1.7 in a relatively quiet and calm environment. Suddenly overnight cron job started throwing out errors like: /usr/sbin/dovecot --exec-mail ext /usr/lib/dovecot/expire-tool Error: userdb(us...@mail.example) didn't return a home directory Error: userdb(us...@mail.example) didn't return a home directory Indeed, running this command produces: - $ sudo /usr/sbin/dovecot --exec-mail ext /usr/lib/dovecot/expire-tool --test Error: userdb(us...@mail.example) didn't return a home directory Info: User lookup failed: us...@mail.example Error: userdb(us...@mail.example) didn't return a home directory Info: User lookup failed: us...@mail.example - Yet these mailboxes are valid, corresponding users can login, send and receive mail. Other mailboxes are OK, too. Where to to start looking? I found that similar error message with v1.1.6 is fixed in v1.1.7, but I am running v.1.1.7 already. Please see dovecot configuration attached. Thank you for your time, Ivars # 1.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.27-9-server i686 Ubuntu 8.10 ext3 base_dir: /var/run/dovecot/ syslog_facility: local1 protocols: imap imaps pop3 pop3s managesieve ssl_cert_file: /etc/certs/mail.mail.example.crt ssl_key_file: /etc/certs/mail.mail.example.key disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login login_user: postfix login_greeting: VDEAVK epasta serveris. login_processes_count: 2 first_valid_uid: 107 mail_location: maildir:/home/vmail/%d/%n mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): expire fts fts_squat antispam mail_plugins(imap): expire fts fts_squat antispam mail_plugins(pop3): expire mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve managesieve_implementation_string(default): dovecot managesieve_implementation_string(imap): dovecot managesieve_implementation_string(pop3): dovecot managesieve_implementation_string(managesieve): Cyrus timsieved v2.2.13 sieve_storage(default): sieve_storage(imap): sieve_storage(pop3): sieve_storage(managesieve): /etc/dovecot/sieve/ sieve(default): sieve(imap): sieve(pop3): sieve(managesieve): /home/vmail/sieve-scripts/%u.sieve auth default: mechanisms: PLAIN LOGIN user: vmail username_format: %...@mail.example verbose: yes passdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf userdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: sieve: /home/vmail/sieve-scripts/%u.sieve expire: Trash 30 Trash/* 30 Spam 60 expire_dict: proxy::expire fts: squat antispam_signature: X-DSPAM-Signature antispam_trash: trash;Trash;Deleted Items antispam_spam: Spam antispam_dspam_binary: /usr/bin/dspam antispam_dspam_args: --deliver=;--user;%u;-s antispam_mail_tmpdir: /tmp antispam_mail_sendmail: /usr/sbin/sendmail antispam_mail_spam: spam...@mail.example antispam_mail_notspam: notspam...@mail.example antispam_crm_binary: /bin/false dict: expire: mysql:/etc/dovecot/dovecot-dict-expire.conf
Re: [Dovecot] Coding question again...
Hello,
Yet I do not know, what functionality the 1.2 provides. In fact I just need an
implementation of the 4 IMAP commands MYRIGHTS, GETACL, SETACL and DELETEACL
and the ability for the user to share mailboxes himself by using these commands.
The groupware we distribute (Open-Xchange, perhaps you know it) implements this
folder sharing by providing a context menu where the user can set the folder
rights within his mailbox, and with this he can enable other users to access
his folders.
The description of the ACL-feature in the table of 1.2 on the roadmap was not
completely comprehendible for me, so I've been not quite sure, if dovecot can
do these things above.
But if you say, it can do, I would be able to stop the extra work and focus our
work on building the mail system on basis of dovecot 1.2.
What do you think? :-)
Best regards
Stefan
On Mon, Jan 19, 2009 at 12:19:17PM -0500, Timo Sirainen wrote:
On Mon, 2009-01-19 at 18:16 +0100, Stefan Jurisch wrote:
Well, that sounds good. If this version is stable enough and the beta will
come soon, then it should be enough for us at the moment.
Perhaps you should know: we implement groupware servers for our customers,
and we like dovecot because it is quite easy to implement multidomain
virtual mailbox servers. But some of these customers want to use mailbox
sharing (user driven). The groupware supports this, and my work is to
implement a plugin for dovecot which provides this functionality. So we
surely will try to do some testing of the 1.2 on our own and hopefully help
the product to become stable soon.
So, I think we will try the 1.2... :-)
v1.2 already has most of the shared mailbox functionality implemented
(although not really documented outside this mailing list). Do you need
more than it provides?
--
SIEGNETZ.IT GmbH
{ w3o-services }
Schneppenkauten 1a
D-57076 Siegen
Tel.: 0271 68193-0
Fax: 0271 68193-29
Geschäftsführer: Oliver Seitz
Handelsregister-Nummer: HRB4838
Registergericht: Amtsgericht Siegen
Das Wort “WINDOWS” stammt aus
einem alten Sioux-Dialekt und
bedeutet:
“Weißer Mann starrt durch
Glasscheibe auf Sanduhr.”
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Re: [Dovecot] behavior of dovecot with Openldap
Masaharu Kawada a écrit : I'm pretty sure that configuration will simply use both the servers all the time more or less randomly. Unless OpenLDAP library has some code that does something similar to what you're talking about, but somehow I doubt that. Here we use uris parameter instead of hosts, and we seems to have expected behaviour: dovecot is always using the first listed uri except if it doesn't respond (switch to the second) We can check it simply: first listed server have more than 200 simultaneous connexions daily, 2nd have only one per slave (replication thread) (we use the slave as first uri) Hope this helps. -- Geoffroy Desvernay signature.asc Description: OpenPGP digital signature
