RE: [Dbmail] APOP vs. PBSP

2003-02-26 Thread Jesse Norell
Hello, Got this patch tested and it works. Not on Sparc platform still, but on Intel it does. Also, the first one I sent was messed up from a copy/paste (tabs->spaces) - the attached file will apply clean. Jesse Original Message From: Jesse Norell To: dbmail@dbmail.org Subject: RE

[Dbmail] sparc libcrypt(o) problems?

2003-02-26 Thread Dave Logan
Hi gang. A hundred years ago, quite possibly slightly more recently than that, I announced that the encryption stuff didn't seem to work on the sparc platform. Let me give a rundown of the problem again: Compiles fine, performs all functions (pop/smtp/adduser/maintenance) flawlessly. If I set a u

Re[2]: [Dbmail] [Dbmail 1.0] MD5 salted hashes patch

2003-02-26 Thread Boyan Alexiev
Hi Jesse, and anyone else who is interested... JN> So - by linking libcrypto instead of libcrypt, that function reverse - lcrypt instead of lcrypto Only lcrypt supports automatic salt recognition so to say and can handle md5 hashes. This way you can always mix different types of passwords, becaus

Re: [Dbmail] sparc libcrypt(o) problems?

2003-02-26 Thread Boyan Alexiev
Hi Dave, I think the difference between lcrypt and lcrypto applies only to the password field when you want to use md5 hashes. Not sure if it has anything to do with md5 digests, which are used for the APOP. Best regards, Bobby [EMAIL PROTECTED] on Wednesday, February 26, 2003, 2:42:25 AM, Dave

Re: Re: [Dbmail] dbmail setup

2003-02-26 Thread Markus Welsch
Hi, > You might add > deb http://debian.nfgd.net/debian/ woody/ > to your sources.list and install dbmail-mysql. You'll find a late cvs > pre 1.1 version > there for now. 1.1 will follow rsn. > But then, why are you installing mysql-max instead of simply doing > apt-get install mysql-server ? T

[Dbmail] Dbmail with Exim?

2003-02-26 Thread Wolf N. Paul
Hello, does anyone have a concise guide to setting up DBmail with Exim? I would like Exim to be the SMTP daemon receiving and distributing all mail, and DBmail to handle the local mailboxes, virtual domains, etc. All of this on Red Hat 8.0, with MySQL. Thanks, Wolf Paul

Re[3]: [Dbmail] dbmail setup

2003-02-26 Thread Boyan Alexiev
Hi Markus, The mysql-server package in Debian in fact supports InnoDB :) You just need to enter the neccessary lines in the my.cnf file. With dbmail it is best to use InnoDB i think. Best regards, Bobby [EMAIL PROTECTED] on Wednesday, February 26, 2003, 12:20:44 PM, Markus Welsch wrote: MW> Hi,

RE: [Dbmail] dbmail setup

2003-02-26 Thread Curtis Maurand
I've never been able to get it to compile using configure. I might be because I'm using RedHat. I also tried to get it to configure against MySQL 4.0.10 and it complained about compress. It didn't until I had upgraded from 3.23.49. I was trying to see if I could get it to work. Curtis On T

Re: Re: [Dbmail] dbmail setup

2003-02-26 Thread Curtis Maurand
I know that dbmail recommends innodb tables. they are not trivial to set up and they are not enabled in mysql-max by default. Has anyone done this using the BDB transaction tables which are enabled by default? Curtis On Wed, 26 Feb 2003, Markus Welsch wrote: > Hi, > > > You might add > >

[Dbmail] sparc endian-ness problems?

2003-02-26 Thread Dave Logan
OK, I formerly was fingerpointing at libcrypt(o) as the culprit for the APOP not working. Now I see that it's actually the fault of just the makemd5(), who calls the md5.h files, who includes the . Quick overview again, the hash isn't generated properly, so the login is not authenticated: Feb 26 0

RE: [Dbmail] sparc endian-ness problems?

2003-02-26 Thread Jesse Norell
Hello, Looking a little further, the "problem" is that endian.h is not included, because _LINUX_ is not defined. So, does anyone know the right way to handle this? Simply compiling with -D_LINUX_ fixes it; should all the build scripts automatically determine if you're on a linux system and def

[Dbmail] Urgent - Relay e Unknow User

