Mailing List Archive: exim: users

Help needed 4.63 to 4.69 upgrade issue

Index | Next | Previous | View Threaded

georgek at netwrx1

Jun 16, 2008, 1:11 PM

Post #1 of 7 (1050 views)
Permalink

Help needed 4.63 to 4.69 upgrade issue

Hello:

I'm in the process of helping a client upgrade their exim installation
from 4.63 to 4.69. The compile of 4.69 went fine, however, there seems
to be some issue in the configuration file with the syntax or format
of the ACL rules etc. that has changed from 4.63 to 4.69 that causes
basically all of them to fail. I'm totally foreign to the syntax of
the rules and how they are constructed and the individual that built
the 4.63 config is no longer here. They are running under red hat
enterprise linux with mysql.

Anyone that can provide some assistance or guidance would be greatly
appreciated. I can provide errors and rules/configurations off list on
request (clients choice).

George

--
===[George R. Kasica]=== +1 262 677 0766
President +1 206 374 6482 FAX
Netwrx Consulting Inc. Jackson, WI USA
http://www.netwrx1.com
georgek [at] netwrx1
ICQ #12862186

--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

odhiambo at gmail

Jun 16, 2008, 1:27 PM

Post #2 of 7 (999 views)
Permalink

Re: Help needed 4.63 to 4.69 upgrade issue [In reply to]

On Mon, Jun 16, 2008 at 11:11 PM, George R. Kasica <georgek [at] netwrx1> wrote:
> Hello:
>
> I'm in the process of helping a client upgrade their exim installation
> from 4.63 to 4.69. The compile of 4.69 went fine, however, there seems
> to be some issue in the configuration file with the syntax or format
> of the ACL rules etc. that has changed from 4.63 to 4.69 that causes
> basically all of them to fail. I'm totally foreign to the syntax of
> the rules and how they are constructed and the individual that built
> the 4.63 config is no longer here. They are running under red hat
> enterprise linux with mysql.
>
> Anyone that can provide some assistance or guidance would be greatly
> appreciated. I can provide errors and rules/configurations off list on
> request (clients choice).
>

What errors are you seeing?

AFAIK, there were no changes btn those two versions that anything!
Somehow, you might have missed something during your compile.

--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

"Oh My God! They killed init! You Bastards!"
--from a /. post

--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

peter at bowyer

Jun 16, 2008, 2:05 PM

Post #3 of 7 (1000 views)
Permalink

Re: Help needed 4.63 to 4.69 upgrade issue [In reply to]

2008/6/16 George R. Kasica <georgek [at] netwrx1>:
> Hello:
>
> I'm in the process of helping a client upgrade their exim installation
> from 4.63 to 4.69. The compile of 4.69 went fine, however, there seems
> to be some issue in the configuration file with the syntax or format
> of the ACL rules etc. that has changed from 4.63 to 4.69 that causes
> basically all of them to fail.

What you're interpreting as all of them failing is likely to be Exim
complaining that your config file references a feature (router,
transport or lookup) that hasn't been complied in to the new instance
of the binary. There's no inherent incompatability.

Post the actual errors for more help.

Peter

--
Peter Bowyer
Email: peter [at] bowyer
Follow me on Twitter: twitter.com/peeebeee

--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

odhiambo at gmail

Jun 16, 2008, 10:05 PM

Post #4 of 7 (982 views)
Permalink

Re: Help needed 4.63 to 4.69 upgrade issue [In reply to]

On Tue, Jun 17, 2008 at 12:05 AM, Peter Bowyer <peter [at] bowyer> wrote:
> 2008/6/16 George R. Kasica <georgek [at] netwrx1>:
>> Hello:
>>
>> I'm in the process of helping a client upgrade their exim installation
>> from 4.63 to 4.69. The compile of 4.69 went fine, however, there seems
>> to be some issue in the configuration file with the syntax or format
>> of the ACL rules etc. that has changed from 4.63 to 4.69 that causes
>> basically all of them to fail.

Please post the output of this command:

`exim -bV`

--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

"Oh My God! They killed init! You Bastards!"
--from a /. post

--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

georgek at netwrx1

