sqlgrey-users — Users of SQLgrey

AW: AW: AW: [Sqlgrey-users] sqlgrey: warning: Use of uninitialize d va lue in ....

[<Fra...@co...>]

Oh,
than this will be a feature request :)
For a virusfilter ist maybe necessary that the mal must go though the =
filter
but for Greylisting I don't think that this is needed in every case.=20
So the Spamassassin solution is better for my opinion.=20
A small spamc program try 3 times to connect the spamd process and if =
there
is no process the mail will be delived without a SPAM check.
Frank

> -----Urspr=FCngliche Nachricht-----
> Von: sql...@li...=20
> [mailto:sql...@li...] Im Auftrag=20
> von Lionel Bouton
> Gesendet: Montag, 24. Oktober 2005 16:17
> An: sql...@li...
> Betreff: Re: AW: AW: [Sqlgrey-users] sqlgrey: warning: Use of=20
> uninitialized va lue in ....
>=20
> Fra...@co... wrote the following on 24.10.2005 16:04 :
>=20
> >Hi Lionle,
> >
> >I have also the problem that when SQLGrey dies all mails are=20
> rejected:
> >
> >Oct 24 15:15:46 mail1 postfix/smtpd[14361]: NOQUEUE: reject:=20
> RCPT from
> >mx.xxxxxx.de[83.137.102.4]: 450 Server configuration problem;=20
> >from=3D<ro...@xx...> to=3D<Mar...@xx...> proto=3DESMTP=20
> >helo=3D<mx.xxxxx.de>
> >
> >Can you give me a hint what I have to do in my=20
> main.cf/master.cf that=20
> >in this case mails are delivered without a SQLGrey check?
> > =20
> >
>=20
> You simply can't, Postfix doesn't support it. If you need=20
> stability, please use the 1.6.X branch (the stable one, 1.6.7=20
> is the latest bugfix
> release) and use clean_method =3D sync as advised in the=20
> example configuration file.
>=20
> Lionel.
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.
> Get Certified Today * Register for a JBoss Training Course=20
> Free Certification Exam for All Training Attendees Through=20
> End of 2005 Visit http://www.jboss.com/services/certification=20
> for more information _______________________________________________
> Sqlgrey-users mailing list
> Sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users
>=20

Re: AW: AW: [Sqlgrey-users] sqlgrey: warning: Use of uninitialized va lue in ....

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

Fra...@co... wrote the following on 24.10.2005 16:04 :

>Hi Lionle,
>
>I have also the problem that when SQLGrey dies all mails are rejected:
>
>Oct 24 15:15:46 mail1 postfix/smtpd[14361]: NOQUEUE: reject: RCPT from
>mx.xxxxxx.de[83.137.102.4]: 450 Server configuration problem;
>from=<ro...@xx...> to=<Mar...@xx...> proto=ESMTP
>helo=<mx.xxxxx.de> 
>
>Can you give me a hint what I have to do in my main.cf/master.cf that in
>this case mails are delivered without a SQLGrey check?
>  
>

You simply can't, Postfix doesn't support it. If you need stability, 
please use the 1.6.X branch (the stable one, 1.6.7 is the latest bugfix 
release) and use clean_method = sync as advised in the example 
configuration file.

Lionel.

AW: AW: [Sqlgrey-users] sqlgrey: warning: Use of uninitialized va lue in ....

[<Fra...@co...>]

Hi Lionle,

I have also the problem that when SQLGrey dies all mails are rejected:

Oct 24 15:15:46 mail1 postfix/smtpd[14361]: NOQUEUE: reject: RCPT from
mx.xxxxxx.de[83.137.102.4]: 450 Server configuration problem;
from=3D<ro...@xx...> to=3D<Mar...@xx...> proto=3DESMTP
helo=3D<mx.xxxxx.de>=20

Can you give me a hint what I have to do in my main.cf/master.cf that =
in
this case mails are delivered without a SQLGrey check?

Frank

main.cf

smtpd_recipient_restrictions =3D
           permit_mynetworks,
           permit_sasl_authenticated,
           check_recipient_access hash:/etc/postfix/access,
           reject_non_fqdn_recipient,
           reject_unauth_destination
           reject_unlisted_recipient,
           check_policy_service inet:127.0.0.1:2501,
           permit_auth_destination,
           reject



