sqlgrey-users — Users of SQLgrey

Re: [Sqlgrey-users] Pre Load

[Dan F. <da...@ha...>]

I agree with Lionel.
Its best letting sqlgrey do all this since you really cant tell who is 
valid senders if you dont temporally reject first, and then sees who 
comes back. (which is what greylisting does)

If you are worried that delaying all mail for 5 minutes at the same day 
you enable sqlgrey, consider using the "discrimination" feature from 
1.7.4+. That will let you, via regular expressions, select what to 
greylist and what to just let through . Good way of slowly introducing 
greylisting by making the discrimination rules more and more restrictive.


Also i got this wild idea of the top of my head (note: my wild idea's 
arent always recommended :)):

You could let sqlgrey learn over a month or two. Havent tried excactly 
what you need, but i imagine something like this would work:

By using version 1.7.4+ you can set the "reject_code". By setting
reject_code = dunno
sqlgrey performs as usual, except nothing gets rejected.

Then by changing  "reconnect_delay" to something really low (dont know 
if you kan use "0" here) and
"max_connect_age" to something really high, then everyone who sends more 
than 1 mail withing the time specified by "max_connect_age", will be 
treated as a valid sender and added to "from_awl".

after a while, simply set reject_code, max_connect_age and 
reconnect_delay back to default.

A word of warning.
This will result in a large "connect" table. Also, you will likely will 
get a stack of spammers added to your from_awl as well whom will have to 
expire.

As i said, its a wild idea ;)

- Dan Faerch


Paul Barbeau wrote:
> I was not using grey listing before at all so this is first time data.
> What I am pulling out of the logs is from the postfix lines and they are
> sender, recipient, server what normally would have been passed to the
> server if I had been using it.  I know they will go into the "connect"
> first however based on volume I can move them over as I know what should
> have been added.
>
> Hope this clears up what i meant.
>
> Paul
>
> -----Original Message-----
> From: sql...@li...
> [mailto:sql...@li...] On Behalf Of Kasey
> Speakman
> Sent: Friday, January 19, 2007 11:04 AM
> To: SQLgrey users mailing-list
> Subject: Re: [Sqlgrey-users] Pre Load
>
> If you're using the same MySQL database as before, it should already  
> be there.  The logs only record what is inserted into the database,  
> so losing the logs will not affect your domain_awl, as long as the  
> database still exists.  If you're setting up a new MySQL server too,  
> then just mysql-dump the old database and restore it into the new  
> server.
>
> On Jan 19, 2007, at 9:43 AM, Paul Barbeau wrote:
>
>   
>> I am about to start up SQLGREY and I would like to "pre" load the
>> "domain_awl" and "from_awl" from my old postfix logs and usage.  I  
>> know
>> I can and server/ip to my whitelist files however I would rather  
>> them go
>> into the AWL so they can expire if need be.  Other then just adding to
>> the database is there a better way to do this?  Some how submit  
>> into the
>> daemon?
>>
>> Paul
>>
>>
>> ----------------------------------------------------------------------
>>     
>
>   
>> ---
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to  
>> share your
>> opinions on IT & business topics through brief surveys - and earn cash
>> http://www.techsay.com/default.php? 
>> page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> 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.
>>
>>     
>
>
> ------------------------------------------------------------------------
> -
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE
> V
> _______________________________________________
> Sqlgrey-users mailing list
> Sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Sqlgrey-users mailing list
> Sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users
>
>   

Re: [Sqlgrey-users] Pre Load

[Lionel B. <lio...@bo...>]

Paul Barbeau wrote the following on 19.01.2007 17:12 :
> I was not using grey listing before at all so this is first time data.
> What I am pulling out of the logs is from the postfix lines and they are
> sender, recipient, server what normally would have been passed to the
> server if I had been using it.  I know they will go into the "connect"
> first however based on volume I can move them over as I know what should
> have been added.
>
> Hope this clears up what i meant.
>   

You'll have to use your favorite language to script it. By greylisting's
design there's no sure way of determining the good from the bad reading
postfix logs, so you'll have to code your own heuristics adapted to your
own case. Inserting the lines you want in the good table is the easiest
part, it's only a matter of connecting to the database and doing
INSERTs. You can even prepare the INSERTs in a file and feed it to psql
or mysql clients to avoid coding database accesses in your script.

In fact, if I were you I wouldn't even bother doing so. Greylisting only
adds a small delay that is often not noticeable, even without
auto-whitelists. The delay usually is around 20 minutes, so unless you
expect a mail at a very precise moment or the sender just called to
check if the email got through, nobody is even aware that greylisting
took place.

Even people with huge mailservers didn't have any problem letting
SQLgrey handle the task automatically, why should you have any?

Lionel.

Re: [Sqlgrey-users] Pre Load

[Paul B. <pa...@hy...>]

I was not using grey listing before at all so this is first time data.
What I am pulling out of the logs is from the postfix lines and they are
sender, recipient, server what normally would have been passed to the
server if I had been using it.  I know they will go into the "connect"
first however based on volume I can move them over as I know what should
have been added.

Hope this clears up what i meant.

Paul

-----Original Message-----
From: sql...@li...
[mailto:sql...@li...] On Behalf Of Kasey
Speakman
Sent: Friday, January 19, 2007 11:04 AM
To: SQLgrey users mailing-list
Subject: Re: [Sqlgrey-users] Pre Load

If you're using the same MySQL database as before, it should already =20
be there.  The logs only record what is inserted into the database, =20
so losing the logs will not affect your domain_awl, as long as the =20
database still exists.  If you're setting up a new MySQL server too, =20
then just mysql-dump the old database and restore it into the new =20
server.

On Jan 19, 2007, at 9:43 AM, Paul Barbeau wrote:

> I am about to start up SQLGREY and I would like to "pre" load the
> "domain_awl" and "from_awl" from my old postfix logs and usage.  I =20
> know
> I can and server/ip to my whitelist files however I would rather =20
> them go
> into the AWL so they can expire if need be.  Other then just adding to
> the database is there a better way to do this?  Some how submit =20
> into the
> daemon?
>
> Paul
>
>
> ----------------------------------------------------------------------

> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to =20
> share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?=20
> page=3Djoin.php&p=3Dsourceforge&CID=3DDEVDEV
> _______________________________________________
> Sqlgrey-users mailing list
> Sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users
>
> --=20
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>


------------------------------------------------------------------------
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDE
V
_______________________________________________
Sqlgrey-users mailing list
Sql...@li...
https://lists.sourceforge.net/lists/listinfo/sqlgrey-users

Re: [Sqlgrey-users] Pre Load

[Kasey S. <ksp...@as...>]

If you're using the same MySQL database as before, it should already  
be there.  The logs only record what is inserted into the database,  
so losing the logs will not affect your domain_awl, as long as the  
database still exists.  If you're setting up a new MySQL server too,  
then just mysql-dump the old database and restore it into the new  
server.

On Jan 19, 2007, at 9:43 AM, Paul Barbeau wrote:

> I am about to start up SQLGREY and I would like to "pre" load the
> "domain_awl" and "from_awl" from my old postfix logs and usage.  I  
> know
> I can and server/ip to my whitelist files however I would rather  
> them go
> into the AWL so they can expire if need be.  Other then just adding to
> the database is there a better way to do this?  Some how submit  
> into the
> daemon?
>
> Paul
>
>
> ---------------------------------------------------------------------- 
> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to  
> share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php? 
> page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> 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.
>

[Sqlgrey-users] Pre Load

[Paul B. <pa...@hy...>]

I am about to start up SQLGREY and I would like to "pre" load the
"domain_awl" and "from_awl" from my old postfix logs and usage.  I know
I can and server/ip to my whitelist files however I would rather them go
into the AWL so they can expire if need be.  Other then just adding to
the database is there a better way to do this?  Some how submit into the
daemon?=20

Paul

Re: [Sqlgrey-users] Selectively Check Mail for Certain Users?

[Richard W. <ri...@ev...>]

Hi

=20

Thanks for the information about where to find the README.OPTINOUT as I
hadn=92t been able to find it.  I=92ve now made the appropriate entries =
in the
optout_email table and added =91optmethod =3D optout=92 to sqlgrey.conf =
so I hope
this gets the right results.

=20

Regards

=20

Richard Williams.

=20

****************************************************
Richard Williams
email: HYPERLINK
"mailto:ri...@ev..."ri...@ev...=20
mobile: 07981 734697
****************************************************=20
The contents of this email message and any attachments are confidential =
and
are intended solely for addressee. The information may also be legally
privileged. This transmission is sent in trust, for the sole purpose of
delivery to the intended recipient. If you have received this =
transmission
in error, any use, reproduction or dissemination of this transmission is
strictly prohibited. If you are not the intended recipient, please
immediately notify the sender by reply email or at +44(0)7981 734697 and
delete this message and its attachments, if any.

=20


--=20
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.16.9/623 - Release Date: =
11/01/2007
15:33
=20

Re: [Sqlgrey-users] Selectively Check Mail for Certain Users?

[Gonzalo F. <eat...@gm...>]

Hi Richard,

well... as far as I know, if you include those mails in the whitelist,
they will go straight away into the mailboxes without a delay, otherwise
they will have to wait 5 minutes.
IIf you want a hassel free administration. I recommend you to get: "sgwi"

http://www.vanheusden.com/sgwi/

Straight forward installation and you can speed up the greylisting
process introducing, previously, all those emails/domains you consider safe.

Thanks

Gonzalo

Richard Williams wrote:
> Hi
>
>  
>
> I have a situation where certain email recipients want to have the advantage
> of their incoming email being subject to greylisting but other email
> recipients want all their email to pass straight through without delay.
>
>  
>
> Is it possible to do this with sqlgrey?
>
>  
>
> Regards
>
>  
>
> Richard Williams
>
>  
>
> ****************************************************
> Richard Williams
> email: HYPERLINK
> "mailto:ri...@ev..."ri...@ev... 
> mobile: 07981 734697
> **************************************************** 
> The contents of this email message and any attachments are confidential and
> are intended solely for addressee. The information may also be legally
> privileged. This transmission is sent in trust, for the sole purpose of
> delivery to the intended recipient. If you have received this transmission
> in error, any use, reproduction or dissemination of this transmission is
> strictly prohibited. If you are not the intended recipient, please
> immediately notify the sender by reply email or at +44(0)7981 734697 and
> delete this message and its attachments, if any.
>
>  
>
>
>   
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> ------------------------------------------------------------------------
>
> _______________________________________________
> Sqlgrey-users mailing list
> Sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users
>   

Re: [Sqlgrey-users] Selectively Check Mail for Certain Users?

[Winfried N. <win...@ne...>]

Hi Richard,

* Richard Williams <ri...@ev...>:

> I have a situation where certain email recipients want to have the
> advantage of their incoming email being subject to greylisting but
> other email recipients want all their email to pass straight
> through without delay.
>
This is possible with SQLgrey. It's the Opt-In/Opt-Out feature of
SQLgrey. Have a look at README.OPTINOUT in the sqlgrey sources
directory.

Winfried

--=20
Winfried Neessen                           Phone:       +49 221 2612601
neessen.net - Webhosting                   Fax:         +49 221 2612602
Peter-Bauer-Str. 9                         Email:  win...@ne...
50823 Cologne                              PGP/GPG Key-ID:   0xda5cd8ef

[Sqlgrey-users] Selectively Check Mail for Certain Users?

[Richard W. <ri...@ev...>]

Hi

=20

I have a situation where certain email recipients want to have the =
advantage
of their incoming email being subject to greylisting but other email
recipients want all their email to pass straight through without delay.

=20

Is it possible to do this with sqlgrey?

=20

Regards

=20

Richard Williams

=20

****************************************************
Richard Williams
email: HYPERLINK
"mailto:ri...@ev..."ri...@ev...=20
mobile: 07981 734697
****************************************************=20
The contents of this email message and any attachments are confidential =
and
are intended solely for addressee. The information may also be legally
privileged. This transmission is sent in trust, for the sole purpose of
delivery to the intended recipient. If you have received this =
transmission
in error, any use, reproduction or dissemination of this transmission is
strictly prohibited. If you are not the intended recipient, please
immediately notify the sender by reply email or at +44(0)7981 734697 and
delete this message and its attachments, if any.