Jun 17, 2008, 8:31 AM

Post #5 of 7 (969 views)
Permalink

Re: Help needed 4.63 to 4.69 upgrade issue [In reply to]

>On Tue, 17 Jun 2008 08:05:08 +0300, you wrote:

>On Tue, Jun 17, 2008 at 12:05 AM, Peter Bowyer <peter [at] bowyer> wrote:
>> 2008/6/16 George R. Kasica <georgek [at] netwrx1>:
>>> Hello:
>>>
>>> I'm in the process of helping a client upgrade their exim installation
>>> from 4.63 to 4.69. The compile of 4.69 went fine, however, there seems
>>> to be some issue in the configuration file with the syntax or format
>>> of the ACL rules etc. that has changed from 4.63 to 4.69 that causes
>>> basically all of them to fail.
>
>Please post the output of this command:
>
>`exim -bV`
[root [at] shem ~]# cd /usr/local/exim-4.69/bin/
[root [at] shem bin]# ./exim -bV
Exim version 4.69 #1 built 16-Jun-2008 12:01:17
Copyright (c) University of Cambridge 2006
Berkeley DB: Sleepycat Software: Berkeley DB 4.2.52: (June 6, 2007)
Support for: crypteq iconv() OpenSSL Content_Scanning
Lookups: lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmnz
mysql
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir autoreply pipe smtp
Fixed never_users: 0
Size of off_t: 8
Configuration file is /etc/exim/configure
--
George, Ginger/The Beast Kasica(8/1/88-3/19/01, 1/17/02- ), Rosie(9/1/07- ), Merlin(2/10/08- ), MR. Tibbs(8/1/90-5/24/06), Nazarene(6/1/99-1/28/08)
Jackson, WI USA
georgek [at] netwrx1
http://www.netwrx1.com/georgek
ICQ #12862186

