Hello,
Attached is a patch to handle md5 passwords in a nice fashion. It
supports md5 hashes and digests for mysql and postgres, including
dbmail-adduser support for them, and even updates the man page. :)
A couple other fixes are in there, but not the patch from yesterday
for big endian
Magnus has an important point: don't check for an OS, check for what its
behavior is. I believe that in this case, we're talking about activating
parts of a system-dependent header with this flag. That the flag is system
dependent is not at issue; it's how we test that.
If the approach is like
Hi Bobby,
Could you sent me the e-mail message (full source, you can do that with
the postcat queufile command) that resulted in the sigsegv?
Best regards,
Eelco
On vrijdag, feb 21, 2003, at 22:14 Europe/Amsterdam, Boyan Alexiev
wrote:
Hello again guys!
It seems I am having some
Hello,
Yes, I agree that's a better thing to do, and I completely missed
that point in Magnus's email (my apologies). And defining __LINUX__
seems like the wrong thing to do if what you want to test is if you
need to #include endian.h, that's just how md5.c handles it now.
That can be changed
This sounds really great, but I'd like to pick a bone with the
arguments... I think we're now way past due on adding a distinct
crypt-type argument to complement the password argument.
In particular, the current syntax doesn't make it totally obvious
that one cannot do this:
dbmail-adduser -5
hi
i'm currently working on a webmail interface in jawmail style for dbmail
(without imap). i know that there still exists one - i write the second.
i figured out that every message has 2 record sets in messages. one is
for the header, the other one is the message itself. but how can i teach
Hi All,
I've seen a lot of patches lately, thanks a lot for this. Please keep
in mind though that we can only submit patches that are for both the
postgresql and mysql drivers. Since these are the most used we want
them to keep in sync. So if you change stuff in dbmysql.c, you should
also