=20


--=20
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.16.9/623 - Release Date: =
11/01/2007
15:33
=20

Re: [Sqlgrey-users] Sqlgrey dies while creating mysql tables

[Juraj V. <ju...@eq...>]

Hello,

I am sending following message again, sorry if you already got it. It did 
arrive back to me, but in web archive of this mailinglist isn't visible.

---------

 perl -MDBI -le 'my 
$db=DBI->connect("DBI:mysql:database=sqlgrey;host=localhost","myuser","mypass",undef) 
or die "Error:$DBI::errstr".$db->disconnect()'

 passed without failure and output nothing. Then I tried to create the table, 
with very interesting result:

perl -MDBI -le 'my 
$db=DBI->connect("DBI:mysql:database=sqlgrey;host=localhost","u_sqlgrey","greysql",undef); 
$db->do("CREATE 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))");$db->disconnect();'
DBD::mysql::db do failed: Specified key was too long; max key length is 1000 
bytes at -e line 1.

According to http://bugs.mysql.com/bug.php?id=4541 , it seems the culprit is 
that I have utf8 database....

Juraj

On Wednesday 10 January 2007 20:57, Winfried Neessen wrote:
(snip)
> `---
> please open a shell an execute this line an send us what error that is
> returned by it:
>
> ,---
>
> | perl -MDBI -le 'my
> | $db=DBI->connect("DBI:mysql:database=sqlgrey;host=localhost","youruser","
> |yourpass",undef) or die "Error: $DBI::errstr"$db->disconnect()'
>
> `---
>
> Regards
> Winfried

Re: [Sqlgrey-users] Sqlgrey dies while creating mysql tables

[Juan P. B. <jp...@gr...>]

MySql 4.0.24

I have turned log and log-error to try to catch any mysql complaint.


