You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(10) |
Nov
(37) |
Dec
(66) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(52) |
Feb
(136) |
Mar
(65) |
Apr
(38) |
May
(46) |
Jun
(143) |
Jul
(60) |
Aug
(33) |
Sep
(79) |
Oct
(29) |
Nov
(13) |
Dec
(14) |
2006 |
Jan
(25) |
Feb
(26) |
Mar
(4) |
Apr
(9) |
May
(29) |
Jun
|
Jul
(9) |
Aug
(11) |
Sep
(10) |
Oct
(9) |
Nov
(45) |
Dec
(8) |
2007 |
Jan
(82) |
Feb
(61) |
Mar
(39) |
Apr
(7) |
May
(9) |
Jun
(16) |
Jul
(2) |
Aug
(22) |
Sep
(2) |
Oct
|
Nov
(4) |
Dec
(5) |
2008 |
Jan
|
Feb
|
Mar
(5) |
Apr
(2) |
May
(8) |
Jun
|
Jul
(10) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
(32) |
May
|
Jun
(7) |
Jul
|
Aug
(38) |
Sep
(3) |
Oct
|
Nov
(4) |
Dec
|
2010 |
Jan
(36) |
Feb
(32) |
Mar
(2) |
Apr
(19) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(6) |
Nov
(8) |
Dec
|
2011 |
Jan
(3) |
Feb
|
Mar
(5) |
Apr
|
May
(2) |
Jun
(1) |
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
(6) |
2012 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
|
Nov
(6) |
Dec
(10) |
2014 |
Jan
(8) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
(34) |
Aug
(6) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(18) |
Jul
(13) |
Aug
(30) |
Sep
(4) |
Oct
(1) |
Nov
|
Dec
(4) |
2016 |
Jan
(2) |
Feb
(10) |
Mar
(3) |
Apr
|
May
|
Jun
(11) |
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2017 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Bruce B. <bb...@bo...> - 2010-02-01 21:17:49
|
On Feb 1, 2010, at 3:10 PM, Kyle Lanclos wrote: > Lionel Bouton wrote: >> Isn't it a little too much work to get portability ? There was a >> temporary problem with a sed -i call, but are there any other >> portability problems (that can't be solved by installing the GNU >> tools >> or documenting some dependencies) ? > > It was a real hassle to work around all the hard-coded paths in > SQLgrey. > Honestly, cooking up this autoconf config took me less time than > trying > to work out the dependencies the hard way (try, fail, fix, try, > fail...). And speaking of both hard-coding AND running on a Mac in the same day, please allow me to share this recent post that I wrote on the "Do It Yourself Mac Server" blog at www.diymacserver.com: == To follow up on my earlier post of 24 Dec 09 wherein I reported a small anomaly regarding sqlgrey behavior when started from launchd… The sqlgrey author decided that when sqlgrey is NOT started as a daemon it should log to STDOUT as opposed to syslog, the way we Mac users want it. A few small code edits will get sqlgrey back to logging to mail.log and creating its pid file. Whether you’re using v1.6.8 or v1.7.6, load the sqlgrey executable into your favorite code editor. 1. To get logging back into mail.log, search for log_file => $opt{daemonize} ? 'Sys::Syslog' : undef, and change it to log_file => 'Sys::Syslog', 2. To get sqlgrey to write it’s pid file, necessary to allow the update_sqlgrey_config script to force re-reading it’s config files, search for pid_file => $opt{daemonize} ? $dflt{pidfile} : undef, and change it to pid_file => $dflt{pidfile}, Another benefit of the above code edits is that sqlgrey-logstats.pl will, once again, find its log entries in mail.log in the format that it is expecting. == Just thought the timing was right :-) B. Bodger Oklahoma City, OK |
From: Kyle L. <la...@uc...> - 2010-02-01 21:10:34
|
Lionel Bouton wrote: > Isn't it a little too much work to get portability ? There was a > temporary problem with a sed -i call, but are there any other > portability problems (that can't be solved by installing the GNU tools > or documenting some dependencies) ? It was a real hassle to work around all the hard-coded paths in SQLgrey. Honestly, cooking up this autoconf config took me less time than trying to work out the dependencies the hard way (try, fail, fix, try, fail...). > What worries me is that autoconf would be another thing to master in > order to contribute to the project (after a quick look I don't really > understand much of the content of the added files). I didn't understand autoconf to any useful degree before I started working on the autoconf config I just submitted. It looks worse than it is. --Kyle |
From: John T. <gma...@jt...> - 2010-02-01 21:02:49
|
On 02/01/2010 02:23 AM, Michal Ludvig wrote: > Hi all, > > I have reverted the infamous 'sed -i' Makefile change (sorry for that) > and released sqlgrey-1.8.0-rc2: > > https://sourceforge.net/projects/sqlgrey/files/sqlgrey-1.8%20%28stable%29/sqlgrey-1.8.0-rc2.tar.gz/download > > No other changes made, if -rc1 worked for you there is no need to > upgrade to -rc2. > > Michal > I tried to make an RPM, but I get errors. CentOS54[johnthomas00@srv ~]$ rpmbuild -ta sqlgrey-1.8.0-rc2.tar.gz error: line 7: Illegal char '-' in version: Version: 1.8.0-rc2 I tried a few other things, but they all produced the same result. Any suggestions? -- Sincerely, John Thomas |
From: Lionel B. <lio...@bo...> - 2010-02-01 20:50:28
|
Kyle Lanclos a écrit, le 02/01/2010 09:25 PM : > I wrote: > >> I've got a basic GNU autoconf scheme working with sqlgrey-1.8.0-rc1. >> > > ...and here it is. There's a fair number of steps involved. > > * The following files need to be renamed from 'filename' > to 'filename.in': > > Makefile > sqlgrey-logstats.pl > sqlgrey > sqlgrey.spec > tester.pl > update_sqlgrey_config > > * The attached patch needs to be applied, which modifies > all of the above-listed files to use @macro_definitions@ > instead of hard-coded path names. > > * There are three new files that land in the top-level source > directory (attached): > > aclocal.m4 > configure.ac > install-sh > > * The 'VERSION' file should be removed. The only place that the > version needs to be set is in configure.ac. If you really felt > like keeping the VERSION file around, rename it to VERSION.in, > etc. etc. etc. > > I would suggest invoking autoconf, and committing the resulting configure > script as part of the distributed source code, in addition to the above. > Yes, it doubles the total size of the package, and is amusing for that > reason. > > I did not do an exhaustive search through the source code base for > other hard-coded paths, so there may yet be more files that would > benefit from adopting this scheme. > > I also used arbitrary version numbers in configure.ac for the required > perl modules. Those are by no means real requirements. Someone that is > familiar with the usage of these modules might want to suggest more > realistic lower-bounds. > > The version requirement in configure.ac for a specific version of > autoconf (2.60), however, should be real. I confirmed that it does > not work with autoconf 2.59, but did my testing with autoconf 2.65. > It looks like 2.62 also works. > Isn't it a little too much work to get portability ? There was a temporary problem with a sed -i call, but are there any other portability problems (that can't be solved by installing the GNU tools or documenting some dependencies) ? What worries me is that autoconf would be another thing to master in order to contribute to the project (after a quick look I don't really understand much of the content of the added files). Lionel |
From: Richard <in...@ri...> - 2010-02-01 20:34:44
|
Thanks, this version works on the Mac again! Richard On 1 Feb 2010, at 11:23 AM, Michal Ludvig wrote: > Hi all, > > I have reverted the infamous 'sed -i' Makefile change (sorry for that) > and released sqlgrey-1.8.0-rc2: > > https://sourceforge.net/projects/sqlgrey/files/sqlgrey-1.8%20%28stable%29/sqlgrey-1.8.0-rc2.tar.gz/download > > No other changes made, if -rc1 worked for you there is no need to > upgrade to -rc2. > > Michal > > ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > http://p.sf.net/sfu/theplanet-com > _______________________________________________ > Sqlgrey-users mailing list > Sql...@li... > https://lists.sourceforge.net/lists/listinfo/sqlgrey-users > |
From: Kyle L. <la...@uc...> - 2010-02-01 20:25:34
|
I wrote: > I've got a basic GNU autoconf scheme working with sqlgrey-1.8.0-rc1. ...and here it is. There's a fair number of steps involved. * The following files need to be renamed from 'filename' to 'filename.in': Makefile sqlgrey-logstats.pl sqlgrey sqlgrey.spec tester.pl update_sqlgrey_config * The attached patch needs to be applied, which modifies all of the above-listed files to use @macro_definitions@ instead of hard-coded path names. * There are three new files that land in the top-level source directory (attached): aclocal.m4 configure.ac install-sh * The 'VERSION' file should be removed. The only place that the version needs to be set is in configure.ac. If you really felt like keeping the VERSION file around, rename it to VERSION.in, etc. etc. etc. I would suggest invoking autoconf, and committing the resulting configure script as part of the distributed source code, in addition to the above. Yes, it doubles the total size of the package, and is amusing for that reason. I did not do an exhaustive search through the source code base for other hard-coded paths, so there may yet be more files that would benefit from adopting this scheme. I also used arbitrary version numbers in configure.ac for the required perl modules. Those are by no means real requirements. Someone that is familiar with the usage of these modules might want to suggest more realistic lower-bounds. The version requirement in configure.ac for a specific version of autoconf (2.60), however, should be real. I confirmed that it does not work with autoconf 2.59, but did my testing with autoconf 2.65. It looks like 2.62 also works. I think these modifications (once properly thrashed around, of course) would be very helpful to include with the 1.8.0 release. --Kyle |
From: Karl O. P. <ko...@me...> - 2010-02-01 16:54:03
|
On 02/01/2010 02:17:01 AM, Michal Ludvig wrote: > Karl O. Pinc wrote: > > > Looks like sed -i isn't portable. It's probably a gnu extension. > > I just tried to install sqlgrey on my HP-UX box and indeed there are > more problems than just sed -i > > For instance the Makefile alone requires GNU make (gmake), the > original > HP-UX make didn't like it. > So ... do we aim to be completely installable without GNU tools? IMO there's a difference between having to install something like gmake, which does not overwrite anything in the existing command namespace, and having to replace something like sed. Karl <ko...@me...> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein |
From: Michal L. <ml...@lo...> - 2010-02-01 10:20:17
|
Hi all, I have reverted the infamous 'sed -i' Makefile change (sorry for that) and released sqlgrey-1.8.0-rc2: https://sourceforge.net/projects/sqlgrey/files/sqlgrey-1.8%20%28stable%29/sqlgrey-1.8.0-rc2.tar.gz/download No other changes made, if -rc1 worked for you there is no need to upgrade to -rc2. Michal |
From: Winfried N. <win...@ne...> - 2010-02-01 09:04:24
|
Hi, > I'm sure SPF awareness would be nice to have. > [...] >> SPF support is a recurrent topic. I'm surprised it comes again and >> again. There are 2 reasons why I don't think including it is a good thing: >> [...] >> I totally agree with Lionel. Things such as SPF should not be included into SQLgrey. SQLgrey is a greylisting daemon and following the KISS principles it shouldn't do anything else than this. Besides of this, if we wanna provide SPF support, we also need to make sure that SRS is supported as well. As SPF "breaks" the email forwarding, this might be a big issue for some SQLgrey users. Also there are some studies on the net, that the only users which really rely on SPF are SPAMers. Winni |
From: Michal L. <ml...@lo...> - 2010-02-01 08:14:07
|
Karl O. Pinc wrote: > Looks like sed -i isn't portable. It's probably a gnu extension. I just tried to install sqlgrey on my HP-UX box and indeed there are more problems than just sed -i For instance the Makefile alone requires GNU make (gmake), the original HP-UX make didn't like it. How's it on Solaris? Do you guys install it with make or with gmake? A while later it fails on "install -d -m ...". Apparently my 'install' requires different options to GNU install. So ... do we aim to be completely installable without GNU tools? At the moment we're failing regardless whether I revert the change or not (I did, don't worry ;-) Michal |
From: Kyle L. <la...@uc...> - 2010-02-01 04:08:33
|
Karl Pinc wrote: > And what role would [SPF records] play in greylisting? Where it would be helpful is in identifying diverse ranges of IP addresses that may represent a valid source for a given e-mail address, in the case of MTAs that do not re-send messages from the same IP address. I'm thinking of gmail when I say that. I agree wholeheartedly, with the notion that synchronous DNS lookups are likely too expensive to include as part of SQLgrey, or other similar greylisting implementations. It would be cleaner to have some kind of out-of-band, asynchronous mechanism (a cronjob) that would assert that a range of addresses represents, for the purposes of greylisting, a single source; currently, the out-of-band mechanism only allows for whitelisting. I think that using SPF records in this fashion would be preferable, in principle, to arbitrarily whitelisting. The trouble would be: how do you programmatically deterine which SPF records to query? Perhaps the asynchronous job could query the database for likely candidates, and similarly maintain a database of results. Only update records once a day for existing entries, that kind of thing. I'm thinking it would be a significant amount of work for a relatively modest return. --Kyle |
From: Kyle L. <la...@uc...> - 2010-02-01 03:55:12
|
I've got a basic GNU autoconf scheme working with sqlgrey-1.8.0-rc1. It solves problems like this, in that it eliminates the need to use sed as part of the build process. I'm hoping to make a few more refinements, and then pass it on for scrutiny. In particular, I want to add in testing for the relevant perl modules. Shouldn't take too long to work out, since someone already did the hard part: http://www.nongnu.org/autoconf-archive/ac_perl_module_version.html --Kyle |
From: Karl O. P. <ko...@me...> - 2010-02-01 03:04:05
|
On 01/31/2010 06:33:40 PM, Richard wrote: > Allright found the error but don't know how to solve it in the > intended manner. > > Replace in the makefile this part: > update-version: > sed -i 's/^my $$VERSION = .*;/my $$VERSION = "$(VERSION)";/' > sqlgrey > sed -i 's/^%define ver .*/%define ver $(VERSION)/' > sqlgrey.spec > sed -i 's/^my $$VERSION = .*;/my $$VERSION = "$(VERSION)";/' > sqlgrey-logstats.pl > > With the same code but not so elegant from an older version like > 1.7.6: > update-version: > cat sqlgrey | sed 's/^my $$VERSION = .*;/my $$VERSION = > "$(VERSION)";/' > sqlgrey.new > mv sqlgrey.new sqlgrey > chmod a+x sqlgrey > cat sqlgrey.spec | sed 's/^%define ver .*/%define ver > $(VERSION)/' > sqlgrey.spec.new > mv sqlgrey.spec.new sqlgrey.spec > cat sqlgrey-logstats.pl | sed 's/^my $$VERSION = .*;/my > $$VERSION = "$(VERSION)";/' > sqlgrey-logstats.pl.new > mv sqlgrey-logstats.pl.new sqlgrey-logstats.pl > chmod a+x sqlgrey-logstats.pl Looks like sed -i isn't portable. It's probably a gnu extension. You don't find it in openbsd's sed. I'd say the makefile should be more portable. How about?: ( ;# Run in a subshell just to cleanup early. tfile=sqlgrey.$$ function cleanup () rm -f $tfile trap cleanup EXIT sed 's/^my $$VERSION = .*;/my $$VERSION = "$(VERSION)";/' sqlgrey > $tfile \ && cat $tfile > sqlgrey sed 's/^%define ver .*/%define ver $(VERSION)/' sqlgrey.spec > $tfile \ && cat $tfile > sqlgrey.spec sed 's/^my $$VERSION = .*;/my $$VERSION = "$(VERSION)";/' sqlgrey-logstats.pl > $tfile \ && cat $tfile > sqlgrey-logstats.pl ) Note also that it's probably not a good idea to rely on the file permissions in the tarball. The better approach is to use the install program and set the bits as desired on install. (But the above code does preserve all permissions.) If this was cleaned up I'd get rid of the whole $tfile thing and have the input files named autoconf-ish: sqlgrey.in, sqlgrey.spec.in, etc. and just sed right into the target file (sqlgrey, sqlgrey.spec, etc.). Karl <ko...@me...> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein |
From: Karl O. P. <ko...@me...> - 2010-02-01 02:45:43
|
On 01/31/2010 08:31:25 AM, Lionel Bouton wrote: > Michal Ludvig a écrit, le 01/28/2010 04:55 AM : > > [...] > > I'm sure SPF awareness would be nice to have. > > SPF support is a recurrent topic. I'm surprised it comes again and > again. There are 2 reasons why I don't think including it is a good > thing : And what role would it play in greylisting? (Which is the only thing sqlgrey should be doing.) I can't see the presence or absence of an SPF record being anything I'd want to trigger turning greylisting on or off. Karl <ko...@me...> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein |
From: Richard <in...@ri...> - 2010-02-01 00:52:23
|
Allright found the error but don't know how to solve it in the intended manner. Replace in the makefile this part: update-version: sed -i 's/^my $$VERSION = .*;/my $$VERSION = "$(VERSION)";/' sqlgrey sed -i 's/^%define ver .*/%define ver $(VERSION)/' sqlgrey.spec sed -i 's/^my $$VERSION = .*;/my $$VERSION = "$(VERSION)";/' sqlgrey-logstats.pl With the same code but not so elegant from an older version like 1.7.6: update-version: cat sqlgrey | sed 's/^my $$VERSION = .*;/my $$VERSION = "$(VERSION)";/' > sqlgrey.new mv sqlgrey.new sqlgrey chmod a+x sqlgrey cat sqlgrey.spec | sed 's/^%define ver .*/%define ver $(VERSION)/' > sqlgrey.spec.new mv sqlgrey.spec.new sqlgrey.spec cat sqlgrey-logstats.pl | sed 's/^my $$VERSION = .*;/my $$VERSION = "$(VERSION)";/' > sqlgrey-logstats.pl.new mv sqlgrey-logstats.pl.new sqlgrey-logstats.pl chmod a+x sqlgrey-logstats.pl I'm not an expert on sed but somehow the workings of sed on a Mac are different. That's why you can't get it installed. Hope this helps. Richard On 31 Jan 2010, at 9:10 PM, Richard wrote: > I had not tried the latest version, will take a look at it. If no one else finds the answer first ;-0 > > R > > On 31 Jan 2010, at 9:08 PM, Steve Martin wrote: > >> Yes, in fact I've had a working install of 1.7.6 for some time. The problem is when I get here... >> >> -- >> If youve downloaded SQLGrey from sourceforge please unpack it and ‘cd’ into the directory and run the following commands: >> >> make >> sudo make install >> -- >> >> The "sudo make install" fails as I described. >> >> >> On Jan 31, 2010, at 1:39 PM, Richard wrote: >> >>> Steven, >>> >>> Have you tried these instructions? >>> http://diymacserver.com/installing-the-mailserver/setting-up-greylisting-with-sqlgrey/ >>> >>> They worked for me. >>> >>> Richard >>> >>> On 31 Jan 2010, at 5:40 PM, Steve Martin wrote: >>> >>>> I get the following error when trying to install the latest sqlgrey. MacOS X 10.5.8. >>>> >>>> >>>> mail2:sqlgrey-1.8.0-rc1 cheezmo$ sudo make install >>>> perldoc -u sqlgrey | pod2man -n sqlgrey > sqlgrey.1 >>>> sed -i 's/^my $VERSION = .*;/my $VERSION = "1.8.0-rc1";/' sqlgrey >>>> sed: 1: "sqlgrey": unterminated substitute pattern >>>> make: *** [update-version] Error 1 >>>> >>>> -- >>>> Steve Martin >>>> st...@pl... >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> The Planet: dedicated and managed hosting, cloud storage, colocation >>>> Stay online with enterprise data centers and the best network in the business >>>> Choose flexible plans and management services without long-term contracts >>>> Personal 24x7 support from experience hosting pros just a phone call away. >>>> http://p.sf.net/sfu/theplanet-com >>>> _______________________________________________ >>>> Sqlgrey-users mailing list >>>> Sql...@li... >>>> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users >>>> >>> >>> >>> ------------------------------------------------------------------------------ >>> The Planet: dedicated and managed hosting, cloud storage, colocation >>> Stay online with enterprise data centers and the best network in the business >>> Choose flexible plans and management services without long-term contracts >>> Personal 24x7 support from experience hosting pros just a phone call away. >>> http://p.sf.net/sfu/theplanet-com >>> _______________________________________________ >>> Sqlgrey-users mailing list >>> Sql...@li... >>> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users >>> >> >> -- >> Steve Martin >> st...@pl... >> >> >> >> ------------------------------------------------------------------------------ >> The Planet: dedicated and managed hosting, cloud storage, colocation >> Stay online with enterprise data centers and the best network in the business >> Choose flexible plans and management services without long-term contracts >> Personal 24x7 support from experience hosting pros just a phone call away. >> http://p.sf.net/sfu/theplanet-com >> _______________________________________________ >> Sqlgrey-users mailing list >> Sql...@li... >> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users >> > > > ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > http://p.sf.net/sfu/theplanet-com > _______________________________________________ > Sqlgrey-users mailing list > Sql...@li... > https://lists.sourceforge.net/lists/listinfo/sqlgrey-users > |
From: Richard <in...@ri...> - 2010-01-31 20:11:20
|
I had not tried the latest version, will take a look at it. If no one else finds the answer first ;-0 R On 31 Jan 2010, at 9:08 PM, Steve Martin wrote: > Yes, in fact I've had a working install of 1.7.6 for some time. The problem is when I get here... > > -- > If youve downloaded SQLGrey from sourceforge please unpack it and ‘cd’ into the directory and run the following commands: > > make > sudo make install > -- > > The "sudo make install" fails as I described. > > > On Jan 31, 2010, at 1:39 PM, Richard wrote: > >> Steven, >> >> Have you tried these instructions? >> http://diymacserver.com/installing-the-mailserver/setting-up-greylisting-with-sqlgrey/ >> >> They worked for me. >> >> Richard >> >> On 31 Jan 2010, at 5:40 PM, Steve Martin wrote: >> >>> I get the following error when trying to install the latest sqlgrey. MacOS X 10.5.8. >>> >>> >>> mail2:sqlgrey-1.8.0-rc1 cheezmo$ sudo make install >>> perldoc -u sqlgrey | pod2man -n sqlgrey > sqlgrey.1 >>> sed -i 's/^my $VERSION = .*;/my $VERSION = "1.8.0-rc1";/' sqlgrey >>> sed: 1: "sqlgrey": unterminated substitute pattern >>> make: *** [update-version] Error 1 >>> >>> -- >>> Steve Martin >>> st...@pl... >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> The Planet: dedicated and managed hosting, cloud storage, colocation >>> Stay online with enterprise data centers and the best network in the business >>> Choose flexible plans and management services without long-term contracts >>> Personal 24x7 support from experience hosting pros just a phone call away. >>> http://p.sf.net/sfu/theplanet-com >>> _______________________________________________ >>> Sqlgrey-users mailing list >>> Sql...@li... >>> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users >>> >> >> >> ------------------------------------------------------------------------------ >> The Planet: dedicated and managed hosting, cloud storage, colocation >> Stay online with enterprise data centers and the best network in the business >> Choose flexible plans and management services without long-term contracts >> Personal 24x7 support from experience hosting pros just a phone call away. >> http://p.sf.net/sfu/theplanet-com >> _______________________________________________ >> Sqlgrey-users mailing list >> Sql...@li... >> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users >> > > -- > Steve Martin > st...@pl... > > > > ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > http://p.sf.net/sfu/theplanet-com > _______________________________________________ > Sqlgrey-users mailing list > Sql...@li... > https://lists.sourceforge.net/lists/listinfo/sqlgrey-users > |
From: Steve M. <st...@pl...> - 2010-01-31 20:08:13
|
Yes, in fact I've had a working install of 1.7.6 for some time. The problem is when I get here... -- If youve downloaded SQLGrey from sourceforge please unpack it and ‘cd’ into the directory and run the following commands: make sudo make install -- The "sudo make install" fails as I described. On Jan 31, 2010, at 1:39 PM, Richard wrote: > Steven, > > Have you tried these instructions? > http://diymacserver.com/installing-the-mailserver/setting-up-greylisting-with-sqlgrey/ > > They worked for me. > > Richard > > On 31 Jan 2010, at 5:40 PM, Steve Martin wrote: > >> I get the following error when trying to install the latest sqlgrey. MacOS X 10.5.8. >> >> >> mail2:sqlgrey-1.8.0-rc1 cheezmo$ sudo make install >> perldoc -u sqlgrey | pod2man -n sqlgrey > sqlgrey.1 >> sed -i 's/^my $VERSION = .*;/my $VERSION = "1.8.0-rc1";/' sqlgrey >> sed: 1: "sqlgrey": unterminated substitute pattern >> make: *** [update-version] Error 1 >> >> -- >> Steve Martin >> st...@pl... >> >> >> >> ------------------------------------------------------------------------------ >> The Planet: dedicated and managed hosting, cloud storage, colocation >> Stay online with enterprise data centers and the best network in the business >> Choose flexible plans and management services without long-term contracts >> Personal 24x7 support from experience hosting pros just a phone call away. >> http://p.sf.net/sfu/theplanet-com >> _______________________________________________ >> Sqlgrey-users mailing list >> Sql...@li... >> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users >> > > > ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > http://p.sf.net/sfu/theplanet-com > _______________________________________________ > Sqlgrey-users mailing list > Sql...@li... > https://lists.sourceforge.net/lists/listinfo/sqlgrey-users > -- Steve Martin st...@pl... |
From: Richard <in...@ri...> - 2010-01-31 19:56:57
|
Steven, Have you tried these instructions? http://diymacserver.com/installing-the-mailserver/setting-up-greylisting-with-sqlgrey/ They worked for me. Richard On 31 Jan 2010, at 5:40 PM, Steve Martin wrote: > I get the following error when trying to install the latest sqlgrey. MacOS X 10.5.8. > > > mail2:sqlgrey-1.8.0-rc1 cheezmo$ sudo make install > perldoc -u sqlgrey | pod2man -n sqlgrey > sqlgrey.1 > sed -i 's/^my $VERSION = .*;/my $VERSION = "1.8.0-rc1";/' sqlgrey > sed: 1: "sqlgrey": unterminated substitute pattern > make: *** [update-version] Error 1 > > -- > Steve Martin > st...@pl... > > > > ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > http://p.sf.net/sfu/theplanet-com > _______________________________________________ > Sqlgrey-users mailing list > Sql...@li... > https://lists.sourceforge.net/lists/listinfo/sqlgrey-users > |
From: Steve M. <st...@pl...> - 2010-01-31 16:56:45
|
I get the following error when trying to install the latest sqlgrey. MacOS X 10.5.8. mail2:sqlgrey-1.8.0-rc1 cheezmo$ sudo make install perldoc -u sqlgrey | pod2man -n sqlgrey > sqlgrey.1 sed -i 's/^my $VERSION = .*;/my $VERSION = "1.8.0-rc1";/' sqlgrey sed: 1: "sqlgrey": unterminated substitute pattern make: *** [update-version] Error 1 -- Steve Martin st...@pl... |
From: Lionel B. <lio...@bo...> - 2010-01-31 14:31:40
|
Michal Ludvig a écrit, le 01/28/2010 04:55 AM : > [...] > I'm sure SPF awareness would be nice to have. SPF support is a recurrent topic. I'm surprised it comes again and again. There are 2 reasons why I don't think including it is a good thing : - I'm not sure there are efficient SPAM-fighting behaviours we can implement based on SPF records that wouldn't be possible by configuring Postfix with a separate SPF policy service, - SQLgrey treats incoming mails sequentially. It can do so because it only uses very-low latency queries, querying SPF records is orders of magnitude slower. For people with more than a few mails/minute, SQLgrey+SPF will become a bottleneck. Lionel |
From: Michal L. <ml...@lo...> - 2010-01-28 03:54:32
|
Hi Kyle, On 01/23/2010 08:44 AM, Kyle Lanclos wrote: > What about including some of the modifications posted here: > > http://article.gmane.org/gmane.mail.postfix.sqlgrey/1033 I wasn't aware of these... > ...in particular, the bits relating to logging? Those strike me as > cross-platform improvements, and are 100% required to get sqlgrey > functioning on Solaris. Is this compatible with other Unix/Linux brands? > Are the bits related to SPF functionality desirable? That sounds > like a keen feature, even if I'm not a fan of how the dependency > list grows exponentially when you require Mail::SPF::Query. I'm sure SPF awareness would be nice to have. Ideally make it an optional feature with an optional dependency. Have a look at my smtp-cli script (http://smtp-cli.logix.cz) that has an optional mode for composing messages from the command line arguments. If the required modules are not found the feature is not available: ## MIME::Lite dependency is optional my $mime_lite = eval { require MIME::Lite; 1; }; if (not $mime_lite) { warn("!!! MIME::Lite -- optional module not found\n"); } Later on in the script it checks for $mime_lite before going down the path where the module is needed. > There are a lot of other small things I'm working against to get > sqlgrey working on Solaris, and after working through enough of > them, it's starting to get frustrating. It would be nice if these > problems were solved with a basic autoconf setup, but it's not the > same class of show-stopper. I'm keen to accept patches that fix your problems, provided they won't break sqlgrey for non-Solaris users. > In particular, it would be nice if > further GNU-isms are not assumed (for example, invoking sed -i in > the Makefile) Oops, my bad. Will fix that. > I've attached a patch to sqlgrey that contains the modifcations to > the previously-posted logging behavior against the 1.8.0-rc1 release. Thanks. I will have a look at it. Michal |
From: Kyle L. <la...@uc...> - 2010-01-22 19:44:46
|
Michal Ludvig wrote: > While setting up a new mail server today and realised that the most > recent SQLgrey has only ever existed in GIT and was never released as a > package. We also agreed some time ago that it's time for a new stable > release. What about including some of the modifications posted here: http://article.gmane.org/gmane.mail.postfix.sqlgrey/1033 ...in particular, the bits relating to logging? Those strike me as cross-platform improvements, and are 100% required to get sqlgrey functioning on Solaris. Are the bits related to SPF functionality desirable? That sounds like a keen feature, even if I'm not a fan of how the dependency list grows exponentially when you require Mail::SPF::Query. There are a lot of other small things I'm working against to get sqlgrey working on Solaris, and after working through enough of them, it's starting to get frustrating. It would be nice if these problems were solved with a basic autoconf setup, but it's not the same class of show-stopper. In particular, it would be nice if further GNU-isms are not assumed (for example, invoking sed -i in the Makefile) without some method of first asserting whether the local system supports such an option. I've attached a patch to sqlgrey that contains the modifcations to the previously-posted logging behavior against the 1.8.0-rc1 release. --Kyle |
From: Michal L. <ml...@lo...> - 2010-01-22 14:11:31
|
Hi all, While setting up a new mail server today and realised that the most recent SQLgrey has only ever existed in GIT and was never released as a package. We also agreed some time ago that it's time for a new stable release. Ladies and Gentlemen ... here comes... SQLgrey 1.8.0-rc1 ! The main update from 1.7.6 is a completely reworked IPv6 handling - now it should actually work as good as IPv4, including whitelists, etc. For now it's an RC (release candidate) but I'm not aware of any problems, it should be as production ready as 1.7.6. Download from SourceForge: http://downloads.sourceforge.net/project/sqlgrey/sqlgrey-1.8%20%28stable%29/sqlgrey-1.8.0-rc1.tar.gz Michal |
From: Lionel B. <lio...@bo...> - 2010-01-21 18:53:55
|
Lionel Bouton a écrit, le 01/21/2010 07:37 PM : > Bill McGonigle a écrit, le 01/21/2010 07:06 PM : > >> Hi, Larry, >> >> On 01/20/2010 04:13 PM, Larry Coker wrote: >> >> >>> I work for a registrar and I can renew the names in Lionel's name at no >>> charge. We use SQLGrey and would be happy to support it in this small way. >>> >>> >> Super. I can keep the redirects up or you can handle it, whichever is >> easiest for you. Feel free to initiate a transfer, I'll unlock. >> >> >> > > I'd prefer to have it under direct control (ie: I'll pay for it myself). > I just initiated a transfer using Gandi. Lionel |
From: Lionel B. <lio...@bo...> - 2010-01-21 18:37:22
|
Bill McGonigle a écrit, le 01/21/2010 07:06 PM : > Hi, Larry, > > On 01/20/2010 04:13 PM, Larry Coker wrote: > >> I work for a registrar and I can renew the names in Lionel's name at no >> charge. We use SQLGrey and would be happy to support it in this small way. >> > > Super. I can keep the redirects up or you can handle it, whichever is > easiest for you. Feel free to initiate a transfer, I'll unlock. > > I'd prefer to have it under direct control (ie: I'll pay for it myself). Lionel |