Thread: Re: [Postfixadmin-devel] Regarding Bug #2835877
Brought to you by:
christian_boltz,
gingerdog
Menu
▾
▴
postfixadmin-devel
|
From: David G. <da...@co...> - 2009-10-20 13:50:43
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stevan Bajic wrote: > Message body follows: > > Hallo Gingerdog > Hello! I think there are two bugs - one which is related to the SQL statement - which I think is fixed. Are you able to confirm this with what's in trunk?? The second bug is what I thought I Was replying to - namely there is no need to mangle the email address passed into check_recipient() as it's already been converted from the vacation goto format foo#bar.com@autoreply.whatever to fo...@ba... Does that help? (Are you not able to re-open the ticket?) Thanks David. > You write that you THINK that the patch is not needed. But I > KNOW that the patch is needed because without the patch > vacation is not working on my setup. > > Vacation it self is working but as soon it hit's that wrong > SQL clause which is already in 2.3_rc7 then I get errors. > Please go ahead and try it yourself. You will see that you > will get MySQL and PostgreSQL barking about wrongly formated > SQL clause. > > I get errors like this here: > ug 11 11:24:47 nyx postfix/pipe[15542]: EEA07A3C162: > to=<viktor#laf...@au...net.local>, > orig_to=<vi...@la...>, relay=vacation, delay=0.52, > delays=0.13/0/0/0.38, dsn=5.3.0, status=bounced (Command > died with status 255: "/usr/bin/perl". Command output: > DBD::mysql::st execute failed: You have an error in your SQL > syntax; check the manual that corresponds to your MySQL > server version for the right syntax to use near '% OR goto > LIKE %,'vi...@la...' OR goto LIKE > %,'vi...@la...',%)' at line 1 at > /var/spool/vacation/vacation-postfixadmin-2.3_rc7.pl line > 332, <STDIN> line 45. DBD::mysql::st execute failed: You > have an error in your SQL syntax; check the manual that > corresponds to your MySQL server version for the right > syntax to use near '% OR goto LIKE %,'vi...@la...' OR > goto LIKE %,'vi...@la...',%)' at line 1 at > /var/spool/vacation/vacation-postfixadmin-2.3_rc7.pl line > 332, <STDIN> line 45. ) > > Jul 26 22:33:02 nyx postfix/pipe[12772]: DFE4BA3C160: > to=<rog...@me...@autoreply.vunet.local>, > relay=vacation, delay=0.57, delays=0.12/0.01/0/0.44, > dsn=5.3.0, status=bounced (Command died with status 255: > "/usr/bin/perl". Command output: DBD::mysql::st execute > failed: You have an error in your SQL syntax; check the > manual that corresponds to your MySQL server version for the > right syntax to use near '% OR goto LIKE > %,'rog...@me...' OR goto LIKE > %,'roger.eckerlin@med' at line 1 at > /var/spool/vacation/vacation-postfixadmin-2.3_rc7.pl line > 332, <STDIN> line 40. DBD::mysql::st execute failed: You > have an error in your SQL syntax; check the manual that > corresponds to your MySQL server version for the right > syntax to use near '% OR goto LIKE > %,'rog...@me...' OR goto LIKE > %,'roger.eckerlin@med' at line 1 at > /var/spool/vacation/vacation-postfixadmin-2.3_rc7.pl line > 332, <STDIN> line 40. ) > > So the SQL clause is definitely wrong. > > Could you reopen #2835877 so that we can continue the > discussion there? > > > Kind Regards from Switzerland > > Stevan Bajic > > -- > This message has been sent to you, a registered SourceForge.net user, > by another site user, through the SourceForge.net site. This message > has been delivered to your SourceForge.net mail alias. You may reply > to this message using the "Reply" feature of your email client, or > using the messaging facility of SourceForge.net at: > https://sourceforge.net/sendmessage.php?touser=2515232 > - -- David Goodwin [ david at codepoets dot co dot uk ] [ http://www.codepoets.co.uk ] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkrds00ACgkQ/ISo3RF5V6awZwCg1Q0dqfEWpgtVUJvmqnxHlpFz 7pgAmQFT7ScS+5ILeQw4dpa5rTrxEAEs =lm9J -----END PGP SIGNATURE----- |
|
From: David G. <da...@co...> - 2009-10-20 19:27:53
|
> I checked out trunk and see this here:
> -------------------
> # Recipient has vacation
> if ($rv == 1) {
> $realemail = $email;
> $logger->debug("Found '\$email'\ has vacation active");
> } else {
> my $vemail = $email;
> $vemail =~ s/\@/#/g;
> $logger->debug("Looking for alias records that \'$email\' resolves to with vacation turned on");
> $query = qq{SELECT goto FROM alias WHERE address=? AND (goto LIKE ? OR goto LIKE ? OR goto LIKE ?)};
> $stm = $dbh->prepare($query) or panic_prepare($query);
> $stm->execute($email,"$email,%","%,$email","%,$email,%") or panic_execute($query,"address='$email'");
> $rv = $stm->rows;
> -------------------
>
> This is not going to work. This part here:
> -------------------
> $stm->execute($email,"$email,%","%,$email","%,$email,%") or panic_execute($query,"address='$email'");
> -------------------
>
> Is going to be executed as:
> -------------------
> SELECT goto FROM alias WHERE address='da...@co...' AND (goto LIKE 'da...@co...,%' OR goto LIKE '%,da...@co...' OR goto LIKE '%,da...@co...,%')
> -------------------
>
Hi,
The code above lives in a function called find_recipient() (or
something similar). BEFORE this is called we convert the SMTP
recipient (e.g. foo#bar@autoreply.whatever) to it's real email addres
(e.g. foo@bar). Hence I'm confused as to why you still insist it's
wrong. Can you please read the code which calls that function and
confirm I'm right - perhaps I've totally misread it?
Thanks
David.
|
|
From: Stevan B. <st...@ba...> - 2009-10-20 20:11:07
|
On Tue, 20 Oct 2009 20:27:27 +0100
David Goodwin <da...@co...> wrote:
> > I checked out trunk and see this here:
> > -------------------
> > # Recipient has vacation
> > if ($rv == 1) {
> > $realemail = $email;
> > $logger->debug("Found '\$email'\ has vacation active");
> > } else {
> > my $vemail = $email;
> > $vemail =~ s/\@/#/g;
> > $logger->debug("Looking for alias records that \'$email\' resolves to with vacation turned on");
> > $query = qq{SELECT goto FROM alias WHERE address=? AND (goto LIKE ? OR goto LIKE ? OR goto LIKE ?)};
> > $stm = $dbh->prepare($query) or panic_prepare($query);
> > $stm->execute($email,"$email,%","%,$email","%,$email,%") or panic_execute($query,"address='$email'");
> > $rv = $stm->rows;
> > -------------------
> >
> > This is not going to work. This part here:
> > -------------------
> > $stm->execute($email,"$email,%","%,$email","%,$email,%") or panic_execute($query,"address='$email'");
> > -------------------
> >
> > Is going to be executed as:
> > -------------------
> > SELECT goto FROM alias WHERE address='da...@co...' AND (goto LIKE 'da...@co...,%' OR goto LIKE '%,da...@co...' OR goto LIKE '%,da...@co...,%')
> > -------------------
> >
>
> Hi,
>
Hallo David,
> The code above lives in a function called find_recipient() (or
> something similar).
>
Correct.
> BEFORE this is called we convert the SMTP
> recipient (e.g. foo#bar@autoreply.whatever) to it's real email addres
> (e.g. foo@bar).
>
Correct.
> Hence I'm confused as to why you still insist it's
> wrong. Can you please read the code which calls that function and
> confirm I'm right - perhaps I've totally misread it?
>
You miss the point how the content of the alias table is. Lets look at a normal entry (I removed the created and modified column to make it easier for reading):
+------------------+------------------+-------------+
| address | goto | domain |
+------------------+------------------+-------------+
| @example.com | us...@ex... | example.com |
| us...@ex... | us...@ex... | example.com |
+------------------+------------------+-------------+
Okay. Now "us...@ex..." is going to use Postfix.Admin and add vacation for his account. Beside that the table "vacation" is going to be updated the table "alias" is as well updated and looks like this:
+------------------+--------------------------------------------------+-------------+
| address | goto | domain |
+------------------+--------------------------------------------------+-------------+
| @example.com | us...@ex... | example.com |
| us...@ex... | us...@ex...,user#example.com@vacationdomain | example.com |
+------------------+--------------------------------------------------+-------------+
So lets take a look in the sub called "find_real_address". The purpose of that function is to find users having vacation active. Right? And the purpose of that function is to try hard to find if an alias that got a mail (and aliases do not have "@vacationdomain" in their goto field) in fact has a real address that has vacation active. Right?
So this SQL clause here:
SELECT goto FROM alias WHERE address='us...@ex...' AND (goto LIKE 'us...@ex...,%' OR goto LIKE '%,us...@ex...' OR goto LIKE '%,us...@ex...,%')
Is wrong. It does not honor the vacation goto format. All we want is that the SQL lookup for an alias pointing to an real address (or another alias wich get's then again looked up by the vacation Perl script till it reaches a real address) should only match if that address has in fact vacation active. If goto does not contain the vacation format the the SQL clause should NOT match. That's what I am telling.
Or let's take it the other way around. If you have right then the whole code doing that crazy alias resolving is useless since there is enough to just check for address=$email (wich would be wrong).
The right SQL clause is:
SELECT goto FROM alias WHERE address='us...@ex...' AND (goto LIKE 'user#example.com@%' OR goto LIKE '%,user#example.com@%')
The absolute best (catching all possible cases) SQL clause would be:
SELECT goto FROM alias WHERE address='us...@ex...' AND (goto LIKE 'user#example.com@vacationdomain,%' OR goto LIKE '%,user#example.com@vacationdomain' OR goto LIKE '%,user#example.com@vacationdomain,%' OR goto='user#example.com@vacationdomain')
In Perl code that would be (just the significant lines):
$query = qq{SELECT goto FROM alias WHERE address=? AND (goto LIKE ? OR goto LIKE ? OR goto LIKE ? OR goto=?)};
$stm->execute($email,"$vemail@$vacation_domain,%","%,$vemail@$vacation_domain","%,$vemail@$vacation_domain,%","$vemail@$vacation_domain") or panic_execute($query,"address='$email'");
Do you now understand what I mean?
> Thanks
>
Kind Regards from Switzerland
> David.
>
Stevan Bajic
|
|
From: Stevan B. <st...@ba...> - 2009-10-20 20:25:12
Attachments:
postfix.admin-trunk-vacation.patch
|
On Tue, 20 Oct 2009 20:27:27 +0100
David Goodwin <da...@co...> wrote:
> > I checked out trunk and see this here:
> > -------------------
> > # Recipient has vacation
> > if ($rv == 1) {
> > $realemail = $email;
> > $logger->debug("Found '\$email'\ has vacation active");
> > } else {
> > my $vemail = $email;
> > $vemail =~ s/\@/#/g;
> > $logger->debug("Looking for alias records that \'$email\' resolves to with vacation turned on");
> > $query = qq{SELECT goto FROM alias WHERE address=? AND (goto LIKE ? OR goto LIKE ? OR goto LIKE ?)};
> > $stm = $dbh->prepare($query) or panic_prepare($query);
> > $stm->execute($email,"$email,%","%,$email","%,$email,%") or panic_execute($query,"address='$email'");
> > $rv = $stm->rows;
> > -------------------
> >
> > This is not going to work. This part here:
> > -------------------
> > $stm->execute($email,"$email,%","%,$email","%,$email,%") or panic_execute($query,"address='$email'");
> > -------------------
> >
> > Is going to be executed as:
> > -------------------
> > SELECT goto FROM alias WHERE address='da...@co...' AND (goto LIKE 'da...@co...,%' OR goto LIKE '%,da...@co...' OR goto LIKE '%,da...@co...,%')
> > -------------------
> >
>
> Hi,
>
Hallo David,
> The code above lives in a function called find_recipient() (or
> something similar). BEFORE this is called we convert the SMTP
> recipient (e.g. foo#bar@autoreply.whatever) to it's real email addres
> (e.g. foo@bar). Hence I'm confused as to why you still insist it's
> wrong. Can you please read the code which calls that function and
> confirm I'm right - perhaps I've totally misread it?
>
I have attached the patch I would use to patch Postfix.Admin trunk for fixing that issue regarding alias lookups.
I was so free to change the email addresses in the header to not be directly addressable.
> Thanks
>
Kind Regards from Switzerland
> David.
>
Stevan Bajic
|
|
From: David G. <da...@co...> - 2009-10-21 08:02:29
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> > Hallo David, > > >> The code above lives in a function called find_recipient() (or >> something similar). BEFORE this is called we convert the SMTP >> recipient (e.g. foo#bar@autoreply.whatever) to it's real email addres >> (e.g. foo@bar). Hence I'm confused as to why you still insist it's >> wrong. Can you please read the code which calls that function and >> confirm I'm right - perhaps I've totally misread it? >> > I have attached the patch I would use to patch Postfix.Admin trunk for fixing that issue regarding alias lookups. > > I was so free to change the email addresses in the header to not be directly addressable. > Hi Stevan Thanks for the patch, it was against the Smarty branch which didn't cleanly apply; but I think I've translated it properly. I've merged the change into svn and also updated the ticket on sf.net; thanks for having the patience to explain to me why you are/were right :) thanks David. - -- David Goodwin [ david at codepoets dot co dot uk ] [ http://www.codepoets.co.uk ] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkrewAoACgkQ/ISo3RF5V6YCowCg9+9EykFyjUea7jhiIPyKtiPF MRsAoNIXLIl7i+XO9ieHjdy3gZ3LbdN5 =ADQ7 -----END PGP SIGNATURE----- |
|
From: Stevan B. <st...@ba...> - 2009-10-20 14:58:12
|
On Tue, 20 Oct 2009 13:55:41 +0100 David Goodwin <da...@co...> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Stevan Bajic wrote: > > Message body follows: > > > > Hallo Gingerdog > > > > > Hello! > Hello David > I think there are two bugs - one which is related to the SQL statement - > which I think is fixed. Are you able to confirm this with what's in trunk?? > I have to check. Will inform you as soon as I find time to checkout trunk. > The second bug is what I thought I Was replying to - namely there is no > need to mangle the email address passed into check_recipient() as it's > already been converted from the vacation goto format > foo#bar.com@autoreply.whatever to fo...@ba... > Yes. You are right about that. But the only way to find out by looking at the alias table if an user has vacation active or not is by looking if the goto field has the vacation format. Assuming your own personal vacation domain is "postfixadmin.local" then one needs to craft the SQL clause to be like this here: SELECT goto FROM alias WHERE address='da...@co...' AND (goto LIKE 'david#codepoets.co.uk@%' OR goto LIKE '%,david#codepoets.co.uk@%') The vacation domain "postfixadmin.local" is in fact not even needed but without replacing the "@" sign with "#" one is not able (by only looking at the alias table) to find out if the user "da...@co..." has vacation active or not. And since multi values inside the goto field are separated by a simple "," checking for 'david#codepoets.co.uk@%' or '%,david#codepoets.co.uk@%' is enough to find even the wildest combinations in the goto field: da...@co...,dav...@gm...,david#codepoets.co.uk@postfixadmin.local da...@co...,david#codepoets.co.uk@postfixadmin.local,dav...@gm... dav...@gm...,david#codepoets.co.uk@postfixadmin.local,da...@co... etc. > Does that help? > I hope I could make clear why the "@" character needs to be replaced by "#" for the SQL clause. > (Are you not able to re-open the ticket?) > No. I have no admin right in the Postfix.Admin bug tracker. And you closed the bug for future comments so I am even not able to post any additional text into the bug. > > Thanks > Kind Regards from Switzerland > David. > Stevan Bajić > > > You write that you THINK that the patch is not needed. But I > > KNOW that the patch is needed because without the patch > > vacation is not working on my setup. > > > > Vacation it self is working but as soon it hit's that wrong > > SQL clause which is already in 2.3_rc7 then I get errors. > > Please go ahead and try it yourself. You will see that you > > will get MySQL and PostgreSQL barking about wrongly formated > > SQL clause. > > > > I get errors like this here: > > ug 11 11:24:47 nyx postfix/pipe[15542]: EEA07A3C162: > > to=<viktor#laf...@au...net.local>, > > orig_to=<vi...@la...>, relay=vacation, delay=0.52, > > delays=0.13/0/0/0.38, dsn=5.3.0, status=bounced (Command > > died with status 255: "/usr/bin/perl". Command output: > > DBD::mysql::st execute failed: You have an error in your SQL > > syntax; check the manual that corresponds to your MySQL > > server version for the right syntax to use near '% OR goto > > LIKE %,'vi...@la...' OR goto LIKE > > %,'vi...@la...',%)' at line 1 at > > /var/spool/vacation/vacation-postfixadmin-2.3_rc7.pl line > > 332, <STDIN> line 45. DBD::mysql::st execute failed: You > > have an error in your SQL syntax; check the manual that > > corresponds to your MySQL server version for the right > > syntax to use near '% OR goto LIKE %,'vi...@la...' OR > > goto LIKE %,'vi...@la...',%)' at line 1 at > > /var/spool/vacation/vacation-postfixadmin-2.3_rc7.pl line > > 332, <STDIN> line 45. ) > > > > Jul 26 22:33:02 nyx postfix/pipe[12772]: DFE4BA3C160: > > to=<rog...@me...@autoreply.vunet.local>, > > relay=vacation, delay=0.57, delays=0.12/0.01/0/0.44, > > dsn=5.3.0, status=bounced (Command died with status 255: > > "/usr/bin/perl". Command output: DBD::mysql::st execute > > failed: You have an error in your SQL syntax; check the > > manual that corresponds to your MySQL server version for the > > right syntax to use near '% OR goto LIKE > > %,'rog...@me...' OR goto LIKE > > %,'roger.eckerlin@med' at line 1 at > > /var/spool/vacation/vacation-postfixadmin-2.3_rc7.pl line > > 332, <STDIN> line 40. DBD::mysql::st execute failed: You > > have an error in your SQL syntax; check the manual that > > corresponds to your MySQL server version for the right > > syntax to use near '% OR goto LIKE > > %,'rog...@me...' OR goto LIKE > > %,'roger.eckerlin@med' at line 1 at > > /var/spool/vacation/vacation-postfixadmin-2.3_rc7.pl line > > 332, <STDIN> line 40. ) > > > > So the SQL clause is definitely wrong. > > > > Could you reopen #2835877 so that we can continue the > > discussion there? > > > > > > Kind Regards from Switzerland > > > > Stevan Bajic > > > > -- > > This message has been sent to you, a registered SourceForge.net user, > > by another site user, through the SourceForge.net site. This message > > has been delivered to your SourceForge.net mail alias. You may reply > > to this message using the "Reply" feature of your email client, or > > using the messaging facility of SourceForge.net at: > > https://sourceforge.net/sendmessage.php?touser=2515232 > > > > > - -- > David Goodwin > > [ david at codepoets dot co dot uk ] > [ http://www.codepoets.co.uk ] > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkrds00ACgkQ/ISo3RF5V6awZwCg1Q0dqfEWpgtVUJvmqnxHlpFz > 7pgAmQFT7ScS+5ILeQw4dpa5rTrxEAEs > =lm9J > -----END PGP SIGNATURE----- > |
|
From: Christian B. <pos...@cb...> - 2009-10-21 11:49:33
|
Hello,
Am Dienstag, 20. Oktober 2009 schrieb Stevan Bajić:
> > (Are you not able to re-open the ticket?)
>
> No. I have no admin right in the Postfix.Admin bug tracker. And you
> closed the bug for future comments so I am even not able to post any
> additional text into the bug.
That's a feature (IMHO: mis-feature) that sourceforge introduced some
time ago. There's a checkbox "Close comment posting" that appears when
marking a bug as closed, which is unfortunately checked by default.
I just unchecked it for this specific bugreport.
@David: Please _always_ uncheck the "Close comment posting" box when
marking a bug as closed.
@Stevan: From now on, you have posting permissions on postfixadmin-
devel, but you won't receive replies (unless you are in CC [1]).
Regards,
Christian Boltz
[1] depends on who is sending the answer: David usually CCs the sender,
I usually send the mail only to the mailinglist.
--
> (bezieht sich nicht unbedingt auf Laptops, die Liste ist
> aber etwas ruhig)
Cool, das wäre eigentlich ein Fall für die .signature.
[> Kevin Pfeiffer und Stefan Seyfried in suse-laptop]
|
|
From: Stevan B. <st...@ba...> - 2009-10-20 17:56:33
|
On Tue, 20 Oct 2009 13:55:41 +0100
David Goodwin <da...@co...> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Stevan Bajic wrote:
> > Message body follows:
> >
> > Hallo Gingerdog
> >
>
>
> Hello!
>
Hallo David
> I think there are two bugs - one which is related to the SQL statement -
> which I think is fixed. Are you able to confirm this with what's in trunk??
>
I checked out trunk and see this here:
-------------------
# Recipient has vacation
if ($rv == 1) {
$realemail = $email;
$logger->debug("Found '\$email'\ has vacation active");
} else {
my $vemail = $email;
$vemail =~ s/\@/#/g;
$logger->debug("Looking for alias records that \'$email\' resolves to with vacation turned on");
$query = qq{SELECT goto FROM alias WHERE address=? AND (goto LIKE ? OR goto LIKE ? OR goto LIKE ?)};
$stm = $dbh->prepare($query) or panic_prepare($query);
$stm->execute($email,"$email,%","%,$email","%,$email,%") or panic_execute($query,"address='$email'");
$rv = $stm->rows;
-------------------
This is not going to work. This part here:
-------------------
$stm->execute($email,"$email,%","%,$email","%,$email,%") or panic_execute($query,"address='$email'");
-------------------
Is going to be executed as:
-------------------
SELECT goto FROM alias WHERE address='da...@co...' AND (goto LIKE 'da...@co...,%' OR goto LIKE '%,da...@co...' OR goto LIKE '%,da...@co...,%')
-------------------
And will return a record even if 'da...@co...' does NOT have vacation active. So the patch I posted in the SF Bug Tracker has from my viewpoint still the better SQL clause for finding users in the alias table having vacation active.
Should I go on and modify the vacation script from trunk and send you a patch that fixes the issue?
> The second bug is what I thought I Was replying to - namely there is no
> need to mangle the email address passed into check_recipient() as it's
> already been converted from the vacation goto format
> foo#bar.com@autoreply.whatever to fo...@ba...
>
> Does that help?
>
>
> (Are you not able to re-open the ticket?)
>
>
> Thanks
>
Kind Regards from Switzerland
> David.
>
Stevan Bajic
>
> > You write that you THINK that the patch is not needed. But I
> > KNOW that the patch is needed because without the patch
> > vacation is not working on my setup.
> >
> > Vacation it self is working but as soon it hit's that wrong
> > SQL clause which is already in 2.3_rc7 then I get errors.
> > Please go ahead and try it yourself. You will see that you
> > will get MySQL and PostgreSQL barking about wrongly formated
> > SQL clause.
> >
> > I get errors like this here:
> > ug 11 11:24:47 nyx postfix/pipe[15542]: EEA07A3C162:
> > to=<viktor#laf...@au...net.local>,
> > orig_to=<vi...@la...>, relay=vacation, delay=0.52,
> > delays=0.13/0/0/0.38, dsn=5.3.0, status=bounced (Command
> > died with status 255: "/usr/bin/perl". Command output:
> > DBD::mysql::st execute failed: You have an error in your SQL
> > syntax; check the manual that corresponds to your MySQL
> > server version for the right syntax to use near '% OR goto
> > LIKE %,'vi...@la...' OR goto LIKE
> > %,'vi...@la...',%)' at line 1 at
> > /var/spool/vacation/vacation-postfixadmin-2.3_rc7.pl line
> > 332, <STDIN> line 45. DBD::mysql::st execute failed: You
> > have an error in your SQL syntax; check the manual that
> > corresponds to your MySQL server version for the right
> > syntax to use near '% OR goto LIKE %,'vi...@la...' OR
> > goto LIKE %,'vi...@la...',%)' at line 1 at
> > /var/spool/vacation/vacation-postfixadmin-2.3_rc7.pl line
> > 332, <STDIN> line 45. )
> >
> > Jul 26 22:33:02 nyx postfix/pipe[12772]: DFE4BA3C160:
> > to=<rog...@me...@autoreply.vunet.local>,
> > relay=vacation, delay=0.57, delays=0.12/0.01/0/0.44,
> > dsn=5.3.0, status=bounced (Command died with status 255:
> > "/usr/bin/perl". Command output: DBD::mysql::st execute
> > failed: You have an error in your SQL syntax; check the
> > manual that corresponds to your MySQL server version for the
> > right syntax to use near '% OR goto LIKE
> > %,'rog...@me...' OR goto LIKE
> > %,'roger.eckerlin@med' at line 1 at
> > /var/spool/vacation/vacation-postfixadmin-2.3_rc7.pl line
> > 332, <STDIN> line 40. DBD::mysql::st execute failed: You
> > have an error in your SQL syntax; check the manual that
> > corresponds to your MySQL server version for the right
> > syntax to use near '% OR goto LIKE
> > %,'rog...@me...' OR goto LIKE
> > %,'roger.eckerlin@med' at line 1 at
> > /var/spool/vacation/vacation-postfixadmin-2.3_rc7.pl line
> > 332, <STDIN> line 40. )
> >
> > So the SQL clause is definitely wrong.
> >
> > Could you reopen #2835877 so that we can continue the
> > discussion there?
> >
> >
> > Kind Regards from Switzerland
> >
> > Stevan Bajic
> >
> > --
> > This message has been sent to you, a registered SourceForge.net user,
> > by another site user, through the SourceForge.net site. This message
> > has been delivered to your SourceForge.net mail alias. You may reply
> > to this message using the "Reply" feature of your email client, or
> > using the messaging facility of SourceForge.net at:
> > https://sourceforge.net/sendmessage.php?touser=2515232
> >
>
>
> - --
> David Goodwin
>
> [ david at codepoets dot co dot uk ]
> [ http://www.codepoets.co.uk ]
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkrds00ACgkQ/ISo3RF5V6awZwCg1Q0dqfEWpgtVUJvmqnxHlpFz
> 7pgAmQFT7ScS+5ILeQw4dpa5rTrxEAEs
> =lm9J
> -----END PGP SIGNATURE-----
>
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X