> -----Original Message-----
> From: sql...@li...=20
> [mailto:sql...@li...] On=20
> Behalf Of Gonzalo Fernandez
> Sent: Thursday, January 11, 2007 21:14
> To: SQLgrey users mailing-list
> Subject: Re: [Sqlgrey-users] Sqlgrey dies while creating mysql tables
>=20
>=20
> what is the MYSQL Version?
>=20
> some critical changes in the latests version impact in the table
> creation an data manipulation.
> It looks like the connection is ok, but NOT the table=20
> creation. Have you
> checked any mysql error in /var/log?
>=20
> Juan Pablo Bagnon wrote:
> > Im really a newbbie with MySql and i get LOADS of these:
> >
> > SQLgrey recovered DB:	SQLgrey established connection to:
> > DBI:mysql:database=3DSqlgrey;host=3Dlocalhost
> > SQLgrey database error:	SQLgrey encountered an SQL=20
> error and triggered a
> > reconnection to: DBI:mysql:database=3DSqlgrey;host=3Dlocalhost
> >
> > Cluopd it be the same problem?
> > How can i do it with mysql?
> > I got this:
> >
> > character set latin1=20
> >
> > character sets latin1 big5 czech euc_kr gb2312 gbk=20
> > latin1_de sjis tis620 ujis dec8 dos german1 hp8 koi8_ru=20
> > latin2 swe7 usa7 cp1251 danish hebrew win1251 estonia hungarian=20
> > koi8_ukr win1251ukr greek win1250 croat cp1257 latin5=20
> >
> >
> >  =20
> >> -----Original Message-----
> >> From: sql...@li...=20
> >> [mailto:sql...@li...] On=20
> >> Behalf Of Dan Faerch
> >> Sent: Thursday, January 11, 2007 17:03
> >> To: SQLgrey users mailing-list
> >> Subject: Re: [Sqlgrey-users] Sqlgrey dies while creating=20
> mysql tables
> >>
> >>
> >> Ahh yes...
> >>
> >> Lionel helped someone not long ago who had problems, and it=20
> >> turned out=20
> >> to be a UNICODE problem. Here's a quote from the mailing list:
> >>
> >> "Hum, did you try to use a database with ASCII instead of UNICODE?
> >> SQLgrey doesn't try to speak utf-8 with the database but only=20
> >> pure ASCII."
> >>
> >> Andrew wrote a helpfull mail on how to migrate to ASCII.
> >>  From the maillinglist archives:
> >> http://sourceforge.net/mailarchive/message.php?msg_id=3D37802061
> >>
> >>
> >> On a side note. Since more ppl will have this problem, im=20
> thinking we=20
> >> should either support other encodings or at least warn on=20
> >> execution of=20
> >> sqlgrey.
> >>
> >> Anyone got some thoughts about either of theese?
> >> - How hard is it to support all encodings
> >> - How do we detect if database is ASCII
> >>
> >> If we get a real simple solution, ill try and implement it=20
> very soon.
> >>
> >> - Dan
> >>
> >>
> >> Juraj Variny wrote:
> >>    =20
> >>> Hello,
> >>>
> >>>  perl -MDBI -le 'my=20
> >>>      =20
> >> =
$db=3DDBI->connect("DBI:mysql:database=3Dsqlgrey;host=3Dlocalhost","
> >> myuser","mypass",undef) or die=20
> "Error:$DBI::errstr".$db->disconnect()'
> >>    =20
> >>>  passed without failure and output nothing. Then I tried to=20
> >>>      =20
> >> create the table, with very interesting result:
> >>    =20
> >>> perl -MDBI -le 'my=20
> >>>      =20
> >> =
$db=3DDBI->connect("DBI:mysql:database=3Dsqlgrey;host=3Dlocalhost","
> >> u_sqlgrey","greysql",undef); $db->do("CREATE TABLE from_awl=20
> >> (sender_name varchar(64) NOT NULL, sender_domain varchar(255)=20
> >> NOT NULL, src varchar(39) NOT NULL, first_seen timestamp NOT=20
> >> NULL, last_seen timestamp NOT NULL, PRIMARY KEY (src,=20
> >> sender_domain, sender_name))");$db->disconnect();'
> >>    =20
> >>> DBD::mysql::db do failed: Specified key was too long; max=20
> >>>      =20
> >> key length is 1000 bytes at -e line 1.
> >>    =20
> >>> According to http://bugs.mysql.com/bug.php?id=3D4541 , it=20
> >>>      =20
> >> seems the culprit is that I have utf8 database....
> >>    =20
> >>> Juraj
> >>>
> >>> On Wednesday 10 January 2007 20:57, Winfried Neessen wrote:
> >>> (snip)
> >>>  =20
> >>>      =20
> >>>> `---
> >>>> please open a shell an execute this line an send us what=20
> >>>>        =20
> >> error that is
> >>    =20
> >>>> returned by it:
> >>>>
> >>>> ,---
> >>>>
> >>>> | perl -MDBI -le 'my
> >>>> |=20
> >>>>        =20
> >> =
$db=3DDBI->connect("DBI:mysql:database=3Dsqlgrey;host=3Dlocalhost","
> >> youruser","
> >>    =20
> >>>> |yourpass",undef) or die "Error: $DBI::errstr"$db->disconnect()'
> >>>>
> >>>> `---
> >>>>
> >>>> Regards
> >>>> Winfried
> >>>>    =20
> >>>>        =20
> >>>      =20
> >> --------------------------------------------------------------
> >> -----------
> >>    =20
> >>> Take Surveys. Earn Cash. Influence the Future of IT
> >>> Join SourceForge.net's Techsay panel and you'll get the=20
> >>>      =20
> >> chance to share your
> >>    =20
> >>> opinions on IT & business topics through brief surveys -=20
> >>>      =20
> >> and earn cash
> >>    =20
> >> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge
> >>    =20
> > &CID=3DDEVDEV
> >  =20
> >> _______________________________________________
> >> Sqlgrey-users mailing list
> >> Sql...@li...
> >> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users
> >>
> >>  =20
> >>    =20
> >
> >
> >=20
> --------------------------------------------------------------
> -----------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the=20
> chance to share your
> > opinions on IT & business topics through brief surveys -=20
> and earn cash
> >=20
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge
&CID=3DDEVDEV
> _______________________________________________
> Sqlgrey-users mailing list
> Sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users
>
>
>
> =
-------------------------------------------------------------------------=

> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to =
share
your
> opinions on IT & business topics through brief surveys - and earn cash
> =
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> Sqlgrey-users mailing list
> Sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users
>
>  =20


-------------------------------------------------------------------------=

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share =
your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
_______________________________________________
Sqlgrey-users mailing list
Sql...@li...
https://lists.sourceforge.net/lists/listinfo/sqlgrey-users

Re: [Sqlgrey-users] Sqlgrey dies while creating mysql tables

[Gonzalo F. <eat...@gm...>]

what is the MYSQL Version?

some critical changes in the latests version impact in the table
creation an data manipulation.
It looks like the connection is ok, but NOT the table creation. Have you
checked any mysql error in /var/log?

Juan Pablo Bagnon wrote:
> Im really a newbbie with MySql and i get LOADS of these:
>
> SQLgrey recovered DB:	SQLgrey established connection to:
> DBI:mysql:database=Sqlgrey;host=localhost
> SQLgrey database error:	SQLgrey encountered an SQL error and triggered a
> reconnection to: DBI:mysql:database=Sqlgrey;host=localhost
>
> Cluopd it be the same problem?
> How can i do it with mysql?
> I got this:
>
> character set latin1 
>
> character sets latin1 big5 czech euc_kr gb2312 gbk 
> latin1_de sjis tis620 ujis dec8 dos german1 hp8 koi8_ru 
> latin2 swe7 usa7 cp1251 danish hebrew win1251 estonia hungarian 
> koi8_ukr win1251ukr greek win1250 croat cp1257 latin5 
>
>
>   
>> -----Original Message-----
>> From: sql...@li... 
>> [mailto:sql...@li...] On 
>> Behalf Of Dan Faerch
>> Sent: Thursday, January 11, 2007 17:03
>> To: SQLgrey users mailing-list
>> Subject: Re: [Sqlgrey-users] Sqlgrey dies while creating mysql tables
>>
>>
>> Ahh yes...
>>
>> Lionel helped someone not long ago who had problems, and it 
>> turned out 
>> to be a UNICODE problem. Here's a quote from the mailing list:
>>
>> "Hum, did you try to use a database with ASCII instead of UNICODE?
>> SQLgrey doesn't try to speak utf-8 with the database but only 
>> pure ASCII."
>>
>> Andrew wrote a helpfull mail on how to migrate to ASCII.
>>  From the maillinglist archives:
>> http://sourceforge.net/mailarchive/message.php?msg_id=37802061
>>
>>
>> On a side note. Since more ppl will have this problem, im thinking we 
>> should either support other encodings or at least warn on 
>> execution of 
>> sqlgrey.
>>
>> Anyone got some thoughts about either of theese?
>> - How hard is it to support all encodings
>> - How do we detect if database is ASCII
>>
>> If we get a real simple solution, ill try and implement it very soon.
>>
>> - Dan
>>
>>
>> Juraj Variny wrote:
>>     
>>> Hello,
>>>
>>>  perl -MDBI -le 'my 
>>>       
>> $db=DBI->connect("DBI:mysql:database=sqlgrey;host=localhost","
>> myuser","mypass",undef) or die "Error:$DBI::errstr".$db->disconnect()'
>>     
>>>  passed without failure and output nothing. Then I tried to 
>>>       
>> create the table, with very interesting result:
>>     
>>> perl -MDBI -le 'my 
>>>       
>> $db=DBI->connect("DBI:mysql:database=sqlgrey;host=localhost","
>> u_sqlgrey","greysql",undef); $db->do("CREATE 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))");$db->disconnect();'
>>     
>>> DBD::mysql::db do failed: Specified key was too long; max 
>>>       
>> key length is 1000 bytes at -e line 1.
>>     
>>> According to http://bugs.mysql.com/bug.php?id=4541 , it 
>>>       
>> seems the culprit is that I have utf8 database....
>>     
>>> Juraj
>>>
>>> On Wednesday 10 January 2007 20:57, Winfried Neessen wrote:
>>> (snip)
>>>   
>>>       
>>>> `---
>>>> please open a shell an execute this line an send us what 
>>>>         
>> error that is
>>     
>>>> returned by it:
>>>>
>>>> ,---
>>>>
>>>> | perl -MDBI -le 'my
>>>> | 
>>>>         
>> $db=DBI->connect("DBI:mysql:database=sqlgrey;host=localhost","
>> youruser","
>>     
>>>> |yourpass",undef) or die "Error: $DBI::errstr"$db->disconnect()'
>>>>
>>>> `---
>>>>
>>>> Regards
>>>> Winfried
>>>>     
>>>>         
>>>       
>> --------------------------------------------------------------
>> -----------
>>     
>>> Take Surveys. Earn Cash. Influence the Future of IT
>>> Join SourceForge.net's Techsay panel and you'll get the 
>>>       
>> chance to share your
>>     
>>> opinions on IT & business topics through brief surveys - 
>>>       
>> and earn cash
>>     
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge
>>     
> &CID=DEVDEV
>   
>> _______________________________________________
>> Sqlgrey-users mailing list
>> Sql...@li...
>> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users
>>
>>   
>>     
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Sqlgrey-users mailing list
> Sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Sqlgrey-users mailing list
> Sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users
>
>   

Re: [Sqlgrey-users] Sqlgrey dies while creating mysql tables

[Juan P. B. <jp...@gr...>]

Im really a newbbie with MySql and i get LOADS of these:

SQLgrey recovered DB:	SQLgrey established connection to:
DBI:mysql:database=3DSqlgrey;host=3Dlocalhost
SQLgrey database error:	SQLgrey encountered an SQL error and triggered a
reconnection to: DBI:mysql:database=3DSqlgrey;host=3Dlocalhost

Cluopd it be the same problem?
How can i do it with mysql?
I got this:

character set latin1=20

character sets latin1 big5 czech euc_kr gb2312 gbk=20
latin1_de sjis tis620 ujis dec8 dos german1 hp8 koi8_ru=20
latin2 swe7 usa7 cp1251 danish hebrew win1251 estonia hungarian=20
koi8_ukr win1251ukr greek win1250 croat cp1257 latin5=20


> -----Original Message-----
> From: sql...@li...=20
> [mailto:sql...@li...] On=20
> Behalf Of Dan Faerch
> Sent: Thursday, January 11, 2007 17:03
> To: SQLgrey users mailing-list
> Subject: Re: [Sqlgrey-users] Sqlgrey dies while creating mysql tables
>=20
>=20
> Ahh yes...
>=20
> Lionel helped someone not long ago who had problems, and it=20
> turned out=20
> to be a UNICODE problem. Here's a quote from the mailing list:
>=20
> "Hum, did you try to use a database with ASCII instead of UNICODE?
> SQLgrey doesn't try to speak utf-8 with the database but only=20
> pure ASCII."
>=20
> Andrew wrote a helpfull mail on how to migrate to ASCII.
>  From the maillinglist archives:
> http://sourceforge.net/mailarchive/message.php?msg_id=3D37802061
>=20
>=20
> On a side note. Since more ppl will have this problem, im thinking we=20
> should either support other encodings or at least warn on=20
> execution of=20
> sqlgrey.
>=20
> Anyone got some thoughts about either of theese?
> - How hard is it to support all encodings
> - How do we detect if database is ASCII
>=20
> If we get a real simple solution, ill try and implement it very soon.
>=20
> - Dan
>=20
>=20
> Juraj Variny wrote:
> > Hello,
> >
> >  perl -MDBI -le 'my=20
> $db=3DDBI->connect("DBI:mysql:database=3Dsqlgrey;host=3Dlocalhost","
> myuser","mypass",undef) or die "Error:$DBI::errstr".$db->disconnect()'
> >
> >  passed without failure and output nothing. Then I tried to=20
> create the table, with very interesting result:
> >
> > perl -MDBI -le 'my=20
> $db=3DDBI->connect("DBI:mysql:database=3Dsqlgrey;host=3Dlocalhost","
> u_sqlgrey","greysql",undef); $db->do("CREATE TABLE from_awl=20
> (sender_name varchar(64) NOT NULL, sender_domain varchar(255)=20
> NOT NULL, src varchar(39) NOT NULL, first_seen timestamp NOT=20
> NULL, last_seen timestamp NOT NULL, PRIMARY KEY (src,=20
> sender_domain, sender_name))");$db->disconnect();'
> > DBD::mysql::db do failed: Specified key was too long; max=20
> key length is 1000 bytes at -e line 1.
> >
> > According to http://bugs.mysql.com/bug.php?id=3D4541 , it=20
> seems the culprit is that I have utf8 database....
> >
> > Juraj
> >
> > On Wednesday 10 January 2007 20:57, Winfried Neessen wrote:
> > (snip)
> >  =20
> >> `---
> >> please open a shell an execute this line an send us what=20
> error that is
> >> returned by it:
> >>
> >> ,---
> >>
> >> | perl -MDBI -le 'my
> >> |=20
> $db=3DDBI->connect("DBI:mysql:database=3Dsqlgrey;host=3Dlocalhost","
> youruser","
> >> |yourpass",undef) or die "Error: $DBI::errstr"$db->disconnect()'
> >>
> >> `---
> >>
> >> Regards
> >> Winfried
> >>    =20
> >
> >=20
> --------------------------------------------------------------
> -----------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the=20
> chance to share your
> > opinions on IT & business topics through brief surveys -=20
> and earn cash
> >=20
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge
&CID=3DDEVDEV
> _______________________________________________
> Sqlgrey-users mailing list
> Sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users
>
>  =20


-------------------------------------------------------------------------=

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share =
your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
_______________________________________________
Sqlgrey-users mailing list
Sql...@li...
https://lists.sourceforge.net/lists/listinfo/sqlgrey-users

Re: [Sqlgrey-users] Sqlgrey dies while creating mysql tables

[Dan F. <da...@ha...>]

Ahh yes...

Lionel helped someone not long ago who had problems, and it turned out 
to be a UNICODE problem. Here's a quote from the mailing list:

"Hum, did you try to use a database with ASCII instead of UNICODE?
SQLgrey doesn't try to speak utf-8 with the database but only pure ASCII."

Andrew wrote a helpfull mail on how to migrate to ASCII.
 From the maillinglist archives:
http://sourceforge.net/mailarchive/message.php?msg_id=37802061


On a side note. Since more ppl will have this problem, im thinking we 
should either support other encodings or at least warn on execution of 
sqlgrey.

Anyone got some thoughts about either of theese?
- How hard is it to support all encodings
- How do we detect if database is ASCII

If we get a real simple solution, ill try and implement it very soon.

- Dan


Juraj Variny wrote:
> Hello,
>
>  perl -MDBI -le 'my $db=DBI->connect("DBI:mysql:database=sqlgrey;host=localhost","myuser","mypass",undef) or die "Error:$DBI::errstr".$db->disconnect()'
>
>  passed without failure and output nothing. Then I tried to create the table, with very interesting result:
>
> perl -MDBI -le 'my $db=DBI->connect("DBI:mysql:database=sqlgrey;host=localhost","u_sqlgrey","greysql",undef); $db->do("CREATE 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))");$db->disconnect();'
> DBD::mysql::db do failed: Specified key was too long; max key length is 1000 bytes at -e line 1.
>
> According to http://bugs.mysql.com/bug.php?id=4541 , it seems the culprit is that I have utf8 database....
>
> Juraj
>
> On Wednesday 10 January 2007 20:57, Winfried Neessen wrote:
> (snip)
>   
>> `---
>> please open a shell an execute this line an send us what error that is
>> returned by it:
>>
>> ,---
>>
>> | perl -MDBI -le 'my
>> | $db=DBI->connect("DBI:mysql:database=sqlgrey;host=localhost","youruser","
>> |yourpass",undef) or die "Error: $DBI::errstr"$db->disconnect()'
>>
>> `---
>>
>> Regards
>> Winfried
>>     
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Sqlgrey-users mailing list
> Sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users
>
>   

Re: [Sqlgrey-users] Sqlgrey dies while creating mysql tables

[Juraj V. <ju...@eq...>]

Hello,

 perl -MDBI -le 'my $db=DBI->connect("DBI:mysql:database=sqlgrey;host=localhost","myuser","mypass",undef) or die "Error:$DBI::errstr".$db->disconnect()'

 passed without failure and output nothing. Then I tried to create the table, with very interesting result:

perl -MDBI -le 'my $db=DBI->connect("DBI:mysql:database=sqlgrey;host=localhost","u_sqlgrey","greysql",undef); $db->do("CREATE 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))");$db->disconnect();'
DBD::mysql::db do failed: Specified key was too long; max key length is 1000 bytes at -e line 1.

According to http://bugs.mysql.com/bug.php?id=4541 , it seems the culprit is that I have utf8 database....

Juraj

On Wednesday 10 January 2007 20:57, Winfried Neessen wrote:
(snip)
> `---
> please open a shell an execute this line an send us what error that is
> returned by it:
>
> ,---
>
> | perl -MDBI -le 'my
> | $db=DBI->connect("DBI:mysql:database=sqlgrey;host=localhost","youruser","
> |yourpass",undef) or die "Error: $DBI::errstr"$db->disconnect()'
>
> `---
>
> Regards
> Winfried

Re: [Sqlgrey-users] Sqlgrey dies while creating mysql tables

[Winfried N. <win...@ne...>]

Hi Dan,

* Dan Faerch <da...@ha...>:

>> That's not true. sqlgrey uses Perl's DBI mechanism, which is working
>> fine with connecting via socket. In fact it's working exactly the same
>>
> Really? Then i stand corrected..But havent you then explicitly defined
> the socket file and not an IP? or at least 127.0.0.1 as the IP?
>
Nop ;-) I defined these db specific parameters:
,---[ /etc/sqlgrey/sqlgrey.conf ]
| db_type =3D mysql
| db_name =3D sqlgrey
| db_host =3D localhost
| db_user =3D xxxxx
| db_pass =3D yyyyy
`---

But if I wouldn't have defined db_host in /etc/sqlgrey/sqlgrey.conf
it would use localhost by default as defined in sqlgres:
,---
| $dflt{db_host}            =3D 'localhost';
`---

Winfried

--=20
Winfried Neessen                           Phone:       +49 221 2612601
neessen.net - Webhosting                   Fax:         +49 221 2612602
Peter-Bauer-Str. 9                         Email:  win...@ne...
50823 Cologne                              PGP/GPG Key-ID:   0xda5cd8ef

Re: [Sqlgrey-users] Sqlgrey dies while creating mysql tables

[Dan F. <da...@ha...>]

Winfried Neessen wrote:
> That's not true. sqlgrey uses Perl's DBI mechanism, which is working
> fine with connecting via socket. In fact it's working exactly the same
>
>   
Really? Then i stand corrected..But havent you then explicitly defined 
the socket file and not an IP? or at least 127.0.0.1 as the IP?

- Dan

Re: [Sqlgrey-users] Sqlgrey dies while creating mysql tables

[Winfried N. <win...@ne...>]

Hi,

* Dan Faerch <da...@ha...>:

> If skip-networking is enabled, that would definently explain it, as
> sqlgrey doesn't connect through the socket file=20
> "/var/run/mysqld/mysqld.sock" like eg. php does pr. default.
>
That's not true. sqlgrey uses Perl's DBI mechanism, which is working
fine with connecting via socket. In fact it's working exactly the same
way here for me (Debian Sarge with self-compiles MySQL)

MySQL is started with UNIX socket only:
,---[ grep networking /etc/my.cnf ]
| skip-networking
`----

No my MySQL is listening on TCP port 3306:
,---[ lsof -n -i :3306 ]
|
`----

As sqlgrey doesn't seem to return the error why the query failed,
,---
| [...]
| Use of uninitialized value in concatenation (.) or string at
| /usr/local/sbin/sqlgrey line 227.
|
| (which would be the $DBI::errstr here
`---
please open a shell an execute this line an send us what error that is
returned by it:

,---
| perl -MDBI -le 'my $db=3DDBI->connect("DBI:mysql:database=3Dsqlgrey;host=
=3Dlocalhost","youruser","yourpass",undef) or die "Error: $DBI::errstr"$db-=
>disconnect()'
`---

Regards
Winfried

--=20
Winfried Neessen                           Phone:       +49 221 2612601
neessen.net - Webhosting                   Fax:         +49 221 2612602
Peter-Bauer-Str. 9                         Email:  win...@ne...
50823 Cologne                              PGP/GPG Key-ID:   0xda5cd8ef

Re: [Sqlgrey-users] Sqlgrey dies while creating mysql tables

[Dan F. <da...@ha...>]

Not sure. I run on several sqlgreys on Debian Sarge myself and havnt had 
this problem.

But i do seem to recall that the default Debian settings for Mysql is 
either having "skip-networking" enabled or bind to 127.0.0.1 (depending 
on versions).

If skip-networking is enabled, that would definently explain it, as 
sqlgrey doesn't connect through the socket file 
"/var/run/mysqld/mysqld.sock" like eg. php does pr. default.

and if mysql is bound to 127.0.0.1 and youre using the servers real ip 
or hostname in db_host, then that would also explain your problem.

- Dan



Juraj Variny wrote:
> Hello,
>
> I am trying to set it up on Debian Sarge.  In /etc/sqlgrey/sqlgrey.conf I have 
> only:
>
> db_type=mysql
> db_name=sqlgrey
> db_user=XXXX
> db_pass=YYYY
>
> When I start sqlgrey, it dies and leaves following in syslog. The db_user and 
> pass are correct. Please advise where could be the problem.
>
> Jan 10 16:07:28 testserver sqlgrey: Process Backgrounded
> Jan 10 16:07:28 testserver sqlgrey: 2007/01/10-16:07:28 sqlgrey (type 
> Net::Server::Multiplex) starting! pid(1658)
> Jan 10 16:07:28 testserver sqlgrey: Binding to TCP port 2501 on host localhost
> Jan 10 16:07:28 testserver sqlgrey: Setting gid to "109 109"
> Jan 10 16:07:28 testserver sqlgrey: Setting uid to "108"
> Jan 10 16:07:28 testserver sqlgrey: warning: Use of uninitialized value in 
> concatenation (.) or string at /usr/local/sbin/sqlgrey line 227.
> Jan 10 16:07:28 testserver sqlgrey: dbaccess: warning: couldn't do query: 
> CREATE TABLE from_awl (sender_name varchar(64) NOT NULL, sender_domain 
> varchar(255) NOT NULL, src va
> rchar(39) NOT NULL, first_seen timestamp NOT NULL, last_seen timestamp NOT 
> NULL, PRIMARY KEY (src, sender_domain, sender_name)): , reconnecting to DB
> Jan 10 16:07:28 testserver sqlgrey: mail: child exited with value: 1
> Jan 10 16:07:28 testserver sqlgrey: fatal: create_from_awl_table error 
> at /usr/local/sbin/sqlgrey line 176.
>
>
>   

[Sqlgrey-users] Sqlgrey dies while creating mysql tables

[Juraj V. <ju...@eq...>]

Hello,

I am trying to set it up on Debian Sarge.  In /etc/sqlgrey/sqlgrey.conf I have 
only:

db_type=mysql
db_name=sqlgrey
db_user=XXXX
db_pass=YYYY

When I start sqlgrey, it dies and leaves following in syslog. The db_user and 
pass are correct. Please advise where could be the problem.

Jan 10 16:07:28 testserver sqlgrey: Process Backgrounded
Jan 10 16:07:28 testserver sqlgrey: 2007/01/10-16:07:28 sqlgrey (type 
Net::Server::Multiplex) starting! pid(1658)
Jan 10 16:07:28 testserver sqlgrey: Binding to TCP port 2501 on host localhost
Jan 10 16:07:28 testserver sqlgrey: Setting gid to "109 109"
Jan 10 16:07:28 testserver sqlgrey: Setting uid to "108"
Jan 10 16:07:28 testserver sqlgrey: warning: Use of uninitialized value in 
concatenation (.) or string at /usr/local/sbin/sqlgrey line 227.
Jan 10 16:07:28 testserver sqlgrey: dbaccess: warning: couldn't do query: 
CREATE TABLE from_awl (sender_name varchar(64) NOT NULL, sender_domain 
varchar(255) NOT NULL, src va
rchar(39) NOT NULL, first_seen timestamp NOT NULL, last_seen timestamp NOT 
NULL, PRIMARY KEY (src, sender_domain, sender_name)): , reconnecting to DB
Jan 10 16:07:28 testserver sqlgrey: mail: child exited with value: 1
Jan 10 16:07:28 testserver sqlgrey: fatal: create_from_awl_table error 
at /usr/local/sbin/sqlgrey line 176.


-- 
Juraj Variny <ju...@eq...>

Administrator, Developer
Equilibrium Ltd. / Rovnovaha s r.o.
http://www.equit.sk/

Re: [Sqlgrey-users] sqlgrey dying

[Lionel B. <lio...@bo...>]

Steve Heaven wrote the following on 09.01.2007 10:34 :
>
> sqlgrey has recently started dying, see log entries below:
>
>
> Jan  5 14:58:02 frigga sqlgrey: fatal: Quantifier follows nothing in 
> regex; marked by <-- HERE in m/+ <-- HERE 
> [.*-]+_-jjv[=\?\*~\.]+?identify[.*-]+co[.*-]+uk|identify[.*-]+co[.*-]+uk[=\?\*~\.]+?+[.*-]+_-jjv|+[.*-]+_-jjv/ 
> at /usr/sbin/sqlgrey line 997.
>
> Jan  9 03:36:14 frigga sqlgrey: fatal: Quantifier follows nothing in 
> regex; marked by <-- HERE in m/+ <-- HERE 
> [.*-]+_-ndih[=\?\*~\.]+?michaelwood[.*-]+co[.*-]+uk|michaelwood[.*-]+co[.*-]+uk[=\?\*~\.]+?+[.*-]+_-ndih|+[.*-]+_-ndih/ 
> at /usr/sbin/sqlgrey line 997.
>
>
> In the lines above both identify.co.uk & michaelwood.co.uk are domains 
> hosted by us.
>
> We are running  V1.7.1

If you need the development version functionalities, please use 1.7.4. 
If not, 1.6.7 is the latest stable version.

Bug reports for intermediate versions take more efforts to check and 
might even be solved in the latest versions.

Lionel.

[Sqlgrey-users] sqlgrey dying

[Steve H. <st...@th...>]

sqlgrey has recently started dying, see log entries below:


Jan  5 14:58:02 frigga sqlgrey: fatal: Quantifier follows nothing in
regex; marked by <-- HERE in m/+ <-- HERE [.*-]+_-jjv[=\?\*~\.]+?
identify[.*-]+co[.*-]+uk|identify[.*-]+co[.*-]+uk[=\?\*~\.]+?+[.*-]+_-
jjv|+[.*-]+_-jjv/ at /usr/sbin/sqlgrey line 997.

Jan  9 03:36:14 frigga sqlgrey: fatal: Quantifier follows nothing in
regex; marked by <-- HERE in m/+ <-- HERE [.*-]+_-ndih[=\?\*~\.]+?
michaelwood[.*-]+co[.*-]+uk|michaelwood[.*-]+co[.*-]+uk[=\?\*~\.]+?
+[.*-]+_-ndih|+[.*-]+_-ndih/ at /usr/sbin/sqlgrey line 997.


In the lines above both identify.co.uk & michaelwood.co.uk are domains
hosted by us.

We are running  V1.7.1


-- 
thorNET
Internet Services, Consultancy & Training
www.thornet.co.uk

[Sqlgrey-users] Moving postgres from unicode to ascii

[Andrew D. <and...@gm...>]

Hello SQLgrey,

  I ran into problems using a postgres database with unicode encoding,
since sqlgrey isn't designed for unicode.  Pesky Internet standards.
Anyway, this is how I migrated it, for the good of the archives:

1. Create a new database with SQL_ASCII encoding:
andrew@tango:~> createdb -E SQL_ASCII -O sqlgrey sqlgreyascii

2. View that the database really exists:
andrew@tango:~> psql -l
          List of databases
     Name     |  Owner   | Encoding
--------------+----------+-----------
 sqlgrey      | sqlgrey  | UNICODE
 sqlgreyascii | sqlgrey  | SQL_ASCII
 template0    | postgres | UNICODE
 template1    | postgres | UNICODE

3. Dump the existing sqlgrey database:
andrew@tango:~> pg_dump sqlgrey > sqlgrey.20061228

4. Restore it into the new database:
andrew@tango:~> psql sqlgreyascii < sqlgrey.20061228
(database SETs, etc.)

5. Edit /etc/sqlgrey/sqlgrey.conf, adding "db_name = sqlgreyascii" (I
had used the default name previously, so I just set the new name.)

6. Restart sqlgrey:
/etc/init.d/sqlgrey restart

I have a low volume system (a few thousand emails a day) so I left
SQLgrey running during the db work. It's running just fine now, and I
don't expect to get the db reset emails anymore.

-- 
Best regards,
 Andrew

Re: [Sqlgrey-users] More on sqlgrey stop/recover issue

[Juan P. B. <jp...@gr...>]

Well, my DB is in latin1, as the whole mysql, same problem.
Im being flooded with 50+ emails with db disconnect, db reconnected all =
the
time.
Sorry not to mention the exact frace cose i delete with a rule all those
mails.

> -----Original Message-----
> From: sql...@li...=20
> [mailto:sql...@li...] On=20
> Behalf Of Andrew Diederich
> Sent: Monday, December 18, 2006 20:14
> To: SQLgrey users mailing-list
> Subject: Re: [Sqlgrey-users] More on sqlgrey stop/recover issue
>=20
>=20
> Hello Lionel,
>=20
> Monday, December 18, 2006, 1:32:39 PM, you wrote:
>=20
> > Andrew Diederich wrote the following on 18.12.2006 21:14 :
> >> Dec 18 12:32:43 tango sqlgrey: dbaccess: warning: couldn't=20
> do query: UPDATE from_awl SET last_seen =3D NOW(), first_seen =3D=20
> first_seen WHERE sender_name =3D 'man?=B9genervy' AND=20
> sender_domain =3D 'abyss.wesn.sun.com' AND src =3D=20
> '81.215.189.168': ERROR:  invalid byte sequence for encoding=20
> "UNICODE": 0xe86765 , reconnecting to DB
> >>  =20
>=20
> > Hum, did you try to use a database with ASCII instead of UNICODE?=20
> > SQLgrey doesn't try to speak utf-8 with the database but only pure=20
> > ASCII. If you receive adresses with characters outside the=20
> utf-8 space,
> > this behavior is expected with a UNICODE database.
>=20
> <rest snipped>
>=20
> I bet that's it.  My database is in UNICODE.  I'll try a dump and
> restore later this week and let you know how that goes.
>=20
> Thanks for the tip.
>=20
> --=20
> Best regards,
>  Andrew
>=20
>=20
> --------------------------------------------------------------
> -----------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the=20
> chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge
&CID=3DDEVDEV
_______________________________________________
Sqlgrey-users mailing list
Sql...@li...
https://lists.sourceforge.net/lists/listinfo/sqlgrey-users

Re: [Sqlgrey-users] More on sqlgrey stop/recover issue

[Andrew D. <and...@gm...>]

Hello Lionel,

Monday, December 18, 2006, 1:32:39 PM, you wrote:

> Andrew Diederich wrote the following on 18.12.2006 21:14 :
>> Dec 18 12:32:43 tango sqlgrey: dbaccess: warning: couldn't do query: UPD=
ATE from_awl SET last_seen =3D NOW(), first_seen =3D first_seen WHERE sende=
r_name =3D 'man=C3=83=C5=A1genervy' AND sender_domain =3D 'abyss.wesn.sun.c=
om' AND src =3D '81.215.189.168': ERROR:  invalid byte sequence for encodin=
g "UNICODE": 0xe86765 , reconnecting to DB
>>  =20

> Hum, did you try to use a database with ASCII instead of UNICODE?=20
> SQLgrey doesn't try to speak utf-8 with the database but only pure=20
> ASCII. If you receive adresses with characters outside the utf-8 space,
> this behavior is expected with a UNICODE database.

<rest snipped>

I bet that's it.  My database is in UNICODE.  I'll try a dump and
restore later this week and let you know how that goes.

Thanks for the tip.

--=20
Best regards,
 Andrew