> -----Urspr=FCngliche Nachricht-----
> Von: sql...@li...=20
> [mailto:sql...@li...] Im Auftrag=20
> von Lionel Bouton
> Gesendet: Donnerstag, 29. September 2005 14:34
> An: sql...@li...
> Betreff: Re: AW: [Sqlgrey-users] sqlgrey: warning: Use of=20
> uninitialized value in ....
>=20
> Fra...@co... wrote the following on 29.09.2005 11:43 :
>=20
> >>This is a bug introduced with the connect cleanup in 1.7.0.=20
> >>In fact the CVS HEAD doesn't have this bug anymore because=20
> I cleaned=20
> >>up the related methods and removed the bug without noticing it!
> >>
> >>1.7.2 will correct this.
> >>
> >>Lionel.
> >>   =20
> >>
> >
> >Since Im using 1.7.1 the sqlgrey deamon dies from time to time.
> >Im using 5 mailserver and only on one of them the database=20
> (mysql) is=20
> >running for all server The process dies several times a day on all=20
> >servers, expect the server where the database is running Is=20
> this maybe=20
> >also a problem of the "uninitialized value in ....". I can see this=20
> >errormessage also in my log. I cant find any other errormessage.
> > =20
> >
>=20
> The log should tell the line number. Could you please give me=20
> an extract with the line numbers? This would ease the bug=20
> hunting a lot.
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads,=20
> discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Sqlgrey-users mailing list
> Sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users
>=20

Re: [Sqlgrey-users] uninitialized values in 1.6.6

[Sascha L. <sas...@ru...>]

Hi Lionel,

> Then all the lines where you get an unitialised value are from the 
> "cleanup_*" methods. Do you use "clean_method=async" by any chance? If this

I think I use clean_method=sync. The truth is, I have the parameter 
clean_method not set in sqlgrey.conf, believing the default would be sync. 
Isn't it?

> is true, please try to revert to "clean_method=sync". There are bugs in the

For now I set it explicit in sqlgrey.conf and I'll try the new release 
1.6.7.

Thanks for your fast answer.

Sascha.

[Sqlgrey-users] 1.7.2 tests

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

I borked my mail server with the current 1.7.2 code. This is most 
probably the asynchronous cleanup code biting. I've added the 
cleanup_method support in sqlgrey.conf and retried with sync. More news 
later.

Lionel.

Re: AW: AW: [Sqlgrey-users] sqlgrey: warning: Use of uninitialized va lue in ....

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

Fra...@co... wrote the following on 19.10.2005 20:28 :

>>1.7.2 will correct this.
>>
>>Lionel.
>>    
>>
>Hi,
>
>I have a lot of trouble with this bug. How long will it need until the new
>version will be ready?
>What can I do to fix the problem by hand???
>  
>

1.7.2 is currently tested on my mail server. If all goes well I'll 
release it tomorrow.

Lionel

[Sqlgrey-users] [RELEASE] 1.6.7

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

Hi,

this is a small bugfix release. It might fix some odd problems with 
database unavailability (all undefined variables are now checked for, 
which not only removes odd log errors but also protects against 
undefined behaviour).

http://sourceforge.net/project/showfiles.php?group_id=113566&package_id=155492&release_id=365539

no RPM yet. Rpm-based distribution users, please use "rpmbuid -ta 
sqlgrey-1.6.7.tar.bz2"

Happy greylisting,

Lionel.

Re: [Sqlgrey-users] multiple databases ?

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

Who Knows wrote the following on 29.09.2005 04:46 :

> Lionel Bouton wrote:
>
>> So several messages like this were rejected. If I understand 
>> correctly SQLgrey recovered when the database came back. Did some 
>> messages get through while the database was down or each and every 
>> message were tempfailed ?
>>
>> Lionel
>
>
> to the best of my knowledge all inbound messages were rejected with 
> 450 until the sql server was restored to service.
>

I reviewed the whole 1.6.x code looking for a case where it could reject 
the message when the DB is not reachable and found none obvious.

I just uploaded 1.6.7 which fixes the odd log errors you witnessed. 
There is a remote possibility that they were linked to the rejects you 
witnessed (I'm not sure how Perl handles the undefined variables, the 
calling methods could abort at mid-processing which *could* explain 
messages being rejected).

Lionel.

Re: [Sqlgrey-users] uninitialized values in 1.6.6

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

Hi all,

I'm going back to sqlgrey bug-fixing after a long pause. Sorry for the 
wait, I was doing intense C++ development at work lately and was quite 
disgusted by the code-writing task when coming home :-/


