[Dbmail] dbmail 1.1
is this still scheduled for release tomorrow? -- "power off einstein" - moe syzlak
[Dbmail] dbmail 1.1
i am assuming that the current cvs is 1.1? if not, where can i get it? and is the autoconf "configure" script working on rh7x? thanks, shon -- "power off einstein" - moe syzlak
[Dbmail] DBmail 1.1 release
Hi all, from our point of view, dbmail 1.1 is needed as soon as possible since the 1.0 release does not compile straight away and suffers from severe pop-bugs. These problems seem to be solved now; we are planning to release the current CVS as dbmail 1.1 next thursday. I would ask you all for patches are available but have not yet been included in cvs. Some key points from the top of my head: * automake anyone has some working automake/autoconf patches for current CVS? * separate authentication (LDAP) has this been tested? is it ready for release? are patches available to include auth_connect() calls? is it possible to disable the separte authentication (such a waste to connect twice to the same database)? * QUOTA imap extension has testing been performed? does it work correcly with the internal dbmail quotum system? does it consider removed-but-not-yet-purged-in-maintenance messages (i.e. messages with status < 2 should not count for the mailboxsize)? i will remove the QUOTA keyword from the CAPABILITY string in case of any doubt.. i know, these are a lot of questions and probably i could find some answers myself but we are real busy now :-( (but then again, life can't always be as fun as dbmail coding - sometimes you just have to make money :p) Met vriendelijke groet, Roel Rozendaal _ R.A. Rozendaal ICT Manager IC&S T: +31 30 2322878 F: +31 30 2322305 www.ic-s.nl
Re: [Dbmail] dbmail 1.1
well it was scheduled for last thursday :-) after checking all updates on the mailing list i think it is safe to release 1.1 tomorrow; the 1.1 release will be the current CVS then. regards roel shon heeft op woensdag, 12 feb 2003 om 18:11 (Europe/Amsterdam) het volgende geschreven: is this still scheduled for release tomorrow? -- "power off einstein" - moe syzlak ___ Dbmail mailing list Dbmail@dbmail.org https://mailman.fastxs.nl/mailman/listinfo/dbmail Met vriendelijke groet, Roel Rozendaal _ R.A. Rozendaal ICT Manager IC&S T: +31 30 2322878 F: +31 30 2322305 www.ic-s.nl
Re: [Dbmail] dbmail 1.1
dbmail.org has the CVS instructions on it. I just installed the latest CVS on redhat 7.2, using the build.sh script and it ran fine, except it barfed on the final handoff to dbmail-install.sh. This I had to just run by hand. -Micah At 04:20 PM 2/19/2003 -0600, you wrote: i am assuming that the current cvs is 1.1? if not, where can i get it? and is the autoconf "configure" script working on rh7x? thanks, shon -- "power off einstein" - moe syzlak ___ Dbmail mailing list Dbmail@dbmail.org https://mailman.fastxs.nl/mailman/listinfo/dbmail
Re: [Dbmail] dbmail 1.1
On Wed, 2003-02-19 at 16:20, shon wrote: > i am assuming that the current cvs is 1.1? if not, where can i get it? and > is the autoconf "configure" script working on rh7x? > > thanks, > shon If it isn't, I'd like to hear about it. -- Ryan Butler <[EMAIL PROTECTED]> ADI Internet Solutions
[Dbmail] DBMail 1.1 fixes.
Does anyone know if 1.1 fixes the pop3d delivery to incorrect users problem. The issue was that someone would get disconnected during a pop3 download, then someone else would get that some pop3d process and recieve the previous persons email. The fix was to have each pop3d die after 1 connection. Thank you very much. Other than that is there a changelog anywhere? -- Bret Baptist Systems and Technical Support Specialist [EMAIL PROTECTED] Internet Exposure, Inc. http://www.iexposure.com (612)676-1946 x17 Web Development-Web Marketing-ISP Services -- Today is the tomorrow you worried about yesterday.
Re: [Dbmail] DBmail 1.1 release
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 wouldn't it be better to release CVS current as 1.1rc1, and let us test it. this way we don't run into the silly things that happened to 1.0 :) - -ben "Unix is user friendly, Its just picky about its friends." On Tue, 4 Feb 2003, Roel Rozendaal - IC&S wrote: > Hi all, > > from our point of view, dbmail 1.1 is needed as soon as possible since > the 1.0 release does not compile straight away and suffers from severe > pop-bugs. These problems seem to be solved now; we are planning to > release the current CVS as dbmail 1.1 next thursday. I would ask you > all for patches are available but have not yet been included in cvs. > Some key points from the top of my head: > > * automake > anyone has some working automake/autoconf patches for current CVS? > * separate authentication (LDAP) > has this been tested? is it ready for release? are patches available > to include auth_connect() calls? is it possible to disable the separte > authentication (such a waste to connect twice to the same database)? > * QUOTA imap extension > has testing been performed? does it work correcly with the internal > dbmail quotum system? does it consider > removed-but-not-yet-purged-in-maintenance messages (i.e. messages with > status < 2 should not count for the mailboxsize)? i will remove the > QUOTA keyword from the CAPABILITY string in case of any doubt.. > > i know, these are a lot of questions and probably i could find some > answers myself but we are real busy now :-( (but then again, life can't > always be as fun as dbmail coding - sometimes you just have to make > money :p) > > > > Met vriendelijke groet, > > > Roel Rozendaal > > > _ > R.A. Rozendaal > ICT Manager > IC&S > T: +31 30 2322878 > F: +31 30 2322305 > www.ic-s.nl > > ___ > Dbmail mailing list > Dbmail@dbmail.org > https://mailman.fastxs.nl/mailman/listinfo/dbmail > -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+P+xcflzKmtpiQEMRAg9DAJwIIj7C3+zArDfYGxeEnzLGTOAv2QCgiM0R Ggbujn4m5l6fV6hVLs+qJgg= =gv3o -END PGP SIGNATURE-
Re: [Dbmail] DBmail 1.1 release
well that would seem sensible from a pure version-number point of view but the current cvs has no real new developments other than separate authentication and QUOTA support. So this 1.1 release is more like a 1.0a bugfix release or however you would like to call it :-). Our goal for the moment is to release (on _real_ short notice) a dbmail version that is (1) compiles at once and (2) has working POP and IMAP daemons. I prefer (by far) not yet implementing LDAP-authentication and QUOTA for a stable release. As said before on this list, the segfaulting pop daemon and compile-time errors are show-stoppers and we really hate it that people get disappointed about dbmail because of this.. Ben Kochie heeft op dinsdag, 4 feb 2003 om 17:37 (Europe/Amsterdam) het volgende geschreven: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 wouldn't it be better to release CVS current as 1.1rc1, and let us test it. this way we don't run into the silly things that happened to 1.0 :) - -ben "Unix is user friendly, Its just picky about its friends." On Tue, 4 Feb 2003, Roel Rozendaal - IC&S wrote: Hi all, from our point of view, dbmail 1.1 is needed as soon as possible since the 1.0 release does not compile straight away and suffers from severe pop-bugs. These problems seem to be solved now; we are planning to release the current CVS as dbmail 1.1 next thursday. I would ask you all for patches are available but have not yet been included in cvs. Some key points from the top of my head: * automake anyone has some working automake/autoconf patches for current CVS? * separate authentication (LDAP) has this been tested? is it ready for release? are patches available to include auth_connect() calls? is it possible to disable the separte authentication (such a waste to connect twice to the same database)? * QUOTA imap extension has testing been performed? does it work correcly with the internal dbmail quotum system? does it consider removed-but-not-yet-purged-in-maintenance messages (i.e. messages with status < 2 should not count for the mailboxsize)? i will remove the QUOTA keyword from the CAPABILITY string in case of any doubt.. i know, these are a lot of questions and probably i could find some answers myself but we are real busy now :-( (but then again, life can't always be as fun as dbmail coding - sometimes you just have to make money :p) Met vriendelijke groet, Roel Rozendaal _ R.A. Rozendaal ICT Manager IC&S T: +31 30 2322878 F: +31 30 2322305 www.ic-s.nl ___ Dbmail mailing list Dbmail@dbmail.org https://mailman.fastxs.nl/mailman/listinfo/dbmail -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+P+xcflzKmtpiQEMRAg9DAJwIIj7C3+zArDfYGxeEnzLGTOAv2QCgiM0R Ggbujn4m5l6fV6hVLs+qJgg= =gv3o -END PGP SIGNATURE- ___ Dbmail mailing list Dbmail@dbmail.org https://mailman.fastxs.nl/mailman/listinfo/dbmail Met vriendelijke groet, Roel Rozendaal _ R.A. Rozendaal ICT Manager IC&S T: +31 30 2322878 F: +31 30 2322305 www.ic-s.nl
Re: [Dbmail] DBmail 1.1 release
I absolutely agree that the LDAP authentication should not be included for 1.1, however if you can include the infrastructure changes that will make it easier to patch in, I'd much appreciate it :-) I've posted the changes again this week, but mostly as descriptions and code, not specifically patches. If you're too time-crunched for my ramblings, I'll get you a diff -c, it's no trouble! Aaron On Tue, 4 Feb 2003, Roel Rozendaal - IC&S wrote: > well that would seem sensible from a pure version-number point of view > but the current cvs has no real new developments other than separate > authentication and QUOTA support. So this 1.1 release is more like a > 1.0a bugfix release or however you would like to call it :-). > > Our goal for the moment is to release (on _real_ short notice) a dbmail > version that is (1) compiles at once and (2) has working POP and IMAP > daemons. I prefer (by far) not yet implementing LDAP-authentication and > QUOTA for a stable release. As said before on this list, the > segfaulting pop daemon and compile-time errors are show-stoppers and we > really hate it that people get disappointed about dbmail because of > this.. > > > Ben Kochie heeft op dinsdag, 4 feb 2003 om 17:37 (Europe/Amsterdam) het > volgende geschreven: > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > wouldn't it be better to release CVS current as 1.1rc1, and let us test > > it. this way we don't run into the silly things that happened to 1.0 > > :) > > > > - -ben > > > > "Unix is user friendly, Its just picky about its friends." > > > > On Tue, 4 Feb 2003, Roel Rozendaal - IC&S wrote: > > > >> Hi all, > >> > >> from our point of view, dbmail 1.1 is needed as soon as possible since > >> the 1.0 release does not compile straight away and suffers from severe > >> pop-bugs. These problems seem to be solved now; we are planning to > >> release the current CVS as dbmail 1.1 next thursday. I would ask you > >> all for patches are available but have not yet been included in cvs. > >> Some key points from the top of my head: > >> > >> * automake > >>anyone has some working automake/autoconf patches for current CVS? > >> * separate authentication (LDAP) > >>has this been tested? is it ready for release? are patches available > >> to include auth_connect() calls? is it possible to disable the separte > >> authentication (such a waste to connect twice to the same database)? > >> * QUOTA imap extension > >>has testing been performed? does it work correcly with the internal > >> dbmail quotum system? does it consider > >> removed-but-not-yet-purged-in-maintenance messages (i.e. messages with > >> status < 2 should not count for the mailboxsize)? i will remove the > >> QUOTA keyword from the CAPABILITY string in case of any doubt.. > >> > >> i know, these are a lot of questions and probably i could find some > >> answers myself but we are real busy now :-( (but then again, life > >> can't > >> always be as fun as dbmail coding - sometimes you just have to make > >> money :p) > >> > >> > >> > >> Met vriendelijke groet, > >> > >> > >> Roel Rozendaal > >> > >> > >> _ > >> R.A. Rozendaal > >> ICT Manager > >> IC&S > >> T: +31 30 2322878 > >> F: +31 30 2322305 > >> www.ic-s.nl > >> > >> ___ > >> Dbmail mailing list > >> Dbmail@dbmail.org > >> https://mailman.fastxs.nl/mailman/listinfo/dbmail > >> > > -BEGIN PGP SIGNATURE- > > Version: GnuPG v1.2.1 (GNU/Linux) > > > > iD8DBQE+P+xcflzKmtpiQEMRAg9DAJwIIj7C3+zArDfYGxeEnzLGTOAv2QCgiM0R > > Ggbujn4m5l6fV6hVLs+qJgg= > > =gv3o > > -END PGP SIGNATURE- > > ___ > > Dbmail mailing list > > Dbmail@dbmail.org > > https://mailman.fastxs.nl/mailman/listinfo/dbmail > > > Met vriendelijke groet, > > > Roel Rozendaal > > > _ > R.A. Rozendaal > ICT Manager > IC&S > T: +31 30 2322878 > F: +31 30 2322305 > www.ic-s.nl > > ___ > Dbmail mailing list > Dbmail@dbmail.org > https://mailman.fastxs.nl/mailman/listinfo/dbmail >
Re: [Dbmail] DBmail 1.1 release
On Tue, 2003-02-04 at 02:51, Roel Rozendaal - IC&S wrote: > Hi all, > > from our point of view, dbmail 1.1 is needed as soon as possible since > the 1.0 release does not compile straight away and suffers from severe > pop-bugs. These problems seem to be solved now; we are planning to > release the current CVS as dbmail 1.1 next thursday. I would ask you > all for patches are available but have not yet been included in cvs. > Some key points from the top of my head: > > * automake > anyone has some working automake/autoconf patches for current CVS? I made patches for 1.0 to bring it up to date, were those ever applied to the cvs? If not, you can find them on dbmail.adiis.net. If you're truly interested in having it work, I'll be more than happy to update them to the current cvs. The ones that were spun for 1.0 seem functional to me, I can specify either a mysql or postgres build and it will find the libraries and build it for me. But if it is not working for some people I do need bug reports so I can straighten it out. -- Ryan Butler <[EMAIL PROTECTED]> ADI Internet Solutions
Re: [Dbmail] DBmail 1.1 release
Hello, This seems like a sound gameplan; I think your original message in this thread soliciting additional patches to throw in prior to a 1.1 release could be asking for the same problems the 1.0 release had (ie. too many changes w/o enough time to work issues out). Just wrap up the minimal things (eg. autoconf, maybe the auth hooks Aaron's requesting), like you said here. Original Message From: Roel Rozendaal - IC&S To: dbmail@dbmail.org Subject: Re: [Dbmail] DBmail 1.1 release Sent: Tue, 4 Feb 2003 17:57:41 +0100 > well that would seem sensible from a pure version-number point of view > but the current cvs has no real new developments other than separate > authentication and QUOTA support. So this 1.1 release is more like a > 1.0a bugfix release or however you would like to call it :-). > > Our goal for the moment is to release (on _real_ short notice) a dbmail > version that is (1) compiles at once and (2) has working POP and IMAP > daemons. I prefer (by far) not yet implementing LDAP-authentication and > QUOTA for a stable release. As said before on this list, the > segfaulting pop daemon and compile-time errors are show-stoppers and we > really hate it that people get disappointed about dbmail because of > this.. > > > Ben Kochie heeft op dinsdag, 4 feb 2003 om 17:37 (Europe/Amsterdam) het > volgende geschreven: > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > wouldn't it be better to release CVS current as 1.1rc1, and let us test > > it. this way we don't run into the silly things that happened to 1.0 > > :) > > > > - -ben > > > > "Unix is user friendly, Its just picky about its friends." > > > > On Tue, 4 Feb 2003, Roel Rozendaal - IC&S wrote: > > > >> Hi all, > >> > >> from our point of view, dbmail 1.1 is needed as soon as possible since > >> the 1.0 release does not compile straight away and suffers from severe > >> pop-bugs. These problems seem to be solved now; we are planning to > >> release the current CVS as dbmail 1.1 next thursday. I would ask you > >> all for patches are available but have not yet been included in cvs. > >> Some key points from the top of my head: > >> > >> * automake > >>anyone has some working automake/autoconf patches for current CVS? > >> * separate authentication (LDAP) > >>has this been tested? is it ready for release? are patches available > >> to include auth_connect() calls? is it possible to disable the separte > >> authentication (such a waste to connect twice to the same database)? > >> * QUOTA imap extension > >>has testing been performed? does it work correcly with the internal > >> dbmail quotum system? does it consider > >> removed-but-not-yet-purged-in-maintenance messages (i.e. messages with > >> status < 2 should not count for the mailboxsize)? i will remove the > >> QUOTA keyword from the CAPABILITY string in case of any doubt.. > >> > >> i know, these are a lot of questions and probably i could find some > >> answers myself but we are real busy now :-( (but then again, life > >> can't > >> always be as fun as dbmail coding - sometimes you just have to make > >> money :p) > >> > >> > >> > >> Met vriendelijke groet, > >> > >> > >> Roel Rozendaal > >> > >> > >> _ > >> R.A. Rozendaal > >> ICT Manager > >> IC&S > >> T: +31 30 2322878 > >> F: +31 30 2322305 > >> www.ic-s.nl > >> > >> ___ > >> Dbmail mailing list > >> Dbmail@dbmail.org > >> https://mailman.fastxs.nl/mailman/listinfo/dbmail > >> > > -BEGIN PGP SIGNATURE- > > Version: GnuPG v1.2.1 (GNU/Linux) > > > > iD8DBQE+P+xcflzKmtpiQEMRAg9DAJwIIj7C3+zArDfYGxeEnzLGTOAv2QCgiM0R > > Ggbujn4m5l6fV6hVLs+qJgg= > > =gv3o > > -END PGP SIGNATURE- > > ___ > > Dbmail mailing list > > Dbmail@dbmail.org > > https://mailman.fastxs.nl/mailman/listinfo/dbmail > > > Met vriendelijke groet, > > > Roel Rozendaal > > > _ > R.A. Rozendaal > ICT Manager > IC&S > T: +31 30 2322878 > F: +31 30 2322305 > www.ic-s.nl > > ___ > Dbmail mailing list > Dbmail@dbmail.org > https://mailman.fastxs.nl/mailman/listinfo/dbmail > -- End Original Message -- -- Jesse Norell [EMAIL PROTECTED]
Re: [Dbmail] DBmail 1.1 release
I don't know if anybody has already done this or not but be sure to change the postgresql schema file. Currently you are specifying a DATETIME field when it should be TIMESTAMP. DATETIME is not a valid postgresql field type. :wq Tim Uckun US Investigations Services/Due Diligence http://www.diligence.com/
[Dbmail] dbmail 1.1 - autoconf issues
Hi, we've decided to release dbmail 1.1 as soon as the autoconf is working. I have applied some patches to cvs recently (last wednesday) but i can't seem to get it working on our systems; seems like some dependencies are failing (missing object files). Does anyone have a patch to make the current cvs work with autoconf? regards roel Met vriendelijke groet, Roel Rozendaal _ R.A. Rozendaal ICT Manager IC&S T: +31 30 2322878 F: +31 30 2322305 www.ic-s.nl
Re: [Dbmail] DBMail 1.1 fixes.
has been fixed :-) Bret Baptist heeft op vrijdag, 21 feb 2003 om 19:05 (Europe/Amsterdam) het volgende geschreven: Does anyone know if 1.1 fixes the pop3d delivery to incorrect users problem. The issue was that someone would get disconnected during a pop3 download, then someone else would get that some pop3d process and recieve the previous persons email. The fix was to have each pop3d die after 1 connection. Thank you very much. Other than that is there a changelog anywhere? -- Bret Baptist Systems and Technical Support Specialist [EMAIL PROTECTED] Internet Exposure, Inc. http://www.iexposure.com (612)676-1946 x17 Web Development-Web Marketing-ISP Services -- Today is the tomorrow you worried about yesterday. ___ Dbmail mailing list Dbmail@dbmail.org https://mailman.fastxs.nl/mailman/listinfo/dbmail _ R.A. Rozendaal ICT Manager IC&S T: +31 30 2322878 F: +31 30 2322305 www.ic-s.nl
Re: [Dbmail] dbmail 1.1 - autoconf issues
On Fri, 2003-02-07 at 12:59, Roel Rozendaal - IC&S wrote: > Hi, > > we've decided to release dbmail 1.1 as soon as the autoconf is working. > I have applied some patches to cvs recently (last wednesday) but i > can't seem to get it working on our systems; seems like some > dependencies are failing (missing object files). Does anyone have a > patch to make the current cvs work with autoconf? > > regards roel > > The patch was correct, but I didn't patch it after running automake to update Makefile.am. I made a new patch here that updates the autoconf version to 1.1, and has all the post automake changes, this patch, applied to the current CVS as I checked it out about 10 minutes ago compiles smoothly on mysql and pgsql builds. -- Ryan Butler <[EMAIL PROTECTED]> ADI Internet Solutions diff -ur dbmail/Makefile.am dbmail.working/Makefile.am --- dbmail/Makefile.am Wed Feb 5 04:25:29 2003 +++ dbmail.working/Makefile.am Fri Feb 7 13:10:54 2003 @@ -1,6 +1,6 @@ SUBDIRS = mysql pgsql . -bin_PROGRAMS = dbmail-smtp dbmail-pop3d dbmail-imapd dbmail-maintenance dbmail-adduser dbmail-readvut raw-convertor dbmail-mini-injector mb2db +bin_PROGRAMS = dbmail-smtp dbmail-pop3d dbmail-imapd dbmail-maintenance dbmail-adduser dbmail-readvut raw-convertor dbmail-mini-injector bin_SCRIPTS = install-dbmail.sh dbmail_smtp_SOURCES = config.c list.c debug.c dbmd5.c md5.c mime.c main.c pipe.c bounce.c forward.c memblock.c diff -ur dbmail/Makefile.in dbmail.working/Makefile.in --- dbmail/Makefile.in Fri Jul 26 16:34:15 2002 +++ dbmail.working/Makefile.in Fri Feb 7 13:15:48 2003 @@ -1,6 +1,6 @@ -# Makefile.in generated automatically by automake 1.4-p4 from Makefile.am +# Makefile.in generated automatically by automake 1.4-p5 from Makefile.am -# Copyright (C) 1994, 1995-8, 1999 Free Software Foundation, Inc. +# Copyright (C) 1994, 1995-8, 1999, 2001 Free Software Foundation, Inc. # This Makefile.in is free software; the Free Software Foundation # gives unlimited permission to copy and/or distribute it, # with or without modifications, as long as this notice is preserved. @@ -70,55 +70,51 @@ SUBDIRS = mysql pgsql . -bin_PROGRAMS = dbmail-smtp dbmail-pop3d dbmail-imapd dbmail-maintenance dbmail-config dbmail-adduser dbmail-readvut dbmail-smtp-injector uni-one-convertor raw-convertor dbmail-mini-injector +bin_PROGRAMS = dbmail-smtp dbmail-pop3d dbmail-imapd dbmail-maintenance dbmail-adduser dbmail-readvut raw-convertor dbmail-mini-injector bin_SCRIPTS = install-dbmail.sh -dbmail_smtp_SOURCES = list.c debug.c dbmd5.c md5.c mime.c main.c pipe.c bounce.c forward.c memblock.c +dbmail_smtp_SOURCES = config.c list.c debug.c dbmd5.c md5.c mime.c main.c pipe.c bounce.c forward.c memblock.c dbmail_smtp_LDADD = @SQLALIB@ dbmail_smtp_LDFLAGS = @SQLLIB@ -dbmail_pop3d_SOURCES = pop3.c list.c debug.c dbmd5.c md5.c mime.c misc.c memblock.c pop3d.c +dbmail_pop3d_SOURCES = config.c server.c serverchild.c pop3.c list.c debug.c dbmd5.c md5.c mime.c misc.c memblock.c pop3d.c dbmail_pop3d_LDADD = @SQLALIB@ dbmail_pop3d_LDFLAGS = @SQLLIB@ -dbmail_imapd_SOURCES = imap4.c debug.c serverservice.c list.c dbmd5.c md5.c imaputil.c imapcommands.c mime.c misc.c memblock.c rfcmsg.c imapd.c +dbmail_imapd_SOURCES = quota.c config.c server.c serverchild.c imap4.c debug.c list.c dbmd5.c md5.c imaputil.c imapcommands.c mime.c misc.c memblock.c rfcmsg.c imapd.c 1 dbmail_imapd_LDADD = @SQLALIB@ dbmail_imapd_LDFLAGS = @SQLLIB@ -dbmail_maintenance_SOURCES = debug.c list.c dbmd5.c md5.c mime.c memblock.c maintenance.c auth.h +dbmail_maintenance_SOURCES = config.c debug.c list.c dbmd5.c md5.c mime.c memblock.c maintenance.c auth.h dbmail_maintenance_LDADD = @SQLALIB@ dbmail_maintenance_LDFLAGS = @SQLLIB@ -dbmail_config_SOURCES = list.c md5.c debug.c dbmd5.c mime.c memblock.c settings.c -dbmail_config_LDADD = @SQLALIB@ -dbmail_config_LDFLAGS = @SQLLIB@ - -dbmail_adduser_SOURCES = debug.c list.c dbmd5.c md5.c mime.c memblock.c user.c +dbmail_adduser_SOURCES = config.c debug.c list.c dbmd5.c md5.c mime.c memblock.c user.c dbmail_adduser_LDADD = @SQLALIB@ dbmail_adduser_LDFLAGS = @SQLLIB@ -dbmail_readvut_SOURCES = debug.c list.c dbmd5.c md5.c mime.c vut2dbmail.c +dbmail_readvut_SOURCES = config.c debug.c list.c dbmd5.c md5.c mime.c vut2dbmail.c dbmail_readvut_LDADD = @SQLALIB@ dbmail_readvut_LDFLAGS = @SQLLIB@ -#dbmail_realsmtp_SOURCES = debug.c dbmd5.c md5.c list.c mime.c \ +#dbmail_realsmtp_SOURCES = config.c debug.c dbmd5.c md5.c list.c mime.c \ # serverservice.c misc.c memblock.c #dbmail_realsmtp_LDADD = @SQLALIB@ #dbmail_realsmtp_LDFLAGS = @SQLLIB@ -dbmail_smtp_injector_SOURCES = list.c debug.c dbmd5.c md5.c mime.c injector.c -dbmail_smtp_injector_LDADD = @SQLALIB@ -dbmail_smtp_injector_LDFLAGS = @SQLLIB@ - -uni_one_convertor_SOURCES = list.c debug.c dbmd5.c md5.c mime.c uni-one-convert.c -uni_one_convertor_LDADD = @SQLALIB@ -uni_one_convertor_LDFLAGS = @SQLLIB@ +#dbmail_smtp_injector_SOURCES
Re: [Dbmail] dbmail 1.1 - autoconf issues
Also caught that another patch was never applied, so I remade it for the current cvs as well, this can be applied after the patch I just sent, it makes it so you MUST specify either --with-mysql or --with-pgsql The current cvs will happily let you just ./configure and not setup either sql backend, which of course doesn't compile right Please apply the previous patch and this one. -- Ryan Butler <[EMAIL PROTECTED]> ADI Internet Solutions
Re: [Dbmail] dbmail 1.1 - autoconf issues
On Fri, 2003-02-07 at 13:41, Ryan Butler wrote:
> Also caught that another patch was never applied, so I remade it for the
> current cvs as well, this can be applied after the patch I just sent, it
> makes it so you MUST specify either --with-mysql or --with-pgsql
>
> The current cvs will happily let you just ./configure and not setup
> either sql backend, which of course doesn't compile right
>
> Please apply the previous patch and this one.
Would help if I sent the patch eh?
--
Ryan Butler <[EMAIL PROTECTED]>
ADI Internet Solutions
diff -ur dbmail/aclocal.m4 dbmail.working/aclocal.m4
--- dbmail/aclocal.m4 Fri Jul 26 16:17:05 2002
+++ dbmail.working/aclocal.m4 Thu Nov 21 09:44:39 2002
@@ -155,6 +155,26 @@
WARN=0
# Make sure we only select one, mysql or pgsql
+if test "${mysqlheadername-x}" = "x"
+then
+ if test "${pgsqlheadername-x}" = "x"
+ then
+NEITHER=1
+mysqlheadername=""
+MYSQLINC=""
+PGSQLINC=""
+ fi
+fi
+if test "$NEITHER" = 1
+ then
+ AC_MSG_ERROR([
+
+ You have to specify --with-mysql or --with-pgsql to build.
+])
+fi
+
+
+
if test ! "${mysqlheadername-x}" = "x"
then
if test ! "${pgsqlheadername-x}" = "x"
diff -ur dbmail/configure dbmail.working/configure
--- dbmail/configure Fri Sep 13 08:56:44 2002
+++ dbmail.working/configure Thu Nov 21 09:44:41 2002
@@ -871,6 +871,26 @@
WARN=0
# Make sure we only select one, mysql or pgsql
+if test "${mysqlheadername-x}" = "x"
+then
+ if test "${pgsqlheadername-x}" = "x"
+ then
+NEITHER=1
+mysqlheadername=""
+MYSQLINC=""
+PGSQLINC=""
+ fi
+fi
+if test "$NEITHER" = 1
+ then
+ { echo "configure: error:
+
+ You have to specify --with-mysql or --with-pgsql to build.
+" 1>&2; exit 1; }
+fi
+
+
+
if test ! "${mysqlheadername-x}" = "x"
then
if test ! "${pgsqlheadername-x}" = "x"
@@ -897,7 +917,7 @@
if test "$withval" != "yes"
then
echo $ac_n "checking for mysql.h (user supplied)""... $ac_c" 1>&6
-echo "configure:901: checking for mysql.h (user supplied)" >&5
+echo "configure:921: checking for mysql.h (user supplied)" >&5
if test -r "$mysqlheadername/mysql.h"
then
# found
@@ -915,7 +935,7 @@
else
# Lets look in our standard paths
echo $ac_n "checking for mysql.h""... $ac_c" 1>&6
-echo "configure:919: checking for mysql.h" >&5
+echo "configure:939: checking for mysql.h" >&5
for mysqlpaths in $mysqlheaderpaths
do
if test -r "$mysqlpaths/mysql.h"
@@ -942,7 +962,7 @@
if test "$withval" != "yes"
then
echo $ac_n "checking for libpq-fe.h (user supplied)""... $ac_c" 1>&6
-echo "configure:946: checking for libpq-fe.h (user supplied)" >&5
+echo "configure:966: checking for libpq-fe.h (user supplied)" >&5
if test -r "$pgsqlheadername/libpq-fe.h"
then
# found
@@ -960,7 +980,7 @@
else
# Lets look in our standard paths
echo $ac_n "checking for libpq-fe.h""... $ac_c" 1>&6
-echo "configure:964: checking for libpq-fe.h" >&5
+echo "configure:984: checking for libpq-fe.h" >&5
for pgsqlpaths in $pgsqlheaderpaths
do
if test -r "$pgsqlpaths/libpq-fe.h"
@@ -984,7 +1004,7 @@
if test ! "${mysqlheadername-x}" = "x"
then
echo $ac_n "checking for mysql_real_connect in -lmysqlclient""... $ac_c" 1>&6
-echo "configure:988: checking for mysql_real_connect in -lmysqlclient" >&5
+echo "configure:1008: checking for mysql_real_connect in -lmysqlclient" >&5
ac_lib_var=`echo mysqlclient'_'mysql_real_connect | sed 'y%./+-%__p_%'`
if eval "test \"`echo '$''{'ac_cv_lib_$ac_lib_var'+set}'`\" = set"; then
echo $ac_n "(cached) $ac_c" 1>&6
@@ -992,7 +1012,7 @@
ac_save_LIBS="$LIBS"
LIBS="-lmysqlclient $LIBS"
cat > conftest.$ac_ext <&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
+if { (eval echo configure:1027: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
rm -rf conftest*
eval "ac_cv_lib_$ac_lib_var=yes"
else
@@ -1035,7 +1055,7 @@
if test ! "${pgsqlheadername-x}" = "x"
then
echo $ac_n "checking for PQconnectdb in -lpq""... $ac_c" 1>&6
-echo "configure:1039: checking for PQconnectdb in -lpq" >&5
+echo "configure:1059: checking for PQconnectdb in -lpq" >&5
ac_lib_var=`echo pq'_'PQconnectdb | sed 'y%./+-%__p_%'`
if eval "test \"`echo '$''{'ac_cv_lib_$ac_lib_var'+set}'`\" = set"; then
echo $ac_n "(cached) $ac_c" 1>&6
@@ -1043,7 +1063,7 @@
ac_save_LIBS="$LIBS"
LIBS="-lpq $LIBS"
cat > conftest.$ac_ext <&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
+if { (eval echo configure:1078: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
rm -rf conftest*
eval "ac_cv_lib_$ac_lib_var=yes"
else
@@ -1089,7 +1109,7 @@
# Extract the first word of "gcc", so it can be a program name with args.
set dummy gcc; ac_word=$2
echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
-echo "configure:1093: checking for $ac_word" >&5
+echo "configure:1113: checking for $ac_word" >&5
if eval "t
Re: [Dbmail] dbmail 1.1 - autoconf issues
Here is another patch so that autoconf finds postgresql headers on debian machines. -- Ryan Butler <[EMAIL PROTECTED]> ADI Internet Solutions diff -ur dbmail/configure.in dbmail.working/configure.in --- dbmail/configure.in Fri Sep 13 08:56:44 2002 +++ dbmail.working/configure.in Fri Feb 7 15:34:46 2003 @@ -19,7 +19,7 @@ pgsqlheaderpaths="/usr/include/pgsql /usr/include /usr/local/include/pgsql \ /usr/local/include /usr/freeware/include/pgsql \ /usr/freeware/include $HOME/include $HOME/pgsql/include \ - /usr/local/pgsql/include $HOME" + /usr/local/pgsql/include /usr/include/postgresql $HOME" DBMAIL_BOTH_SQL_CHECK DBMAIL_CHECK_SQL_LIBS
Re: [Dbmail] dbmail 1.1 - autoconf issues
Ryan Butler wrote: Here is another patch so that autoconf finds postgresql headers on debian machines. Shouldn't files like Makefile.in and configure and all the other files that are generated by automake and autoconf be removed from cvs? Just an idea, since I know this is common practice in some other os-projects. -- Paul Stevens mailto:[EMAIL PROTECTED] NET FACILITIES GROUP PGP: finger [EMAIL PROTECTED] The Netherlandshttp://www.nfg.nl
Re: [Dbmail] dbmail 1.1 - autoconf issues
On Sat, 2003-02-08 at 06:56, Paul J Stevens wrote: > Ryan Butler wrote: > > >Here is another patch so that autoconf finds postgresql headers on > >debian machines. > > > Shouldn't files like Makefile.in and configure and all the other files > that are generated by automake > and autoconf be removed from cvs? Just an idea, since I know this is > common practice in some other > os-projects. Not really since they're part of the development process, and tracking their changes in cvs is just as valid... Some of the files could be removed from the releases (aclocal.m4, configure.in, Makefile.am, etc) Makefile.in and configure need to stay as it would be a useless build system without configure and configure reads Makefile.in to generate the Makefiles. So they must stay in cvs, and are optional for the releases. -- Ryan Butler <[EMAIL PROTECTED]> ADI Internet Solutions
[Dbmail] DBMAIl 1.1 release - final fixes
Hi all, last change request for 1.1: updating the 'version' defines/tags in the different files - where exactly is the version defined for automake? We'll be releasing dbmail 1.1 shortly afterwards. Furthermore: would anyone on this list be prepared to write an how-to for installing postfix+dbmail? Our aim is to have such an how-to placed on www.postfix.org - it would certainly help spreading out the dbmail usage :)) regards roel Met vriendelijke groet, Roel Rozendaal _ R.A. Rozendaal ICT Manager IC&S T: +31 30 2322878 F: +31 30 2322305 www.ic-s.nl
[Dbmail] dbmail 1.1 + postgreSQL + timestamp encoding
Hello, I've recently installed dbmail 1.1 on a Debian GNU/Linux machine (woody), using PostgreSQL 7.2.1. Everything works fine, except that Outlook 2002 SP2 (aka XP, German localization) shows "Sa 03.11.1979 00:00" "received" date for every single mail when used as an IMAP client. When looking at the source I came across the date_sql2imap routine (in imaputil.c) which expects the SQL server result set using a -mm-dd hh:mm:ss timestamp convention; unfortunately, my PostgreSQL deliveres "dd.mm.yyy hh:mm:ss TZ" I'm aware of the DATESTYLE option, but AFAIK this option can only be set system-wide, and since other applications are using the same PostgreSQL postmaster, I cannot alter the current setting (actually, I'm using German DATESYTLE as default) As a quick solution, I hacked pgsql/dbpgsql.c, adding an explicit cast to the expected timestamp format: --- ../dbmail-1.1-debian-orig/pgsql/dbpgsql.c Sat Mar 15 14:30:04 2003 +++ pgsql/dbpgsql.c Sat Mar 15 14:09:16 2003 @@ -3755,7 +3755,10 @@ char *row; - snprintf(query, DEF_QUERYSIZE, "SELECT internal_date FROM messages WHERE mailbox_idnr = %llu::bigint " + /* [EMAIL PROTECTED] Added missing to_char because otherwise date_sql2imap will break */ + snprintf(query, DEF_QUERYSIZE, + "SELECT to_char(internal_date, '-MM-DD HH24:MI:SS') " +"FROM messages WHERE mailbox_idnr = %llu::bigint " "AND message_idnr = %llu::bigint AND unique_id!=''", mailboxuid, msguid); if (db_query(query) == -1) (please note that I have applied the Debian patches provided by Paul J Stevens, too) Can anyone confirm whether my hack is neccessary? If not, what are the alternatives? BTW, Mozilla 1.3 doesn't care about internal IMAP dates, thus everything's just fine there. Thanks alot, Thomas
Re: [Dbmail] DBMAIl 1.1 release - final fixes
A quick grep shows... [snipped for interesting lines] [EMAIL PROTECTED] dbmail]$ grep -r "1\.0" * buildtools/configure:VERSION=1.0 buildtools/configure.in:AM_INIT_AUTOMAKE(dbmail-smtp, 1.0) configure.in:AM_INIT_AUTOMAKE(dbmail-smtp, 1.0) VERSION:This is DBMAIL version 1.0 The VERSION file is created manually, but configure is generated by the autotools, so just to update configure.in will do it... AM_INIT_AUTOMAKE(dbmail, 1.1) Of course, which configure.in? Umm... the one in dbmail/ says that the rest of the auto* files are in dbmail/buildtools/ which means... I'm confused :-P As far as I can tell, the duplicated things in buildtools/ are not needed, ie the extra configure.in, aclocal.m4, Makefile.am, etc. Best to check with a real autoconf expert, though, since I've only got a few weeks' worth of experience in writing autoconf scripts! Aaron On Fri, 14 Feb 2003, Roel Rozendaal - IC&S wrote: > Hi all, > > last change request for 1.1: updating the 'version' defines/tags in the > different files - where exactly is the version defined for automake? > We'll be releasing dbmail 1.1 shortly afterwards. > > Furthermore: would anyone on this list be prepared to write an how-to > for installing postfix+dbmail? Our aim is to have such an how-to placed > on www.postfix.org - it would certainly help spreading out the dbmail > usage :)) > > regards roel > > Met vriendelijke groet, > > > Roel Rozendaal > > > _ > R.A. Rozendaal > ICT Manager > IC&S > T: +31 30 2322878 > F: +31 30 2322305 > www.ic-s.nl > > ___ > Dbmail mailing list > Dbmail@dbmail.org > https://mailman.fastxs.nl/mailman/listinfo/dbmail >
Re: [Dbmail] DBMAIl 1.1 release - final fixes
On Fri, 2003-02-14 at 09:33, Aaron Stone wrote: > A quick grep shows... [snipped for interesting lines] > > [EMAIL PROTECTED] dbmail]$ grep -r "1\.0" * > buildtools/configure:VERSION=1.0 > buildtools/configure.in:AM_INIT_AUTOMAKE(dbmail-smtp, 1.0) > configure.in:AM_INIT_AUTOMAKE(dbmail-smtp, 1.0) > VERSION:This is DBMAIL version 1.0 > The simple solution is to change them everywhere, this is just a very basic automated build system autoconf, eventually we'll get to using the buildtools stuff, probably libtool, adding function substitution for functions that are detectes as missing, etc. This is just the "1st Draft that actually makes a useable build system" :) -- Ryan Butler <[EMAIL PROTECTED]> ADI Internet Solutions