("`-''-/").___..--''"`-._
`6_ 6 ) `-. ( ).`-.__.`)
(_Y_.)' ._ ) `._ `. ``-..-'
_..`--'_..-_/ /--'_.' ,'
(il),-'' (li),' ((!.-'

--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

georgek at netwrx1

Jun 17, 2008, 8:31 AM

Post #6 of 7 (968 views)
Permalink

Re: Help needed 4.63 to 4.69 upgrade issue [In reply to]

>On Mon, 16 Jun 2008 22:05:07 +0100, you wrote:

>2008/6/16 George R. Kasica <georgek [at] netwrx1>:
>> Hello:
>>
>> I'm in the process of helping a client upgrade their exim installation
>> from 4.63 to 4.69. The compile of 4.69 went fine, however, there seems
>> to be some issue in the configuration file with the syntax or format
>> of the ACL rules etc. that has changed from 4.63 to 4.69 that causes
>> basically all of them to fail.
>
>What you're interpreting as all of them failing is likely to be Exim
>complaining that your config file references a feature (router,
>transport or lookup) that hasn't been complied in to the new instance
>of the binary. There's no inherent incompatability.
>
>Post the actual errors for more help.
>
2008-06-16 12:05:08 1K8I8N-0002Ig-TA failed to expand condition "${if
and { {eq{$h_X-Spam-Flag:}{YES} } {= {${lookup mysql{SELECT filterspam
FROM vpopmail WHERE pw_name='${local_part}' AND pw_domain =
'${domain}'}} }{1} }} {yes}{no}}" for mysql_spam router: integer
expected but " " found inside "and{...}" condition

2008-06-16 12:06:26 1K8I9l-0002Xw-MC failed to expand condition "${if
and { {eq{$h_X-Spam-Flag:}{YES} } {= {${lookup mysql{SELECT filterspam
FROM vpopmail WHERE pw_name='${local_part}' AND pw_domain =
'${domain}'}} }{1} }} {yes}{no}}" for mysql_spam router: integer
expected but " " found inside "and{...}" condition

2008-06-16 12:06:28 1K7HQA-0007XJ-FX failed to expand condition "${if
and { {eq{$h_X-Spam-Flag:}{YES} } {= {${lookup mysql{SELECT filterspam
FROM vpopmail WHERE pw_name='${local_part}' AND pw_domain =
'${domain}'}} }{1} }} {yes}{no}}" for mysql_spam router: integer
expected but " " found inside "and{...}" condition

2008-06-16 12:06:37 1K8I9w-0002Xz-AH failed to expand condition "${if
and { {eq{$h_X-Spam-Flag:}{YES} } {= {${lookup mysql{SELECT filterspam
FROM vpopmail WHERE pw_name='${local_part}' AND pw_domain =
'${domain}'}} }{1} }} {yes}{no}}" for mysql_spam router: integer
expected but " " found inside "and{...}" condition

2008-06-16 12:06:43 1K7AQK-0003r4-Vv failed to expand condition "${if
and { {eq{$h_X-Spam-Flag:}{YES} } {= {${lookup mysql{SELECT filterspam
FROM vpopmail WHERE pw_name='${local_part}' AND pw_domain =
'${domain}'}} }{1} }} {yes}{no}}" for mysql_spam router: integer
expected but " " found inside "and{...}" condition

2008-06-16 12:06:43 1K7FkK-0003Qn-W9 failed to expand condition "${if
and { {eq{$h_X-Spam-Flag:}{YES} } {= {${lookup mysql{SELECT filterspam
FROM vpopmail WHERE pw_name='${local_part}' AND pw_domain =
'${domain}'}} }{1} }} {yes}{no}}" for mysql_spam router: integer
expected but " " found inside "and{...}" condition

2008-06-16 12:06:43 1K6uhF-00049A-Qv failed to expand condition "${if
and { {eq{$h_X-Spam-Flag:}{YES} } {= {${lookup mysql{SELECT filterspam
FROM vpopmail WHERE pw_name='${local_part}' AND pw_domain =
'${domain}'}} }{1} }} {yes}{no}}" for mysql_spam router: integer
expected but " " found inside "and{...}" condition

2008-06-16 12:06:46 1K77jF-0001W6-Pm failed to expand condition "${if
and { {eq{$h_X-Spam-Flag:}{YES} } {= {${lookup mysql{SELECT filterspam
FROM vpopmail WHERE pw_name='${local_part}' AND pw_domain =
'${domain}'}} }{1} }} {yes}{no}}" for mysql_spam router: integer
expected but " " found inside "and{...}" condition

2008-06-16 12:06:49 1K8IAA-0002cZ-2s failed to expand condition "${if
and { {eq{$h_X-Spam-Flag:}{YES} } {= {${lookup mysql{SELECT filterspam
FROM vpopmail WHERE pw_name='${local_part}' AND pw_domain =
'${domain}'}} }{1} }} {yes}{no}}" for mysql_spam router: integer
expected but " " found inside "and{...}" condition

2008-06-16 12:06:58 1K7DaF-00006e-AM failed to expand condition "${if
and { {eq{$h_X-Spam-Flag:}{YES} } {= {${lookup mysql{SELECT filterspam
FROM vpopmail WHERE pw_name='${local_part}' AND pw_domain =
'${domain}'}} }{1} }} {yes}{no}}" for mysql_spam router: integer
expected but " " found inside "and{...}" condition

2008-06-16 12:07:19 1K8I8p-0002OC-8q spam acl condition: error reading
from spamd socket: Connection timed out

2008-06-16 12:07:43 1K8IB1-0002oY-Aa failed to expand condition "${if
and { {eq{$h_X-Spam-Flag:}{YES} } {= {${lookup mysql{SELECT filterspam
FROM vpopmail WHERE pw_name='${local_part}' AND pw_domain =
'${domain}'}} }{1} }} {yes}{no}}" for mysql_spam router: integer
expected but " " found inside "and{...}" condition

2008-06-16 12:08:10 1K8IBX-0002sl-Kx failed to expand condition "${if
and { {eq{$h_X-Spam-Flag:}{YES} } {= {${lookup mysql{SELECT filterspam
FROM vpopmail WHERE pw_name='${local_part}' AND pw_domain =
'${domain}'}} }{1} }} {yes}{no}}" for mysql_spam router: integer
expected but " " found inside "and{...}" condition

2008-06-16 12:08:20 1K8IBb-0002tu-3U failed to expand condition "${if
and { {eq{$h_X-Spam-Flag:}{YES} } {= {${lookup mysql{SELECT filterspam
FROM vpopmail WHERE pw_name='${local_part}' AND pw_domain =
'${domain}'}} }{1} }} {yes}{no}}" for mysql_spam router: integer
expected but " " found inside "and{...}" condition

2008-06-16 12:08:32 1K8IA2-0002bl-FJ spam acl condition: error reading
from spamd socket: Connection timed out

2008-06-16 12:08:35 1K8IBr-0002wk-TE failed to expand condition "${if
and { {eq{$h_X-Spam-Flag:}{YES} } {= {${lookup mysql{SELECT filterspam
FROM vpopmail WHERE pw_name='${local_part}' AND pw_domain =
'${domain}'}} }{1} }} {yes}{no}}" for mysql_spam router: integer
expected but " " found inside "and{...}" condition

2008-06-16 12:09:31 1K8ICn-00035W-U2 failed to expand condition "${if
and { {eq{$h_X-Spam-Flag:}{YES} } {= {${lookup mysql{SELECT filterspam
FROM vpopmail WHERE pw_name='${local_part}' AND pw_domain =
'${domain}'}} }{1} }} {yes}{no}}" for mysql_spam router: integer
expected but " " found inside "and{...}" condition

--
George, Ginger/The Beast Kasica(8/1/88-3/19/01, 1/17/02- ), Rosie(9/1/07- ), Merlin(2/10/08- ), MR. Tibbs(8/1/90-5/24/06), Nazarene(6/1/99-1/28/08)
Jackson, WI USA
georgek [at] netwrx1
http://www.netwrx1.com/georgek
ICQ #12862186

("`-''-/").___..--''"`-._
`6_ 6 ) `-. ( ).`-.__.`)
(_Y_.)' ._ ) `._ `. ``-..-'
_..`--'_..-_/ /--'_.' ,'
(il),-'' (li),' ((!.-'