Sascha Lucas wrote the following on 23.10.2005 14:18 :

> Hi,
>
> I read the thread about uninitialized values. It was said, that 1.7.x 
> was effected. But just some days ago I have this messages in 1.6.6.
>
> Example:
>
> Oct 23 01:37:33 charybdis sqlgrey: warning: Use of uninitialized value 
> in concatenation (.) or string at /usr/sbin/sqlgrey line 228.
> Oct 23 01:40:32 charybdis sqlgrey: warning: Use of uninitialized value 
> in string eq at /usr/sbin/sqlgrey line 1192.
> Oct 23 01:40:32 charybdis sqlgrey: warning: Use of uninitialized value 
> in string eq at /usr/sbin/sqlgrey line 1204.
> Oct 23 01:40:32 charybdis sqlgrey: warning: Use of uninitialized value 
> in string eq at /usr/sbin/sqlgrey line 1396.
> Oct 23 02:15:40 charybdis sqlgrey: warning: Use of uninitialized value 
> in string eq at /usr/sbin/sqlgrey line 1192.
> Oct 23 02:15:40 charybdis sqlgrey: warning: Use of uninitialized value 
> in string eq at /usr/sbin/sqlgrey line 1204.
>
>
> one example which triggers mysql blocking:
>
> Oct 23 01:37:33 charybdis sqlgrey: warning: Use of uninitialized value 
> in concatenation (.) or string at /usr/sbin/sqlgrey line 228.
>
> Oct 23 01:37:33 charybdis sqlgrey: dbaccess: warning: couldn't do 
> query: INSERT INTO from_awl (sender_name, sender_domain, src, 
> first_seen, last_seen) 
> VALUES('stk1ny','aol.com','66.51.199','20051023013052',NOW()): , 
> reconnecting to DB


The first line means that there's an undefined string in the log that 
follows. On inspection the only missing string is "$DBI::errstr". This 
is odd because the log is there to report an error in database access 
which is *supposed* to set $DBI::errstr.

Then all the lines where you get an unitialised value are from the 
"cleanup_*" methods. Do you use "clean_method=async" by any chance? If 
this is true, please try to revert to "clean_method=sync". There are 
bugs in the async code that seems to be burried deep in the code and 
will probably be resolved only in the 1.7.x branch later (there are 
warnings in the 1.6.6 sqlgrey.conf).

Regards,

Lionel.

[Sqlgrey-users] uninitialized values in 1.6.6

[Sascha L. <sas...@ru...>]

Hi,

I read the thread about uninitialized values. It was said, that 1.7.x was 
effected. But just some days ago I have this messages in 1.6.6.

Example:

Oct 23 01:37:33 charybdis sqlgrey: warning: Use of uninitialized value in 
concatenation (.) or string at /usr/sbin/sqlgrey line 228.
Oct 23 01:40:32 charybdis sqlgrey: warning: Use of uninitialized value in 
string eq at /usr/sbin/sqlgrey line 1192.
Oct 23 01:40:32 charybdis sqlgrey: warning: Use of uninitialized value in 
string eq at /usr/sbin/sqlgrey line 1204.
Oct 23 01:40:32 charybdis sqlgrey: warning: Use of uninitialized value in 
string eq at /usr/sbin/sqlgrey line 1396.
Oct 23 02:15:40 charybdis sqlgrey: warning: Use of uninitialized value in 
string eq at /usr/sbin/sqlgrey line 1192.
Oct 23 02:15:40 charybdis sqlgrey: warning: Use of uninitialized value in 
string eq at /usr/sbin/sqlgrey line 1204.


one example which triggers mysql blocking:

Oct 23 01:37:33 charybdis sqlgrey: warning: Use of uninitialized value in 
concatenation (.) or string at /usr/sbin/sqlgrey line 228.

Oct 23 01:37:33 charybdis sqlgrey: dbaccess: warning: couldn't do query: 
INSERT INTO from_awl (sender_name, sender_domain, src, first_seen, 
last_seen) VALUES('stk1ny','aol.com','66.51.199','20051023013052',NOW()): 
, reconnecting to DB

Oct 23 01:37:33 charybdis sqlgrey: dbaccess: warning: couldn't do query: 
DELETE FROM connect WHERE sender_name = 'stk1ny' AND sender_domain = 
'aol.com' AND src = '66.51.199': Host 'charybdis.rus.uni-stuttgart.de' is 
bloc ked because of many connection errors.  Unblock with 'mysqladmin 
flush-hosts', reconnecting to DB


