search for: maib

...number(10000). I made the script which is called when quota_warning condition is met. Then i made a rule to exclude that folder from quota, quota_rule3:folder:ignore The problem is that this folder is still counted in quota. I don't know if this is a bug or this is how ignore is suposed to work(maibe ignore works only for storage). -- View this message in context: http://www.nabble.com/dovecot-quota-messages-problem-tp19738722p19738722.html Sent from the Dovecot mailing list archive at Nabble.com.

hi all, Im trying to configure a * server with FXO and FXS cards. Basically what i want to do is be able to recieve calls from PSTN and dailout as well...but im really very confused with how to handle the 30 channels coming in on the PRI....what would be the best hardware to use n stuff.. if someone can give me some hints or config examples that would be just great.... Thank's in

...idmap the same user could be assigned two different Unix UID's on each server which is what we want to avoid. I've read what I could find about LDAP idmap and unfortunately that was not very much (if somebody know a good how-to or docs to that topic, please point me there) So I have one maib question: - - Do you have to specify the idmap on the ldap server or is it generated on the fly like with the file based map? Regards - -- Beno?t Panizzon, <bp@imp.ch> - ------------------------------------------------------------------------ ImproWare AG, UNIXSP & ISP...

Hello again, folks! I''m getting one strange problem with FC5 running on XEN 3.0.3 x64... The MRTG point to my machine with XEN running one absurd volume of output data sent (normal is around 6 MB/s) and when XEN is working we get 80 MB/s until my DRAC is alive... after this, the machine crash, DRAC stop do reply, swith stop do work together... Anyone knows whats happening now? ;)

...did not work. I've also search (quickly) >the mailing list archive but did not find anything relevant... Okay, I've found the problem; a misconfiguration in the firewall caused it to block ports 137-139 on both sides of the firewall; it should block them only on the Internet side. doh! Maibe you should add this in DIAGNOSIS.txt: if everything fails, try to think of the most stupid thing that could prevent samba to work; chances are this is the problem... 8) Thanks to Alain Toussaint who sent me a couple of tips on how to discover the source of the problem, GFK's -- Guillaume Fili...