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: Kyle L. <la...@uc...> - 2010-04-05 17:08:28
|
Bruce Bodger wrote: > Thanks a lot for that, Kyle. But are they all "misbehaved"... i.e. do > they all warrant adding to the whitelist? I don't know. After whitelisting Google's SPF record (which includes something like 70,000 /24 address blocks), I didn't feel so ambivalent about whitelisting AOL's server list. With whitelisting, one has to hope that the odds are in favor of the whitelisted IP or IP range remaining free of spam-bots. In general, for addresses assigned to mail servers, this is likely to be the case. I realize this breaks the generality of the greylisting, but does not appear to have a measurable impact on the overall effectiveness. --Kyle |
From: Bruce B. <bb...@bo...> - 2010-04-05 15:17:58
|
> >> Since, as you state, SQLgrey only looks >> to the right of the "@" symbol, adding 64.12.206 to my >> clients_ip_whitelist.local might be the cleanest way. > > For what it's worth, you'll probably have to add more than that. The > list > used by SQLgrey to whitelist AOL is a bit stale; this is, to my > knowledge, > the authoritative declaration of AOL's outbound mail servers: > > http://postmaster.aol.com/servers/imo.html Thanks a lot for that, Kyle. But are they all "misbehaved"... i.e. do they all warrant adding to the whitelist? Regards, Bruce |
From: Kyle L. <la...@uc...> - 2010-04-05 14:34:50
|
Bruce Bodger wrote: > Since, as you state, SQLgrey only looks > to the right of the "@" symbol, adding 64.12.206 to my > clients_ip_whitelist.local might be the cleanest way. For what it's worth, you'll probably have to add more than that. The list used by SQLgrey to whitelist AOL is a bit stale; this is, to my knowledge, the authoritative declaration of AOL's outbound mail servers: http://postmaster.aol.com/servers/imo.html --Kyle |
From: Bruce B. <bb...@bo...> - 2010-04-05 13:57:13
|
On Apr 4, 2010, at 4:20 PM, Winfried Neessen wrote: > Hi, > > Bruce Bodger schrieb: >> >> What would be the suggested way to whitelist a singular email >> address? May I simply add, jo...@ao..., to >> clients_fqdn_whitelist.local or would I have to add it as a regex, >> such as /^(johndoe)\@aol.com/ > Non of the examples you mentioned. SQLgrey doesn't look at email > addresses, but only > at hostnames/ip address of sending servers. If you really wanna > whitelist that email > address, you should put some postfix exception rule in place, that > will whiteliste the > mail before sqlgrey can block it (though this isn't a really good > idea). Thank you for the reply, Winni. Since, as you state, SQLgrey only looks to the right of the "@" symbol, adding 64.12.206 to my clients_ip_whitelist.local might be the cleanest way. Regards, Bruce |
From: Winfried N. <win...@ne...> - 2010-04-04 21:36:49
|
Hi, Bruce Bodger schrieb: > What would be the suggested way to whitelist a singular email > address? May I simply add, jo...@ao..., to > clients_fqdn_whitelist.local or would I have to add it as a regex, > such as /^(johndoe)\@aol.com/ I can not find any example of > this in either the documentation or the bundled version of > clients_fqdn_whitelist. > > Non of the examples you mentioned. SQLgrey doesn't look at email addresses, but only at hostnames/ip address of sending servers. If you really wanna whitelist that email address, you should put some postfix exception rule in place, that will whiteliste the mail before sqlgrey can block it (though this isn't a really good idea). Winni -- Winfried Neessen Peter-Bauer-Str. 9 50823 Cologne Phone: +49 221 2612601 Fax: +49 221 2612602 eMail: win...@ne... PGP/GPG Key-ID: 0xda5cd8ef |
From: Bruce B. <bb...@bo...> - 2010-04-04 16:18:32
|
Happy Easter to all! What would be the suggested way to whitelist a singular email address? May I simply add, jo...@ao..., to clients_fqdn_whitelist.local or would I have to add it as a regex, such as /^(johndoe)\@aol.com/ I can not find any example of this in either the documentation or the bundled version of clients_fqdn_whitelist. P.S. I see that some AOL common pool servers are whitelisted in the distributed clients_ip_whitelist... 64.12.137 # AOL (common pool) - http://postmaster.aol.com/ servers/imo.html 64.12.138 # AOL (common pool) 152.163.225 # AOL (common pool) 205.188.139.136 # AOL (common pool) 205.188.139.137 # AOL (common pool) 205.188.144.207 # AOL (common pool) 205.188.144.208 # AOL (common pool) 205.188.156.66 # AOL (common pool) 205.188.157 # AOL (common pool) 205.188.159.7 # AOL (common pool) However, in this case the email came in from 64.12.206. I'm reluctant to add 64.12.206 to clients_ip_whiltelist.local without direction from a more experienced sqlgrey user. I fear it may inadvertently "over-whiten" my installation. Thank you, B. Bodger Oklahoma City, OK |
From: Lionel B. <lio...@bo...> - 2010-03-15 15:35:31
|
The Mon, 15 Mar 2010 15:20:00 +0100, Bastien LAMOUREUX <ba...@yo...> wrote: > Hi, using SQLGrey Version: 1.6.8-1 since a 10 days on our > production setup, receiving around 600 000 message per day. 2 > servers hosting sqlgrey and 1 backend postgreSQL DB for sqlgrey. It > does work really great, thanks for this great tool ;) > > > Only little problem, I wanna solve is that really rarely (most of > time, 1 or 2 times a day, sometimes 0), SQLGrey does encounter a > concatenation problem and does not succeed to enter some data in DB. > This does trigger a lost connection and reconnection event, therefore > sending me an email to tell me that connection to database was lost > and a second one one second later to tell me that connection is back. > > I identified 2 mails which triggered this kind of problem . Any idea > of what was so special with theses 2 emails? Or a way to tell SQLGrey > to wait for 3 or 4 lost connections before sending alert email? > (false positive are a bit annoying) What probably happened is that the origin server contacted both MX at nearly the same time (spam servers are known to do this). The first MX managed to recognize the email and remove it from the connect table before the second MX tried to fetch the entry in the same connect table. This case is hard to detect and we don't have any workable solution in the code yet. Lionel |
From: Bastien L. <ba...@yo...> - 2010-03-15 14:33:09
|
Hi, using SQLGrey Version: 1.6.8-1 since a 10 days on our production setup, receiving around 600 000 message per day. 2 servers hosting sqlgrey and 1 backend postgreSQL DB for sqlgrey. It does work really great, thanks for this great tool ;) Only little problem, I wanna solve is that really rarely (most of time, 1 or 2 times a day, sometimes 0), SQLGrey does encounter a concatenation problem and does not succeed to enter some data in DB. This does trigger a lost connection and reconnection event, therefore sending me an email to tell me that connection to database was lost and a second one one second later to tell me that connection is back. I identified 2 mails which triggered this kind of problem . Any idea of what was so special with theses 2 emails? Or a way to tell SQLGrey to wait for 3 or 4 lost connections before sending alert email? (false positive are a bit annoying) Mar 15 15:09:02 PHMCSMTP02 sqlgrey: grey: get_reconnect_delay error: no connect in database for web...@de..., 78.40.49, adm...@de... Mar 15 15:09:02 PHMCSMTP02 sqlgrey: warning: Use of uninitialized value $delay in concatenation (.) or string at /usr/sbin/sqlgrey line 2053. Mar 15 15:09:02 PHMCSMTP02 sqlgrey: grey: reconnect ok: 78.40.49(78.40.49.241), web...@de... -> adm...@de... () Mar 15 15:09:02 PHMCSMTP02 sqlgrey: grey: from awl: 78.40.49, web...@de... added Mar 15 15:09:02 PHMCSMTP02 postfix/pickup[15438]: DE3F311C9FB: uid=111 from=<sqlgrey> Mar 15 15:09:02 PHMCSMTP02 sqlgrey: warning: Use of uninitialized value $DBI::errstr in concatenation (.) or string at /usr/sbin/sqlgrey line 237. Mar 15 15:09:02 PHMCSMTP02 sqlgrey: dbaccess: warning: couldn't do query:#012INSERT INTO from_awl (sender_name, sender_domain, src, first_seen, last_seen) VALUES('webmaster','de cade.fr','78.40.49','error: nothing in connect',NOW()):#012, reconnecting to DB Mar 10 20:56:48 PHMCSMTP02 sqlgrey: grey: reconnect ok: 88.191.81(88.191.81.9), bo...@ph... -> vg...@ka... (00:08:25.241069) Mar 10 20:56:48 PHMCSMTP02 sqlgrey: grey: from awl: 88.191.81, bo...@ph... added Mar 10 20:56:48 PHMCSMTP02 postfix/pickup[18078]: 94CF911C9FC: uid=111 from=<sqlgrey> Mar 10 20:56:48 PHMCSMTP02 sqlgrey: warning: Use of uninitialized value $DBI::errstr in concatenation (.) or string at /usr/sbin/sqlgrey line 237. Mar 10 20:56:48 PHMCSMTP02 sqlgrey: dbaccess: warning: couldn't do query:#012INSERT INTO from_awl (sender_name, sender_domain, src, first_seen, last_seen) VALUES('bounce','phpli st.fr','88.191.81','2010-03-10 20:52:12.482616',NOW()):#012, reconnecting to DB Mar 10 20:56:48 PHMCSMTP02 postfix/qmgr[12199]: 94CF911C9FC: from=<sq...@PH...rp>, size=441, nrcpt=1 (queue active) Thanks Bastien |
From: Karl O. P. <ko...@me...> - 2010-02-09 17:21:40
|
On 02/09/2010 11:00:53 AM, Craig White wrote: > On Tue, 2010-02-09 at 10:04 -0600, Karl O. Pinc wrote: > > On 02/09/2010 08:50:05 AM, Craig White wrote: > > > > > > > Feb 9 05:52:22 li34-197 sqlgrey: warning: Use of > uninitialized > > > value > > > > > $DBI::errstr in concatenation (.) or string at > /usr/sbin/sqlgrey > > > line > > > > > 227. > > > > Have you searched the list archives? This looks familiar. > ---- > I think the problem was my creation. I created it as UTF8 and when I > dropped it and created it as a latin type, it worked. > But then I believe you have problems with internationalized domains. It's a mysql related problem. Definitely already discussed in the list archives. I forget the details. Karl <ko...@me...> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein |
From: Craig W. <cra...@az...> - 2010-02-09 17:01:02
|
On Tue, 2010-02-09 at 10:04 -0600, Karl O. Pinc wrote: > On 02/09/2010 08:50:05 AM, Craig White wrote: > > > > > Feb 9 05:52:22 li34-197 sqlgrey: warning: Use of uninitialized > > value > > > > $DBI::errstr in concatenation (.) or string at /usr/sbin/sqlgrey > > line > > > > 227. > > > > Feb 9 05:52:22 li34-197 sqlgrey: dbaccess: warning: couldn't do > > > > query:#012CREATE TABLE from_awl (sender_name varchar(64) NOT > > NULL, > > > > sender_domain varchar(255) NOT NULL, src varchar(39) NOT NULL, > > > > first_seen timestamp NOT NULL, last_seen timestamp NOT NULL, > > PRIMARY > > > > KEY > > > > (src, sender_domain, sender_name)):#012, reconnecting to DB > > > > Feb 9 05:52:22 li34-197 sqlgrey: mail: failed to send: No child > > > > processes#012 > > > > Feb 9 05:52:22 li34-197 sqlgrey: fatal: create_from_awl_table > > error > > > > at /usr/sbin/sqlgrey line 176. > > > > > > Have you searched the list archives? This looks familiar. ---- I think the problem was my creation. I created it as UTF8 and when I dropped it and created it as a latin type, it worked. Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |
From: Craig W. <cra...@az...> - 2010-02-09 16:52:38
|
the only 'non-commented' lines are... db_type = mysql db_name = sqlgrey db_user = sqlgrey db_pass = (REMOVED) Craig On Tue, 2010-02-09 at 16:23 +0100, Winfried Neessen wrote: > What does your config look like? > > -----Original Message----- > From: Craig White [mailto:cra...@az...] > Sent: Tuesday, February 09, 2010 3:50 PM > To: SQLgrey users mailing-list > Subject: Re: [Sqlgrey-users] strange install problem > > Sorry... should have provided the info > > Mysql, yes, the user 'sqlgrey' can connect and has privileges to create > the necessary tables. > > # mysql sqlgrey -h localhost -u sqlgrey -p > Enter password: > Welcome to the MySQL monitor. Commands end with ; or \g. > Your MySQL connection id is 281 > Server version: 5.1.42 Source distribution > > Type 'help;' or '\h' for help. Type '\c' to clear the current input > statement. > > perl-DBD-MySQL-4.010-1.fc11.i586 > > I'm still wondering why it doesn't work. > > Craig > > On Tue, 2010-02-09 at 08:56 +0100, Winfried Neessen wrote: > > Hi, > > > > looks like DBI isn't able to create the tables. Which database are you > > > using?Did you install the corresponding DBD::<dbtype> module? > > > > Does the DB user have permissions to create tables? > > > > Winni > > > > -- > > > > Sent from my wireless handheld device > > > > Am 09.02.2010 um 06:54 schrieb Craig White <cra...@az...>: > > > > > sqlgrey-1.6.7-1.noarch > > > > > > perl-DBI-1.607-2.fc11.i586 > > > > > > logs say... > > > Feb 9 05:52:22 li34-197 sqlgrey: 2010/02/09-05:52:22 sqlgrey (type > > > Net::Server::Multiplex) starting! pid(9629) > > > Feb 9 05:52:22 li34-197 sqlgrey: Binding to TCP port 2501 on host > > > localhost#012 > > > Feb 9 05:52:22 li34-197 sqlgrey: Setting gid to "504 504" > > > Feb 9 05:52:22 li34-197 sqlgrey: Setting uid to "504" > > > Feb 9 05:52:22 li34-197 sqlgrey: warning: Use of uninitialized > value > > > $DBI::errstr in concatenation (.) or string at /usr/sbin/sqlgrey > line > > > 227. > > > Feb 9 05:52:22 li34-197 sqlgrey: dbaccess: warning: couldn't do > > > query:#012CREATE TABLE from_awl (sender_name varchar(64) NOT NULL, > > > sender_domain varchar(255) NOT NULL, src varchar(39) NOT NULL, > > > first_seen timestamp NOT NULL, last_seen timestamp NOT NULL, PRIMARY > > > > KEY > > > (src, sender_domain, sender_name)):#012, reconnecting to DB > > > Feb 9 05:52:22 li34-197 sqlgrey: mail: failed to send: No child > > > processes#012 > > > Feb 9 05:52:22 li34-197 sqlgrey: fatal: create_from_awl_table error > > > at /usr/sbin/sqlgrey line 176. > > > > > > and I really don't think it's anything that I did in sqlgrey.conf > > > > > > do I have to go to an older version? > > > > > > Craig > > > > > > > > > -- > > > This message has been scanned for viruses and > > > dangerous content by MailScanner, and is > > > believed to be clean. > > > > > > > > > --- > > > --- > > > --- > > > > --------------------------------------------------------------------- > > > 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 > > > > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > > ------------------------------------------------------------------------ > ------ > 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 > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |
From: Karl O. P. <ko...@me...> - 2010-02-09 16:04:32
|
On 02/09/2010 08:50:05 AM, Craig White wrote: > > > Feb 9 05:52:22 li34-197 sqlgrey: warning: Use of uninitialized > value > > > $DBI::errstr in concatenation (.) or string at /usr/sbin/sqlgrey > line > > > 227. > > > Feb 9 05:52:22 li34-197 sqlgrey: dbaccess: warning: couldn't do > > > query:#012CREATE TABLE from_awl (sender_name varchar(64) NOT > NULL, > > > sender_domain varchar(255) NOT NULL, src varchar(39) NOT NULL, > > > first_seen timestamp NOT NULL, last_seen timestamp NOT NULL, > PRIMARY > > > KEY > > > (src, sender_domain, sender_name)):#012, reconnecting to DB > > > Feb 9 05:52:22 li34-197 sqlgrey: mail: failed to send: No child > > > processes#012 > > > Feb 9 05:52:22 li34-197 sqlgrey: fatal: create_from_awl_table > error > > > at /usr/sbin/sqlgrey line 176. > > > Have you searched the list archives? This looks familiar. Karl <ko...@me...> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein |
From: Winfried N. <win...@ne...> - 2010-02-09 15:23:55
|
What does your config look like? -----Original Message----- From: Craig White [mailto:cra...@az...] Sent: Tuesday, February 09, 2010 3:50 PM To: SQLgrey users mailing-list Subject: Re: [Sqlgrey-users] strange install problem Sorry... should have provided the info Mysql, yes, the user 'sqlgrey' can connect and has privileges to create the necessary tables. # mysql sqlgrey -h localhost -u sqlgrey -p Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 281 Server version: 5.1.42 Source distribution Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. perl-DBD-MySQL-4.010-1.fc11.i586 I'm still wondering why it doesn't work. Craig On Tue, 2010-02-09 at 08:56 +0100, Winfried Neessen wrote: > Hi, > > looks like DBI isn't able to create the tables. Which database are you > using?Did you install the corresponding DBD::<dbtype> module? > > Does the DB user have permissions to create tables? > > Winni > > -- > > Sent from my wireless handheld device > > Am 09.02.2010 um 06:54 schrieb Craig White <cra...@az...>: > > > sqlgrey-1.6.7-1.noarch > > > > perl-DBI-1.607-2.fc11.i586 > > > > logs say... > > Feb 9 05:52:22 li34-197 sqlgrey: 2010/02/09-05:52:22 sqlgrey (type > > Net::Server::Multiplex) starting! pid(9629) > > Feb 9 05:52:22 li34-197 sqlgrey: Binding to TCP port 2501 on host > > localhost#012 > > Feb 9 05:52:22 li34-197 sqlgrey: Setting gid to "504 504" > > Feb 9 05:52:22 li34-197 sqlgrey: Setting uid to "504" > > Feb 9 05:52:22 li34-197 sqlgrey: warning: Use of uninitialized value > > $DBI::errstr in concatenation (.) or string at /usr/sbin/sqlgrey line > > 227. > > Feb 9 05:52:22 li34-197 sqlgrey: dbaccess: warning: couldn't do > > query:#012CREATE TABLE from_awl (sender_name varchar(64) NOT NULL, > > sender_domain varchar(255) NOT NULL, src varchar(39) NOT NULL, > > first_seen timestamp NOT NULL, last_seen timestamp NOT NULL, PRIMARY > > KEY > > (src, sender_domain, sender_name)):#012, reconnecting to DB > > Feb 9 05:52:22 li34-197 sqlgrey: mail: failed to send: No child > > processes#012 > > Feb 9 05:52:22 li34-197 sqlgrey: fatal: create_from_awl_table error > > at /usr/sbin/sqlgrey line 176. > > > > and I really don't think it's anything that I did in sqlgrey.conf > > > > do I have to go to an older version? > > > > Craig > > > > > > -- > > This message has been scanned for viruses and > > dangerous content by MailScanner, and is > > believed to be clean. > > > > > > --- > > --- > > --- > > --------------------------------------------------------------------- > > 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 > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------------------------------------------------------------------------ ------ 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: Craig W. <cra...@az...> - 2010-02-09 14:50:33
|
Sorry... should have provided the info Mysql, yes, the user 'sqlgrey' can connect and has privileges to create the necessary tables. # mysql sqlgrey -h localhost -u sqlgrey -p Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 281 Server version: 5.1.42 Source distribution Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. perl-DBD-MySQL-4.010-1.fc11.i586 I'm still wondering why it doesn't work. Craig On Tue, 2010-02-09 at 08:56 +0100, Winfried Neessen wrote: > Hi, > > looks like DBI isn't able to create the tables. Which database are you > using?Did you install the corresponding DBD::<dbtype> module? > > Does the DB user have permissions to create tables? > > Winni > > -- > > Sent from my wireless handheld device > > Am 09.02.2010 um 06:54 schrieb Craig White <cra...@az...>: > > > sqlgrey-1.6.7-1.noarch > > > > perl-DBI-1.607-2.fc11.i586 > > > > logs say... > > Feb 9 05:52:22 li34-197 sqlgrey: 2010/02/09-05:52:22 sqlgrey (type > > Net::Server::Multiplex) starting! pid(9629) > > Feb 9 05:52:22 li34-197 sqlgrey: Binding to TCP port 2501 on host > > localhost#012 > > Feb 9 05:52:22 li34-197 sqlgrey: Setting gid to "504 504" > > Feb 9 05:52:22 li34-197 sqlgrey: Setting uid to "504" > > Feb 9 05:52:22 li34-197 sqlgrey: warning: Use of uninitialized value > > $DBI::errstr in concatenation (.) or string at /usr/sbin/sqlgrey line > > 227. > > Feb 9 05:52:22 li34-197 sqlgrey: dbaccess: warning: couldn't do > > query:#012CREATE TABLE from_awl (sender_name varchar(64) NOT NULL, > > sender_domain varchar(255) NOT NULL, src varchar(39) NOT NULL, > > first_seen timestamp NOT NULL, last_seen timestamp NOT NULL, PRIMARY > > KEY > > (src, sender_domain, sender_name)):#012, reconnecting to DB > > Feb 9 05:52:22 li34-197 sqlgrey: mail: failed to send: No child > > processes#012 > > Feb 9 05:52:22 li34-197 sqlgrey: fatal: create_from_awl_table error > > at /usr/sbin/sqlgrey line 176. > > > > and I really don't think it's anything that I did in sqlgrey.conf > > > > do I have to go to an older version? > > > > Craig > > > > > > -- > > This message has been scanned for viruses and > > dangerous content by MailScanner, and is > > believed to be clean. > > > > > > --- > > --- > > --- > > --------------------------------------------------------------------- > > 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 > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |
From: Winfried N. <win...@ne...> - 2010-02-09 07:56:55
|
Hi, looks like DBI isn't able to create the tables. Which database are you using?Did you install the corresponding DBD::<dbtype> module? Does the DB user have permissions to create tables? Winni -- Sent from my wireless handheld device Am 09.02.2010 um 06:54 schrieb Craig White <cra...@az...>: > sqlgrey-1.6.7-1.noarch > > perl-DBI-1.607-2.fc11.i586 > > logs say... > Feb 9 05:52:22 li34-197 sqlgrey: 2010/02/09-05:52:22 sqlgrey (type > Net::Server::Multiplex) starting! pid(9629) > Feb 9 05:52:22 li34-197 sqlgrey: Binding to TCP port 2501 on host > localhost#012 > Feb 9 05:52:22 li34-197 sqlgrey: Setting gid to "504 504" > Feb 9 05:52:22 li34-197 sqlgrey: Setting uid to "504" > Feb 9 05:52:22 li34-197 sqlgrey: warning: Use of uninitialized value > $DBI::errstr in concatenation (.) or string at /usr/sbin/sqlgrey line > 227. > Feb 9 05:52:22 li34-197 sqlgrey: dbaccess: warning: couldn't do > query:#012CREATE TABLE from_awl (sender_name varchar(64) NOT NULL, > sender_domain varchar(255) NOT NULL, src varchar(39) NOT NULL, > first_seen timestamp NOT NULL, last_seen timestamp NOT NULL, PRIMARY > KEY > (src, sender_domain, sender_name)):#012, reconnecting to DB > Feb 9 05:52:22 li34-197 sqlgrey: mail: failed to send: No child > processes#012 > Feb 9 05:52:22 li34-197 sqlgrey: fatal: create_from_awl_table error > at /usr/sbin/sqlgrey line 176. > > and I really don't think it's anything that I did in sqlgrey.conf > > do I have to go to an older version? > > Craig > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > > --- > --- > --- > --------------------------------------------------------------------- > 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: Craig W. <cra...@az...> - 2010-02-09 06:08:38
|
sqlgrey-1.6.7-1.noarch perl-DBI-1.607-2.fc11.i586 logs say... Feb 9 05:52:22 li34-197 sqlgrey: 2010/02/09-05:52:22 sqlgrey (type Net::Server::Multiplex) starting! pid(9629) Feb 9 05:52:22 li34-197 sqlgrey: Binding to TCP port 2501 on host localhost#012 Feb 9 05:52:22 li34-197 sqlgrey: Setting gid to "504 504" Feb 9 05:52:22 li34-197 sqlgrey: Setting uid to "504" Feb 9 05:52:22 li34-197 sqlgrey: warning: Use of uninitialized value $DBI::errstr in concatenation (.) or string at /usr/sbin/sqlgrey line 227. Feb 9 05:52:22 li34-197 sqlgrey: dbaccess: warning: couldn't do query:#012CREATE TABLE from_awl (sender_name varchar(64) NOT NULL, sender_domain varchar(255) NOT NULL, src varchar(39) NOT NULL, first_seen timestamp NOT NULL, last_seen timestamp NOT NULL, PRIMARY KEY (src, sender_domain, sender_name)):#012, reconnecting to DB Feb 9 05:52:22 li34-197 sqlgrey: mail: failed to send: No child processes#012 Feb 9 05:52:22 li34-197 sqlgrey: fatal: create_from_awl_table error at /usr/sbin/sqlgrey line 176. and I really don't think it's anything that I did in sqlgrey.conf do I have to go to an older version? Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |
From: LEVEAU S. <sta...@ac...> - 2010-02-04 10:40:36
|
ok thanks for your answer Stan Winfried Neessen a écrit : > Hi, > > put the email address of the use into the "optout_email" table and set > "optmethod = optout" > in your sqlgrey.conf > > > Winni > > ------------------------------------------------------------------------ > *From:* LEVEAU Stanislas [mailto:sta...@ac...] > *Sent:* Wednesday, February 03, 2010 6:13 PM > *To:* SQLgrey users mailing-list > *Subject:* [Sqlgrey-users] whitelist of user > > Hello > > Is it possible to have a whitelist of user only with sqlgrey? > User who does not want to be greylist > > Thank you in advance > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > 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 > -- *LEVEAU Stanislas** *Rectorat de Caen SIAC 168, rue Caponière B.P. 6184 14061 CAEN Cedex / Service Informatique de l'académie de Caen Département Systèmes & Réseaux/ Tel : 02.31.30.17.86 |
From: Winfried N. <win...@ne...> - 2010-02-03 17:31:41
|
Hi, put the email address of the use into the "optout_email" table and set "optmethod = optout" in your sqlgrey.conf Winni _____ From: LEVEAU Stanislas [mailto:sta...@ac...] Sent: Wednesday, February 03, 2010 6:13 PM To: SQLgrey users mailing-list Subject: [Sqlgrey-users] whitelist of user Hello Is it possible to have a whitelist of user only with sqlgrey? User who does not want to be greylist Thank you in advance |
From: LEVEAU S. <sta...@ac...> - 2010-02-03 17:13:34
|
Hello Is it possible to have a whitelist of user only with sqlgrey? User who does not want to be greylist Thank you in advance |
From: Karl O. P. <ko...@me...> - 2010-02-02 03:29:48
|
On 02/01/2010 03:10:27 PM, Kyle Lanclos wrote: > Lionel Bouton wrote: > > Isn't it a little too much work to get portability ? > 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. Autoconf does look worse than it is. I don't understand autoconf enough to cook up something from scratch but have never had any problems hacking around in projects that use autoconf and autoconf does seem to make both portability and end-user customized installation (much) easier. Karl <ko...@me...> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein |
From: Michal L. <ml...@lo...> - 2010-02-02 02:32:09
|
On 02/02/2010 10:44 AM, John Thomas wrote: > I was able to build an RPM by: > extracting the tar.gz, > changed the version in the spec file to _rc2 from -rc2, > changed the bz2 in the spec file to gz, > copied the spec file to ~/, > renamed the directory to _rc2 from -rc2, > tar.gz the directory back up copy it to rpmbuild/SOURCES, and > rpmbuild -bb sqlgrey.spec A bit too complicated ;-) Here's a cleaner way (in sqlgrey.spec): ---- 8< ---- Name: sqlgrey Version: 1.8.0_rc1 # _rc1 ... Source0: sqlgrey-1.8.0-rc1.tar.gz # original tarball ... %prep %setup -n sqlgrey-1.8.0-rc1 %build make ---- 8< ---- The key line is "%setup -n sqlgrey-1.8.0-rc1" which advises the rpm builder that the unpacked directory is sqlgrey-1.8.0-rc1 instead of sqlgrey-1.8.0_rc1 as would have been the default derived from %{version}. HTH, Michal |
From: Kyle L. <la...@uc...> - 2010-02-02 01:24:39
|
I'm testing the behavior of sqlgrey when the database is offline. The first problem is rare, and not likely to be triggered. If you start the database backend, start sqlgrey, and then kill the backend without any messages having hit sqlgrey, the daemon will die a nasty death in sub update_dbnow. There is a reference to $DBI::errstr (line 382) that, in these circumstances, is an uninitialized reference. The resulting error looks like: Use of uninitialized value in concatenation (.) or string at ./sqlgrey line 382. setconfig error One might perhaps consider this a bug in DBI, but it should be easy enough to work around. The second problem is a bit more subtle. In sub smtpd_access_policy, when the database is first accessed by a call to sub is_in_domain_awl, the return value is 1-- meaning the check succeeded. In reality, the check did not occur, because the database was offline; yet, what winds up in the headers is 'domain auto-whitelisted by...', which is misleading. This is clearly by design, and the desired behavior is occurring-- the message is accepted for delivery by postfix. It would be much more informative if there was first a check to see if the database was online, and if it was not available, to instead prepend a header saying something like 'database offline, message not greylisted'. I'm not perl-savvy, so I'm not immediately sure how best to go about this last one. If it was Python, I'd be raising an exception... --Kyle |
From: Michal L. <ml...@lo...> - 2010-02-02 00:02:30
|
Hi Kyle, whether or not your patches are approved at the end please make sure 'make dist' works with them and creates a usable distribution tarball. At the moment it checks out a tagged revision from GIT and packs that up. However I don't think we should have the autoconf-generated files in GIT so you may want to add those to the tarball manually. Let me know should you need any help with it. That said you should consider getting the git repo clone and work on sqlgrey "the git way" instead of manually creating patches ;-) Michal On 02/02/2010 12:52 PM, Kyle Lanclos wrote: > Here's a newer version of configure.ac that does sensible things when > one of the required programs is not found. > > --Kyle > > > > ------------------------------------------------------------------------------ > 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 23:53:02
|
Here's a newer version of configure.ac that does sensible things when one of the required programs is not found. --Kyle |
From: John T. <gma...@jt...> - 2010-02-01 21:45:00
|
>> I have reverted the infamous 'sed -i' Makefile change (sorry for that) >> and released sqlgrey-1.8.0-rc2: > 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 figured out dashes are not allowed in the version number, at least according to this: http://docs.fedoraproject.org/drafts/rpm-guide-en/ch09s03.html I was able to build an RPM by: extracting the tar.gz, changed the version in the spec file to _rc2 from -rc2, changed the bz2 in the spec file to gz, copied the spec file to ~/, renamed the directory to _rc2 from -rc2, tar.gz the directory back up copy it to rpmbuild/SOURCES, and rpmbuild -bb sqlgrey.spec -- Sincerely, John Thomas |