This happens 2-3 times a week. What can I do?

Sascha.

AW: AW: [Sqlgrey-users] sqlgrey: warning: Use of uninitialized va lue in ....

[<Fra...@co...>]

>1.7.2 will correct this.
>
>Lionel.
Hi,

I have a lot of trouble with this bug. How long will it need until the new
version will be ready?
What can I do to fix the problem by hand???

Frank

Re: [Sqlgrey-users] sqlgrey: warning: Use of uninitialized value in . ...

[Michael S. <Mic...@lr...>]

On Fri, 30 Sep 2005 Fra...@co... wrote:

> Is there nobody else with this problem?

Normally it happens only with unusual addresses. Therefore it could be
that no one else saw this error yet.


>
> Sep 30 11:34:36 mail5 sqlgrey: fatal: Quantifier follows nothing in regex;
> marked by <-- HERE in m/* <-- HERE
> *hn[.*-]+clouser[=\?\*~\.]+?commerzbank[.*-]+com|commerzbank[.*-]+com[=\?\*~
> \.]+?**hn[.*-]+clouser|**hn[.*-]+clouser/ at /usr/sbin/sqlgrey line 997.
>

Michael Storz
-------------------------------------------------
Leibniz-Rechenzentrum   !   <mailto:St...@lr...>
Barer Str. 21           !   Fax: +49 89 2809460
80333 Muenchen, Germany !   Tel: +49 89 289-28840

Re: AW: AW: [Sqlgrey-users] sqlgrey: warning: Use of uninitialized va lue in ....

[Michael S. <Mic...@lr...>]

On Thu, 29 Sep 2005 Fra...@co... wrote:

> > >Since Im using 1.7.1 the sqlgrey deamon dies from time to time.
> > >Im using 5 mailserver and only on one of them the database
> > (mysql) is
> > >running for all server The process dies several times a day on all
> > >servers, expect the server where the database is running Is
> > this maybe
> > >also a problem of the "uninitialized value in ....". I can see this
> > >errormessage also in my log. I cant find any other errormessage.
> > >
> > >
> >
> > The log should tell the line number. Could you please give me
> > an extract with the line numbers? This would ease the bug
> > hunting a lot.
>
> Oh. No if found somemore messages
>
> Sep 29 11:12:03 mail2 sqlgrey: warning: Use of uninitialized value in
> substitution (s///) at /usr/sbin/sqlgrey line 994.
> Sep 29 11:12:03 mail2 sqlgrey: warning: Use of uninitialized value in split
> at /usr/sbin/sqlgrey line 995.
> Sep 29 11:12:03 mail2 sqlgrey: warning: Use of uninitialized value in
> concatenation (.) or string at /usr/sbin/sqlgrey line 997.
> Sep 29 11:12:03 mail2 sqlgrey: fatal: Quantifier follows nothing in regex;
> marked by <-- HERE in m/* <-- HERE
> *hn[.*-]+clouser[=\?\*~\.]+?commerzbank[.*-]+com|commerzbank[.*-]+com[=\?\*~
> \.]+?**hn[.*-]+clouser|**hn[.*-]+clouser/ at /usr/sbin/sqlgrey line 997.
>

Indeed this is an error in 1.7.1, which was introduced by my code I send
Lionel. Unfortunately Lionel released 1.7.1 without the patch I send him
for this error. The problem is the missing escape for meta characters in
email addresses like '*'.

Look in the other lines of the log and you will find that the address
includes a '*', if I am right.

My last mailing where I included the sub deverp_user has the patch
applied.

Michael Storz
-------------------------------------------------
Leibniz-Rechenzentrum   !   <mailto:St...@lr...>
Barer Str. 21           !   Fax: +49 89 2809460
80333 Muenchen, Germany !   Tel: +49 89 289-28840

[Sqlgrey-users] sqlgrey: warning: Use of uninitialized value in . ...

[<Fra...@co...>]

Is there nobody else with this problem?

Sep 30 11:34:36 mail5 sqlgrey: fatal: Quantifier follows nothing in regex;
marked by <-- HERE in m/* <-- HERE
*hn[.*-]+clouser[=\?\*~\.]+?commerzbank[.*-]+com|commerzbank[.*-]+com[=\?\*~
\.]+?**hn[.*-]+clouser|**hn[.*-]+clouser/ at /usr/sbin/sqlgrey line 997.

I



> >Since Im using 1.7.1 the sqlgrey deamon dies from time to time.
> >Im using 5 mailserver and only on one of them the database 
> (mysql) is 
> >running for all server The process dies several times a day on all 
> >servers, expect the server where the database is running Is 
> this maybe 
> >also a problem of the "uninitialized value in ....". I can see this 
> >errormessage also in my log. I cant find any other errormessage.
> >  
> >
> 
> The log should tell the line number. Could you please give me 
> an extract with the line numbers? This would ease the bug 
> hunting a lot.

Oh. No if found somemore messages

Sep 29 11:12:03 mail2 sqlgrey: warning: Use of uninitialized value in
substitution (s///) at /usr/sbin/sqlgrey line 994. 
Sep 29 11:12:03 mail2 sqlgrey: warning: Use of uninitialized value in split
at /usr/sbin/sqlgrey line 995. 
Sep 29 11:12:03 mail2 sqlgrey: warning: Use of uninitialized value in
concatenation (.) or string at /usr/sbin/sqlgrey line 997. 
Sep 29 11:12:03 mail2 sqlgrey: fatal: Quantifier follows nothing in regex;
marked by <-- HERE in m/* <-- HERE
*hn[.*-]+clouser[=\?\*~\.]+?commerzbank[.*-]+com|commerzbank[.*-]+com[=\?\*~
\.]+?**hn[.*-]+clouser|**hn[.*-]+clouser/ at /usr/sbin/sqlgrey line 997.  

AW: AW: [Sqlgrey-users] sqlgrey: warning: Use of uninitialized va lue in ....

[<Fra...@co...>]

> >Since Im using 1.7.1 the sqlgrey deamon dies from time to time.
> >Im using 5 mailserver and only on one of them the database 
> (mysql) is 
> >running for all server The process dies several times a day on all 
> >servers, expect the server where the database is running Is 
> this maybe 
> >also a problem of the "uninitialized value in ....". I can see this 
> >errormessage also in my log. I cant find any other errormessage.
> >  
> >
> 
> The log should tell the line number. Could you please give me 
> an extract with the line numbers? This would ease the bug 
> hunting a lot.

Oh. No if found somemore messages

Sep 29 11:12:03 mail2 sqlgrey: warning: Use of uninitialized value in
substitution (s///) at /usr/sbin/sqlgrey line 994. 
Sep 29 11:12:03 mail2 sqlgrey: warning: Use of uninitialized value in split
at /usr/sbin/sqlgrey line 995. 
Sep 29 11:12:03 mail2 sqlgrey: warning: Use of uninitialized value in
concatenation (.) or string at /usr/sbin/sqlgrey line 997. 
Sep 29 11:12:03 mail2 sqlgrey: fatal: Quantifier follows nothing in regex;
marked by <-- HERE in m/* <-- HERE
*hn[.*-]+clouser[=\?\*~\.]+?commerzbank[.*-]+com|commerzbank[.*-]+com[=\?\*~
\.]+?**hn[.*-]+clouser|**hn[.*-]+clouser/ at /usr/sbin/sqlgrey line 997.  

Re: AW: [Sqlgrey-users] sqlgrey: warning: Use of uninitialized value in ....

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

Fra...@co... wrote the following on 29.09.2005 11:43 :

>>This is a bug introduced with the connect cleanup in 1.7.0. 
>>In fact the CVS HEAD doesn't have this bug anymore because I 
>>cleaned up the related methods and removed the bug without 
>>noticing it!
>>
>>1.7.2 will correct this.
>>
>>Lionel.
>>    
>>
>
>Since Im using 1.7.1 the sqlgrey deamon dies from time to time.
>Im using 5 mailserver and only on one of them the database (mysql) is
>running for all server
>The process dies several times a day on all servers, expect the server where
>the database is running
>Is this maybe also a problem of the "uninitialized value in ....". I can see
>this errormessage also in my log. I cant find any other errormessage.
>  
>

The log should tell the line number. Could you please give me an extract 
with the line numbers? This would ease the bug hunting a lot.

Re: AW: [Sqlgrey-users] sqlgrey: warning: Use of uninitialized value in ....

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

Steve Heaven wrote the following on 29.09.2005 11:52 :

> On Thu, 2005-09-29 at 10:43, Fra...@co... wrote:
>
>>/> This is a bug introduced with the connect cleanup in 1.7.0. 
>>> In fact the CVS HEAD doesn't have this bug anymore because I 
>>> cleaned up the related methods and removed the bug without 
>>> noticing it!
>>> 
>>> 1.7.2 will correct this./
>>
> We're using 1.7.1 and get quite a few of these:
>
> Sep 29 10:50:42 balder1 sqlgrey: warning: Use of uninitialized value 
> in substitution (s///) at /usr/sbin/sqlgrey line 994.
> Sep 29 10:50:42 balder1 sqlgrey: warning: Use of uninitialized value 
> in split at /usr/sbin/sqlgrey line 995.
> Sep 29 10:50:42 balder1 sqlgrey: warning: Use of uninitialized value 
> in concatenation (.) or string at /usr/sbin/sqlgrey line 997.
>
>
> Is that the same bug ?


It is.

Re: AW: [Sqlgrey-users] sqlgrey: warning: Use of uninitialized value in ....

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

On Thu, 2005-09-29 at 10:43, Fra...@co... wrote:

> > This is a bug introduced with the connect cleanup in 1.7.0. 
> > In fact the CVS HEAD doesn't have this bug anymore because I 
> > cleaned up the related methods and removed the bug without 
> > noticing it!
> > 
> > 1.7.2 will correct this.

We're using 1.7.1 and get quite a few of these:

Sep 29 10:50:42 balder1 sqlgrey: warning: Use of uninitialized value in
substitution (s///) at /usr/sbin/sqlgrey line 994.
Sep 29 10:50:42 balder1 sqlgrey: warning: Use of uninitialized value in
split at /usr/sbin/sqlgrey line 995.
Sep 29 10:50:42 balder1 sqlgrey: warning: Use of uninitialized value in
concatenation (.) or string at /usr/sbin/sqlgrey line 997.


Is that the same bug ?

Steve


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

AW: [Sqlgrey-users] sqlgrey: warning: Use of uninitialized value in ....

[<Fra...@co...>]

> This is a bug introduced with the connect cleanup in 1.7.0. 
> In fact the CVS HEAD doesn't have this bug anymore because I 
> cleaned up the related methods and removed the bug without 
> noticing it!
> 
> 1.7.2 will correct this.
> 
> Lionel.

Since Im using 1.7.1 the sqlgrey deamon dies from time to time.
Im using 5 mailserver and only on one of them the database (mysql) is
running for all server
The process dies several times a day on all servers, expect the server where
the database is running
Is this maybe also a problem of the "uninitialized value in ....". I can see
this errormessage also in my log. I cant find any other errormessage.

Frank

Re: [Sqlgrey-users] multiple databases ?

[Who K. <qui...@me...>]

Lionel Bouton wrote:

> So several messages like this were rejected. If I understand correctly 
> SQLgrey recovered when the database came back. Did some messages get 
> through while the database was down or each and every message were 
> tempfailed ?
>
> Lionel

to the best of my knowledge all inbound messages were rejected with 450 
until the sql server was restored to service.

Re: [Sqlgrey-users] multiple databases ?

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

Who Knows wrote the following on 28.09.2005 03:18 :

> Lionel Bouton wrote:
>
>> No it is automatic. It is designed to recover from both an 
>> unreachable database and simple query errors (no answer or clearly 
>> invalid answers).
>> Do you rely on the database for anything else than SQLgrey? Was 
>> SQLgrey running on the same systems the MTAs were on (ie 
>> policy_service declared as localhost:<something> on each MTA)?
>>
> My old configuration was sqlgrey v1.6.6-1
>
> serverX
>  local MTA - postfix
>  local sqlgrey localhost sqlgraydb
>
> serverY
> local MTA - postfix
> local sqlgrey remote DB serverX sqlgraydb
>
> serverZ
>  local MTA - postfix
>  local sqlgrey serverX sqlgraydb
>
> Here is an exerpt of what was happened for all messages arriving at 
> serverY after serverX swooned:
> NOTE: the ****** are to protect the guilty(or innocent)
>
> Sep 21 07:51:00 serverY postfix/smtpd[3184]: connect from 
> ablist.about.com[207.241.145.4]
> Sep 21 07:51:03 serverY sqlgrey: dbaccess: can't connect to DB: Can't 
> connect to MySQL server on 'serverX.*******'' (110)
> Sep 21 07:51:03 serverY sqlgrey: dbaccess: warning: couldn't do query: 
> DELETE FROM from_awl WHERE last_seen < timestamp '2005-09-20 21:35:36' 
> - INTERVAL 60 DAY: Can't connect to MySQL server on 'serverX.*******'' 
> (110), reconnecting to DB
> Sep 21 07:51:03 serverY sqlgrey: warning: Use of uninitialized value 
> in string eq at /usr/sbin/sqlgrey line 1191.


This odd-looking warning, I can deal with. It may be why some messages 
were rejected but unless SQLgrey died I believe it shouldn't have 
rejected every message but only a few ones (I'll have to check the flow 
of SQL queries to be sure that there's no loophole introduced by a 
recent change, but last time I did it was OK).

>
> Sep 21 07:51:11 serverY postfix/smtpd[3240]: timeout after RSET from 
> unknown[80.232.117.10]
> Sep 21 07:51:11 serverY postfix/smtpd[3240]: disconnect from 
> unknown[80.232.117.10]
> Sep 21 07:51:11 serverY postfix/smtpd[3130]: timeout after RSET from 
> unknown[80.232.117.10]
> Sep 21 07:51:11 serverY postfix/smtpd[3130]: disconnect from 
> unknown[80.232.117.10]
> Sep 21 07:51:17 serverY postfix/smtpd[3265]: connect from 
> mail3.inbox360.com[207.106.213.11]
> Sep 21 07:51:24 serverY postfix/smtpd[3270]: warning: timeout on 
> 127.0.0.1:2501 while reading input attribute name
> Sep 21 07:51:24 serverY postfix/smtpd[3270]: warning: problem talking 
> to server 127.0.0.1:2501: Connection timed out
> Sep 21 07:51:24 serverY postfix/smtpd[3270]: NOQUEUE: reject: RCPT 
> from smtp02.infoave.net[165.166.0.27]: 450 Server configuration 
> problem; from=<mdf...@lo...> to=<webmaster@**********> 
> proto=ESMTP helo=<SMTP02.INFOAVE.NET>
>
>


So several messages like this were rejected. If I understand correctly 
SQLgrey recovered when the database came back. Did some messages get 
through while the database was down or each and every message were 
tempfailed ?

Lionel

Re: [Sqlgrey-users] multiple databases ?

[Who K. <qui...@me...>]

Lionel Bouton wrote:

> No it is automatic. It is designed to recover from both an unreachable 
> database and simple query errors (no answer or clearly invalid answers).
> Do you rely on the database for anything else than SQLgrey? Was 
> SQLgrey running on the same systems the MTAs were on (ie 
> policy_service declared as localhost:<something> on each MTA)?
>
My old configuration was sqlgrey v1.6.6-1

serverX
  local MTA - postfix
  local sqlgrey localhost sqlgraydb

serverY
 local MTA - postfix
 local sqlgrey remote DB serverX sqlgraydb

serverZ
  local MTA - postfix
  local sqlgrey serverX sqlgraydb

Here is an exerpt of what was happened for all messages arriving at 
serverY after serverX swooned:
NOTE: the ****** are to protect the guilty(or innocent)

Sep 21 07:51:00 serverY postfix/smtpd[3184]: connect from 
ablist.about.com[207.241.145.4]
Sep 21 07:51:03 serverY sqlgrey: dbaccess: can't connect to DB: Can't 
connect to MySQL server on 'serverX.*******'' (110)
Sep 21 07:51:03 serverY sqlgrey: dbaccess: warning: couldn't do query: 
DELETE FROM from_awl WHERE last_seen < timestamp '2005-09-20 21:35:36' - 
INTERVAL 60 DAY: Can't connect to MySQL server on 'serverX.*******'' 
(110), reconnecting to DB
Sep 21 07:51:03 serverY sqlgrey: warning: Use of uninitialized value in 
string eq at /usr/sbin/sqlgrey line 1191.
Sep 21 07:51:11 serverY postfix/smtpd[3240]: timeout after RSET from 
unknown[80.232.117.10]
Sep 21 07:51:11 serverY postfix/smtpd[3240]: disconnect from 
unknown[80.232.117.10]
Sep 21 07:51:11 serverY postfix/smtpd[3130]: timeout after RSET from 
unknown[80.232.117.10]
Sep 21 07:51:11 serverY postfix/smtpd[3130]: disconnect from 
unknown[80.232.117.10]
Sep 21 07:51:17 serverY postfix/smtpd[3265]: connect from 
mail3.inbox360.com[207.106.213.11]
Sep 21 07:51:24 serverY postfix/smtpd[3270]: warning: timeout on 
127.0.0.1:2501 while reading input attribute name
Sep 21 07:51:24 serverY postfix/smtpd[3270]: warning: problem talking to 
server 127.0.0.1:2501: Connection timed out
Sep 21 07:51:24 serverY postfix/smtpd[3270]: NOQUEUE: reject: RCPT from 
smtp02.infoave.net[165.166.0.27]: 450 Server configuration problem; 
from=<mdf...@lo...> to=<webmaster@**********> proto=ESMTP 
helo=<SMTP02.INFOAVE.NET>

Re: [Sqlgrey-users] multiple databases ?

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

Who Knows wrote the following on 27.09.2005 17:33 :

> Lionel Bouton wrote:
>
>>
>> Just to clarify:
>>
>> If you have one SQLgrey sitting on each server running a MX server 
>> and all of them configured to use the same database you don't have 
>> any single point of failure.
>> If one MX fails, the other(s) handle the trafic. If the database 
>> server fails, all SQLgrey processes switch to passthrough 
>> automatically (and warn the email address configured in sqlgrey.conf) 
>> -> your MX are unaffected but the greylisting stops.
>> If you have one single SQLgrey process and the server it is sitting 
>> on fails, all "incoming" mail trafic stops (Postfix answers requests 
>> with "service temporary unavailable" errors).
>>
>> Lionel.
>
>
> Okay, I was aware that was what was supposed to happen. Is the switch 
> to passthru in the abscense of a database ( or database error ) a 
> config setting because according to my logs my MTAs returned config 
> error when the database was inacessable.


No it is automatic. It is designed to recover from both an unreachable 
database and simple query errors (no answer or clearly invalid answers).
Do you rely on the database for anything else than SQLgrey? Was SQLgrey 
running on the same systems the MTAs were on (ie policy_service declared 
as localhost:<something> on each MTA)?

Lionel.

Re: [Sqlgrey-users] multiple databases ?

[Who K. <qui...@me...>]

Lionel Bouton wrote:

>
> Just to clarify:
>
> If you have one SQLgrey sitting on each server running a MX server and 
> all of them configured to use the same database you don't have any 
> single point of failure.
> If one MX fails, the other(s) handle the trafic. If the database 
> server fails, all SQLgrey processes switch to passthrough 
> automatically (and warn the email address configured in sqlgrey.conf) 
> -> your MX are unaffected but the greylisting stops.
> If you have one single SQLgrey process and the server it is sitting on 
> fails, all "incoming" mail trafic stops (Postfix answers requests with 
> "service temporary unavailable" errors).
>
> Lionel.

Okay, I was aware that was what was supposed to happen. Is the switch to 
passthru in the abscense of a database ( or database error ) a config 
setting because according to my logs my MTAs returned config error when 
the database was inacessable.

Re: [Sqlgrey-users] cant set gid

[Michael S. <Mic...@lr...>]

On Tue, 27 Sep 2005, Steve Heaven wrote:

> Trying to setup the second server like the first but we get this:
>
> Sep 27 14:18:43 balder1 sqlgrey: Process Backgrounded
> Sep 27 14:18:43 balder1 sqlgrey: 2005/09/27-14:18:43 sqlgrey (type
> Net::Server::Multiplex) starting! pid(18324)
> Sep 27 14:18:43 balder1 sqlgrey: Binding to TCP port 2501 on host
> localhost
> Sep 27 14:18:43 balder1 sqlgrey: Setting gid to "522 522"
> Sep 27 14:18:43 balder1 sqlgrey: 2005/09/27-14:18:43 Couldn't become gid
> "522":     at line 486 in file
> /usr/lib/perl5/site_perl/5.8.0/Net/Server.pm
> Sep 27 14:18:43 balder1 sqlgrey: 2005/09/27-14:18:43 Server closing!

If you have Net::Server 0.88 then this seems to be the problem. 0.88 in
some cases does not work together with perl 5.8.0, as they said on the
amavisd-new list.

In this case either downgrade to 0.87, see
http://marc.theaimsgroup.com/?l=amavis-user&m=111999829830183&w=2

or upgrade to a new perl version (which may create an entirely new can of
worms).

Michael Storz
-------------------------------------------------
Leibniz-Rechenzentrum   !   <mailto:St...@lr...>
Barer Str. 21           !   Fax: +49 89 2809460
80333 Muenchen, Germany !   Tel: +49 89 289-28840