--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

exim-users at spodhuis

Jun 17, 2008, 4:02 PM

Post #7 of 7 (986 views)
Permalink

Re: Help needed 4.63 to 4.69 upgrade issue [In reply to]

On 2008-06-17 at 10:31 -0500, George R. Kasica wrote:
> >On Mon, 16 Jun 2008 22:05:07 +0100, you wrote:
>
> >2008/6/16 George R. Kasica <georgek [at] netwrx1>:
> >> I'm in the process of helping a client upgrade their exim installation
> >> from 4.63 to 4.69. The compile of 4.69 went fine, however, there seems
> >> to be some issue in the configuration file with the syntax or format
> >> of the ACL rules etc. that has changed from 4.63 to 4.69 that causes
> >> basically all of them to fail.
> >
> >What you're interpreting as all of them failing is likely to be Exim
> >complaining that your config file references a feature (router,
> >transport or lookup) that hasn't been complied in to the new instance
> >of the binary. There's no inherent incompatability.
> >
> >Post the actual errors for more help.
> >
> 2008-06-16 12:05:08 1K8I8N-0002Ig-TA failed to expand condition "${if
> and { {eq{$h_X-Spam-Flag:}{YES} } {= {${lookup mysql{SELECT filterspam
> FROM vpopmail WHERE pw_name='${local_part}' AND pw_domain =
> '${domain}'}} }{1} }} {yes}{no}}" for mysql_spam router: integer
> expected but " " found inside "and{...}" condition

In Exim 4.64, checks for numeric overflow were added and the stronger
numeric enforcement broke some config; all the issues were believed
fixed, including this fix in Exim 4.66:

PH/01 [...]
(i) An empty string was always treated as zero by the numeric comparison
operators. This behaviour has been restored.

This is very literal in that the string must be empty. I guess that
before the problematic (but very necessary) patch, it let you use
whitespace in there too.

So your MySQL query is returning a whitespace and expecting this to be
treated as 0.

What values can the query return? Does it return the literal string "1"
when it matches? Your fastest fix, in that case, might just be to
change '=' (numeric equality) to 'eq' (string equality).

-Phil

--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads