Re: [Dovecot] Allow_nets + MySQL failing when using range notation
* 2008-05-15 07:36, Timo Sirainen wrote: > Fixed: http://hg.dovecot.org/dovecot-1.0/rev/71c02fdf1b59 Uploaded as 1.0.13-5, will hit unstable at the next dinstall run. Thanks for the patch, Timo. -- Fabio Tranchitella http://www.kobold.it Free Software Developer and Consultant http://www.tranchitella.it _ 1024D/7F961564, fpr 5465 6E69 E559 6466 BF3D 9F01 2BF8 EE2B 7F96 1564
Re: [Dovecot] deliver exits with status 89 on some but not all mails of a batch
Hi, On Tuesday 13 May 2008, Charles Marcus wrote: > Lots of nifty stuff (much improved performance for one thing) in the > impending 1.1 (currently at rc5)... > > If this is a new installation, it might be worth going ahead and > upgrading to it... I upgraded again, to 1.1rc5, mostly because of the improved sieve support (I need "include"), and so far it's working quite well. -- STAR Software (Shanghai) Co., Ltd.http://www.star-group.net/ Phone:+86 (21) 5427 7799 x 826 Fax: +86 (21) 6485 0071 PGP key: https://stshacom1.star-china.net/keys/patrick_nagel.asc Fingerprint: E09A D65E 855F B334 E5C3 5386 EF23 20FC E883 A005 signature.asc Description: This is a digitally signed message part.
Re: [Dovecot] Dovecot dying when deliver is called
MyGoddess wrote: Oh, yes, thank you. It think the issue comes because in a previous version, the info_log_path for the lda was copied from its log_path and not from the master info_log_path. I ran into this same problem - and it doesn't fail gracefully either - at least with 1.0.rc15-2etch4. If the permissions aren't there it shouldn't hang the calling MTA. The more I think about this - LDA really should be part of the MTA and not separate - I would love to see a dovecot switch in exim - "maildir_format = dovecot" which would simplify the permissions mess. With the wonders of GPLed code this is a possibility. Karl Schmidt EMail [EMAIL PROTECTED] Transtronics, Inc. WEB http://xtronics.com 3209 West 9th StreetPh (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 The whole point of this sentence is to make clear what the whole point of this sentence is. --Douglas R. Hofstadter
Re: [Dovecot] moving folders bug - rc4
On Thu, 15 May 2008, Anil wrote: I am fairly new to dovecot... I had a user who in outlook tried to move one of the folders into another folder but it crapped out. I kind of fear that Outlook sent the wrong IMAP commands. Can you reproduce this and keep a Dovecot rawlog of the IMAP session? -- Asheesh. -- Life, like beer, is merely borrowed. -- Don Reed
[Dovecot] moving folders bug - rc4
I am fairly new to dovecot... I had a user who in outlook tried to move one of the folders into another folder but it crapped out. User tried to move "Djans*" folders into Koi folder. The subscription seems to show the folder move but the actual data is still under ".ClickEats.Clients.Djans" instead of ".ClickEats.Clients.Koi.Djans*. How do I fix this? Thanks. [EMAIL PROTECTED]:/apps/mail/clickeats.com/juliam/Maildir# grep -i djan subscriptions ClickEats.Restaurants.Djan's ClickEats.Clients.Koi.Djans.Online Orders ClickEats.Clients.Koi.Djans [EMAIL PROTECTED]:/apps/mail/clickeats.com/juliam/Maildir# ls -a |grep -i djan .ClickEats.Clients.Djans .ClickEats.Clients.Djans.Online Orders .ClickEats.Restaurants.Djan's [EMAIL PROTECTED]:/apps/mail/clickeats.com/juliam/Maildir#
Re: [Dovecot] Automounted home dirs not working
At 10:29 AM -0400 5/15/08, Roy McMorran wrote: Timo Sirainen wrote: But it never succeeds on first try? Nope. If you enable more verbosity on automountd (-v -T?) does it correctly log all the chdir attempts? Anyway I've really no idea why it wouldn't work. Maybe try asking in some Solaris forums/lists if they can think of some reason. I've concluded it is some problem with this particular server. I build Dovecot on another Solaris 10 box, and over there the chdir to an automounted home directory works as expected every time. I guess I'll reinstall the OS on my test server now :-( It's definitely not a Dovecot problem, so sorry for the noise on the list. Thanks for all your help. One thing you might want to look at before reinstalling completely is your NFS config on both sides and the controls resident in the network in between. With Solaris 10, you particularly want to make sure that your client system is not trying to use NFS over TCP across a network that interferes with it or to a server that doesn't support it properly. (for definitions of "properly" that are based in the behavior of Solaris 10 as a client...) -- Bill Cole [EMAIL PROTECTED]
Re: [Dovecot] Time moved backwards
At 10:12 AM -0400 5/15/08, Neal Becker wrote: Problem I see is that an external script that *unconditionally* relaunches dovecot could be a terribly problem. It's better for dovecot to do it itself in this particular failure, because it's the only one who knows that it was just a date issue, and relaunching is safe. That certainly does not need to be the case. Dovecot does log the reason in a trivially parsed manner, so a purpose-built watchdog could rather easily detect this particular failure mode. One truly simple change that could be made that would facilitate restarting under this special situation would be to have a specific exit value for Dovecot self-destructing in a time reversal, so a model where a parent process (e.g. launchd) is playing the watchdog role could use the exit value to decide whether to relaunch. That would be less likely to run into conflict with existing practice than internal logic terminating the existing processes and relaunching. On the other hand, a more subtle handling of this issue internally without terminating at all is probably the best approach, since only Dovecot itself can really know whether an immediate relaunch after a time reversal is really safe or how to make it so. For the specific problem of "infant mortality" at boot time that initiated this thread, the best approach is still prevention. Dovecot is far from the only daemon that will run into trouble if time jumps backwards, and there are widely used approaches (such as blocking the startup procedure on a successful ntpdate and using sound hardware whose clock doesn't drift too much in the first place) that minimize the risk of time reversal after sensitive daemons have started. If the problem of time stepping backwards after boot is really *common* then it may well be a dangerous cosmetic approach to just make Dovecot auto-recover (internally or externally) because it happens to be the only daemon that watches for and reacts to such an event. It is impossible to prevent every backwards time step, but preventing the predictable cases system-wide is a sounder approach than making one daemon adapt to what should be a very rare event. -- Bill Cole [EMAIL PROTECTED]
Re: [Dovecot] Automounted home dirs not working
Timo Sirainen wrote: But it never succeeds on first try? Nope. If you enable more verbosity on automountd (-v -T?) does it correctly log all the chdir attempts? Anyway I've really no idea why it wouldn't work. Maybe try asking in some Solaris forums/lists if they can think of some reason. I've concluded it is some problem with this particular server. I build Dovecot on another Solaris 10 box, and over there the chdir to an automounted home directory works as expected every time. I guess I'll reinstall the OS on my test server now :-( It's definitely not a Dovecot problem, so sorry for the noise on the list. Thanks for all your help. Cheers, -r -- Roy McMorran Systems Administrator MDI Biological Laboratory [EMAIL PROTECTED]
Re: [Dovecot] thunderbird sane config (OT)
Moser wrote: > Isn't this one click at accessing the server the first time!? > "Accept this certificate permanently"? I think the certificate needs to be constructed in a certain way (include some CA parts? be signed with itself? not sure) before you can do this. I haven't made it work yet :-/. > But if you figured out, how to add it, let me know! :) Not yet. Will do.
Re: [Dovecot] dovecot developer documentation
On May 15, 2008, at 10:25 AM, Piotr Wadas wrote: I want to create some specific plugin for dovecot v1.1 (rc5). Where can I find some developer documentation ? Unfortunately I haven't had time to write much yet. http://wiki.dovecot.org/Design has something. Can I build my plugin separately, or do I need to rebuild dovecot again ? You'll need to build plugins against the same Dovecot sources (or header files at least) as you're running to make sure all the APIs are correct. PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] Time moved backwards
On May 15, 2008, at 5:12 PM, Neal Becker wrote: Problem I see is that an external script that *unconditionally* relaunches dovecot could be a terribly problem. It's better for dovecot to do it itself in this particular failure, because it's the only one who knows that it was just a date issue, and relaunching is safe. If someone wants to code this relaunching, feel free to do it and if the code looks good I'll include it. I'll maybe try fixing this some other way for v1.2 (verify all timestamp comparison code, make timeout handling work if clock moves, log only a warning. I'm not sure if I'm going to use a monotonic clock, since I'd like to know when time moves backwards or too much forwards and add some hooks there to do things like update dotlock file mtimes). PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] Time moved backwards
Here's another thought: >From man ntpd: If the -x option is included on the command line, the clock will never be stepped and only slew corrections will be used. The issues should be carefully explored before deciding to use the -x option. The maximum slew rate possible is limited to 500 parts-per-million (PPM) as a consequence of the correct- ness principles on which the NTP protocol and algorithm design are based. As a result, the local clock can take a long time to converge to an acceptable offset, about 2,000 s for each second the clock is outside the acceptable range. During this interval the local clock will not be consistent with any other network clock and the system cannot be used for distributed applications that require correctly synchronized network time.
Re: [Dovecot] Time moved backwards
> Problem I see is that an external script that *unconditionally* relaunches > dovecot could be a terribly problem. It's better for dovecot to do it > itself in this particular failure, because it's the only one who knows that > it was just a date issue, and relaunching is safe. But as Timo has explained, simply relaunching might *not* be safe. johannes signature.asc Description: This is a digitally signed message part
Re: [Dovecot] mysql index control allow nets
On May 15, 2008, at 5:07 PM, Evaggelos Balaskas wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Timo thanks again,
allow_nets worked perfectly
INDEX and CONTROL are now with delimiter :
here is my log :
dovecot: May 15 17:01:44 Info: auth(default): master out: USER 3
[EMAIL PROTECTED] home=/var/mail/ uid=1108gid=8
mail=maildir:/var/mail/ebalaskas.gr/ebal:INDEX=/var/mail/.index/
ebalaskas.gr/ebal:CONTROL=/var/mail/.control/ebalaskas.gr/ebal
but there is not index nor control folder created under /var/mail
What do the logs show with mail_debug=yes?
Or one guess: did you explicitly specify a location inside namespace
{ .. }? "mail" and mail_location is used only if namespace location
isn't set.
PGP.sig
Description: This is a digitally signed message part
Re: [Dovecot] Time moved backwards
Bill Cole wrote: > At 10:20 PM +0400 5/14/08, Eugene wrote: >>Hi people, >> >>>From: Adam McDougall <[EMAIL PROTECTED]> >>>I would just like to mention a circumstance that happened to me this >>>Sunday. We had a total power outage in our building, longer than our >>>UPS's could last and we don't have a generator for servers (nor is it >>>economical or needed). When the power came back on, my local NTP server >>>came on at the same time as my mail servers, as well a majority of my >>>other servers. My servers tried to step their time to be in sync with >>>my local NTP server, which was still busy trying to sync itself with >>>outside sources, which takes a while, so my mail servers did not get an >>>answer. Later, dovecot died because the time finally synced, and I >>>found out why pretty quick (have seen this before) but this was an >>>unusual situation. >>> >>>My point is, we had an unusual circumstance, and even though I've taken >>>steps to have my mail servers sync their time at boot and run ntpd >>>afterwards, there are some circumstances in which this is not enough, >>>and dovecot still died. Its not always because someone was lazy about >>>their time setup. >> >>My point exactly. It's amazing how some people are quick to ramble >>about someone else's administrative incompetence without taking time >>to read the situation. > > I most certainly did read your description of the situation, and my > use of the phrase "administrative incompetence" should not be taken > personally. I did not say (or mean) "administrator incompetence" and > would not try to make that sort of judgment at a distance. > >> (One person even suggested hacking the dovecot startup script to >>run ntpdate -- useless as ntpd already occupies the ports). > > That's one of the things that "ntpdate -u" is good for. > > >>Fact is, ntpd can take unpredictable delay before the initial >>time-step. Delay that can't be controlled, and it would be >>unreasonable to delay starting mail services until it is guaranteed >>to complete. Then, dovecot dies, and admin (who is not always >>immediately available) has to start it manually anyway (especially >>as it is not clear what to do with possibly unsynced timestamps) -- >>only after the unnecessary downtime. > > Or you can have an external watchdog that re-launches Dovecot if it > dies. This approach handles a broader set of failure modes and on > some OS's is a built-in feature of the startup subsystem. > > Because of the fact that Dovecot may be running in an environment > with an external watchdog, perhaps one like launchd or classical > SysV/Solaris init that can catch the exit of the process it spawned > and use it to trigger an immediate respawn. This means that adding an > internal respawn inside Dovecot that will not cause breakage on any > system is not as simple as it may seem. > >>So, the question is: why on earth can't we add a single line of code >>to dovecot to restart itself after terminating? > > You can do just that yourself if you believe that it is the best > option for your circumstances and adequate to handle the problem you > are having. One line of code might well do the trick you want on your > system. If Timo puts the functionality in the code he distributes, it > will need to be a great deal more than one line of code. > Problem I see is that an external script that *unconditionally* relaunches dovecot could be a terribly problem. It's better for dovecot to do it itself in this particular failure, because it's the only one who knows that it was just a date issue, and relaunching is safe.
Re: [Dovecot] mysql index control allow nets
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Timo thanks again, allow_nets worked perfectly INDEX and CONTROL are now with delimiter : here is my log : dovecot: May 15 17:01:44 Info: auth(default): master out: USER 3 [EMAIL PROTECTED] home=/var/mail/ uid=1108gid=8 mail=maildir:/var/mail/ebalaskas.gr/ebal:INDEX=/var/mail/.index/ebalaskas.gr/ebal:CONTROL=/var/mail/.control/ebalaskas.gr/ebal but there is not index nor control folder created under /var/mail Any ideas ? Timo Sirainen wrote: > On Wed, 2008-05-14 at 21:01 +0300, Evaggelos Balaskas wrote: > >> I am trying to have the same configuration with dovecot 1.1 and MySQL. >> According to log files when a virtual user is connecting to dovecot, >> the dovecot reads from MySQL the correct values but dovecot doesnt >> create the dirs for INDEX, CONTROL and the allow_nets is bypasses. >> >> - From my logs : >> dovecot: May 14 20:56:23 Info: auth(default): master out: USER 12 >> [EMAIL PROTECTED]uid=1002 gid=8 >> mail=maildir:/var/mail/ebalaskas.gr/ebalaskas >> INDEX=/var/mail/.index/ebalaskas.gr/ebalaskas >> CONTROL=/var/mail/.control/ebalaskas.gr/ebalaskas allow_nets=10.10.10.192 > > 1) There seem to be spaces between mail/INDEX/CONTROL? They're supposed > to be separated by ':', not spaces. > > 2) allow_nets is supposed to be in password_query, not in user_query. > - -- Evaggelos Balaskas - http://ebalaskas.gr Unix System Engineer Informatics Engineer Technological Education -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFILEO8WIK+Pe9twhoRAmw1AJ4sRNJaHmfw+F2iBbBYFr7WbPFTvgCeNPko aRZMkLjT/WNofn7PZdMoS4s= =A+GC -END PGP SIGNATURE-
Re: [Dovecot] Mixed maildir and mbox folder
Hi Timo,
> On Wed, 2008-05-07 at 22:13 +0200, Stefan Klatt wrote:
>> namespace:
>> type: private
>> separator: /
>> location: mbox:/srv/imapd/user/%u/Spam
>
> I guess the Spam is a mbox file? You can't create a location to point
> only to a single mailbox. Rather you might want to use something like:
under ../Spam i want to have the mbox files for spam and spam backscatters.
> namespace private {
> prefix = mbox/
> location = mbox:/srv/imapd/user/%u
> }
>
> Then you'll have mbox/Spam, and whatever other mbox files exist in that
> directory.
I tried all, but nothing worked.
Stefan
[Dovecot] Searching the Archives (was: Re: dovecot developer documentation)
On Thu, 2008-05-15 at 09:25 +0200, Piotr Wadas wrote:
> [...] AFAIK there's no search for mailing list archives
> available, to let me search for some older guidance in
> this case :(
You can use google, by adding site:dovecot.org to the search.
The dovecot list is one of the last fine mailing lists, that offer
archives in monthly (and a full) mbox format archives, suited for
importing into your mail client and searching *really* conveniently
offline and locally.
Also, dovecot.org offers list access by IMAP. :)
See http://dovecot.org/mailinglists.html
guenther
Caveat: I know I should not post before I got a sane dose of
caffeine. ;)
--
char *t="[EMAIL PROTECTED]";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
Re: [Dovecot] homedir override problem, MS AD + WINBIND + PAM + SIEVE
It's 1.0.13.
Ok, i maybe it isn't goog idead to have same directory for maildir and
home directory. But I used it only for sieve (and crashes :-)). Because
I don't know how to change path of home. I periodically create symlinks
from /var/spool/mail/ to /home/MALL/.
So now it's working, but it's incorrect solution :-)
Milan Koudelka
Linux & Network Administrator
Internet Mall, a.s.
Internet Mall - obchody, které si oblíbíte.
http://www.MALL.cz
Timo Sirainen napsal(a):
On Wed, 2008-05-14 at 13:06 +0200, Milan Koudelka - Internet Mall wrote:
I tried to override home directory by set this:
userdb passwd {
args = home=/var/spool/mail/%n
}
What Dovecot version? This works only with v1.1. Also it'd be better if
home directory wasn't the same as mail directory
(http://wiki.dovecot.org/VirtualUsers#homedirs).
--
Pocasi venku laka ke sportovani. Co takhle zkusit koleckove brusle? Ty
nejzadanejsi modely mame skladem s 20% slevou:
http://www.bartsport.cz/koleckove-brusle/
--
[Dovecot] dovecot developer documentation
Hello, I want to create some specific plugin for dovecot v1.1 (rc5). Where can I find some developer documentation ? Can I build my plugin separately, or do I need to rebuild dovecot again ? I'm looking into code, and analyzing some simple plugins, but hooks documentation or any hints you could give would be very helpful.. AFAIK there's no search for mailing list archives available, to let me search for some older guidance in this case :( Regards, Piotr
Re: [Dovecot] Dovecot dying when deliver is called
Oh, yes, thank you. It think the issue comes because in a previous version, the info_log_path for the lda was copied from its log_path and not from the master info_log_path. It is working now. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Timo Sirainen Envoyé : jeudi 15 mai 2008 08:56 À : Dovecot Mailing List Objet : Re: [Dovecot] Dovecot dying when deliver is called On Thu, 2008-05-15 at 08:52 +0200, MyGoddess wrote: > Thank you. > > The logfiles are created with permissions to root:root and 600 by dovecot. > As deliver can't acces them, do I have to change the permissions ? And > to what ? http://wiki.dovecot.org/LDA#logging gives some suggestions.