2003-02-26 Thread Nataniel Klug
Guys, I am with a big problem. I created a linux box with DBMail and RedHat Linux then I put just 1 domain in transport table (clickdanoite.com.br and .clickdanoite.com.br). This works fine with three created accounts ([EMAIL PROTECTED], [EMAIL PROTECTED] and [EMAIL PROTECTED]). Its workin

RE: [Dbmail] Urgent - Relay e Unknow User

2003-02-26 Thread Jesse Norell
Hello, What are the pertinent lines from main.cf? The "User unknown in local recipient table" message doesn't sound familiar to me offhand; are you using a local_recipient_maps entry? If so, I assume it's set to a file with database parameters for dbmail's aliases table? (Forward that file con

Re: [Dbmail] Urgent - Relay e Unknow User

2003-02-26 Thread Nataniel Klug
: What are the pertinent lines from main.cf? The "User unknown in : local recipient table" message doesn't sound familiar to me offhand; : are you using a local_recipient_maps entry? If so, I assume it's set : to a file with database parameters for dbmail's aliases table? : (Forward that file c

Re: [Dbmail] Urgent - Relay e Unknow User

2003-02-26 Thread Jeff Brenton
Hello Nataniel, NK> Then I put another domain in transport (marilon.com.br and NK> .marilon.com.br) table... Done postmap and configured accounts in NK> DBMail. Result: the only account that receive email is NK> [EMAIL PROTECTED] the others that I created just return a NK> message like this: The

Re: [Dbmail] Urgent - Relay e Unknow User

2003-02-26 Thread Nataniel Klug
Hello Jeff, : The problem is that Postfix doesn't know it is the final destination : for the new domain. Just having a transport for it doesn't do it. And, : to be honest, I didn't have any luck with the officially-sanctioned : (by postfix.org) way of doing it... So, I modified what Eelco directed

Re: [Dbmail] Urgent - Relay e Unknow User

2003-02-26 Thread Jeff Brenton
Hello Nataniel, Oh, I forgot... To make postfix use dbmail's aliases table for local addresses, add to main.cf: local_recipient_maps = mysql:/etc/postfix/mailbox.cf where mailbox.cf contains the parameters for checking an address against the dbmail aliases table, such as: user = postfix passwor

Re: [Dbmail] Urgent - Relay e Unknow User

2003-02-26 Thread Nataniel Klug
Jeff, As I was afraid: Feb 26 16:44:39 ns2 postfix/pickup[16705]: fatal: unsupported dictionary type: mysql Feb 26 16:44:39 ns2 postfix/qmgr[16706]: fatal: unsupported dictionary type: mysql Nataniel Klug

Re[2]: [Dbmail] Urgent - Relay e Unknow User

2003-02-26 Thread Jeff Brenton
Hello Nataniel, NK> fatal: unsupported dictionary type: mysql Unfortunately, I have yet to see a distribution of postfix that has MySQL or Postgres support pre-built. You must compile from source. And that means making sure you have all the OTHER required development libraries installed, such as

[Dbmail] Exim transport?

2003-02-26 Thread Kris Pearson
Can someone post an example of a working exim transport? I can import mail using dbmail-smtp on the command line, but if I run it from exim, I get an error saying that dbmail-smtp returned 69. Thanks Kris Pearson

Re: Re[2]: [Dbmail] Urgent - Relay e Unknow User

2003-02-26 Thread Nataniel Klug
Jeff, : Unfortunately, I have yet to see a distribution of postfix that has : MySQL or Postgres support pre-built. You must compile from source. And : that means making sure you have all the OTHER required development : libraries installed, such as Berkley DBM. : : In the mean time, you CAN use th

Re: [Dbmail] Urgent - Relay e Unknow User

2003-02-26 Thread Jesse Norell
Hello Nataniel, Probably keep following Jeff's instructions on getting postfix to talk directly to your database, as you end up with a much more flexible/powerful setup, but you can use postfix+dbmail without any database support in postfix, which you may want/need to do to get this resolved qui

Re: [Dbmail] Urgent - Relay e Unknow User

2003-02-26 Thread Nataniel Klug
Jesse, That was what I done. Its now working ok. Now I am trying to put pop-before-smtp to work so I will not let it as an Open Relay... Thanks a lot. Nataniel Klug - Original Message - From: "Jesse Norell" <[EMAIL PROTECTED]> To: Sent: Wednesday, February 26, 2003 5:50 PM Subject: Re: