search for: iwfm

Hi, In Qualcomm's qpopper, you can specify a list of users to reject at authentication, even if they are otherwise valid, by putting them in a file (/etc/pop.nonauth). I use this to occasionally ban users who bang on the system needlessly until they Get a Clue. I looked thru the wiki.dovecot.org/Authentication pages and didn't see anything like this feature. Does it exist in 1.0?

I am currently using dovecot 0.99.14p1 on OpenBSD 3.8, mbox format, procmail+sendmail MTA. I subscribe to quite a few mailing lists and currently have procmail sorting mail into the proper mboxes. I was hoping there would be some sort of retention policy feature built in to dovecot. I want to delete mail more than X days old from X folders. I have combed the documentation, list archives, and

...ent was dismissed; garbage added at the end); > * %...%'s in a command name were not substituted, whereas they were in > the command's arguments. > > The patch solved things for me, but it's not perfect yet. Damn. And I was testing my version of the same patch... So for, IWFM with one small problem: with the gcc 4.0 frontend, "-emit-llvm" needs to be added to all of the translator.command lines. Not entirely sure how to conditionalize that in the configuration files. -scooter

Hey guys, I have a little problem. i'm running a CentOS 4.4 (Final) (Linux 2.6.9-42.0.10.EL) box. So, i installed SASacct (http://rousse.pm.org/sasacct/) for accouting the traffic of my hosts. But it dont make the graphics/images of utilization. The libs, rrdtool, perl are all installed. I just tested with rpm based rrdtool and Tarball, but no success. The firewall is ok: Counters reset

Once again I have updated Timo's auth patch for Postfix 2.2.1 to work with a 2.3 snapshot. It applied cleanly and compiled and is running for me, but is not really tested. This is Timo's code, not mine. All I did was manually edit in the rejects from the old patch. Find it here if you're interested: http://www.nodns4.us/postfix-2.3-20051121-dovecot-auth.patch.gz md5sum:

Hi, Op 14-aug-06, om 09:29 heeft Reid Spencer het volgende geschreven: > >> Apparently, %llvmgccdir% and %llvmcc1% are not recognized as a useful >> variable by the llvmc configuration parser. > > Actually, they are. See tools/llvmc/ConfigurationDriver.cpp around > line > 304. Also, they are recognized by the lexer. Its more likely that when > you configured LLVM

I have successfully set up a system with Ices0.4 and IceCast2.20 (and Tunez). It plays well using mpg123 or WinAmp. But I would like to use also my KiSS DVD player for the stream, and I have not been able to do so - It appearently needs 110% SHOUTcast compatibility. So I tried the IceCast2.3.1 - but it still didn't like the KiSS (or the other way around). In stead, I have added a SHOUTcast

If I use "system-config-display" or "system-config-display --reconfig" although I get a message that I need to log out of GNOME, to have the new file written, for new Display Resolution, logging out or restarting the box does not result in the new settings for the Display taking hold. Sometimes, the number of colors is updated, but *never* the Resolution. Below is my xorg.conf