Its All monkey.

[swestrup]

Well, for tonight tomorning I give up. Something is the fishy inside the courier stuff. Courier-Imap knows how to read a userdb, and is happy with it. Courier-maildrop is supposed to know how to read one as well, but there is gathering evidence that it, in fact, cannot. At least, not as currently compiled.

So now I have to decide if I want to try and figure out how to compile it with the necessary options, or whether I should just declare that using userdb as a stop-gap has failed, and go and re-implement everything in mysql...

I'm thinking that maybe I should sleep on it.

And since I have an international audience, and I don't know what time zone I'm in anyway:

Good Morning, Good Day, Good Afternoon, Good Evening, and Good Night!

Comments

[sps.livejournal.com]

Take a look at the source and see if it's a simple option. This isn't Windows; recompiling an application is no big deal at all.

[swestrup]

Actually, I've now seen a dozen faq's talking about how courier products are a bitch to compile because they have 7 dozen options and do strange automagic things based on environment probes when they compile. Makes me nervous. On the other hand, I *do* think I know what option needs to be turned on.

I'm also not entirely sure that what I need to do is recompile. maildrop will blurt out a bunch of config lines when you type 'maildrop -v', but what those lines MEAN is documented nowhere. Looking at them, its easy to convince myself they are saying that the option is turned on, but I can't really be sure without reading the source.

So, maybe I wanna bite the bullet and figure out how to set up a compilation environment on linux. (Its not that I don't know how to compile, its that I don't know how source rpm's interact with normal rpm's and how this all fits into the automagic upgrade thingy I've been using to maintain the site...)