Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
found some warning on maillog
3 views
Skip to first unread message
Watthanachai Kekhua
Apr 11, 2012, 12:35:45 AM4/11/12
to
Dear Amavis team,
Today we found some warning below ,
amavis[67002]: (67002-03-2) _WARN: Argument "undef" isn't numeric in addition (+) at (eval 123) line 307.
My amavisd version = amavisd-new-2.7.0
OS = FreeBSD 8.2 amd 64 bit
We try to see this error on google but could not found any information ,
could you try to help us for this error ?
Thank you very much, we still looking for your answer .
Please do not hesitate to contact us , If you have any questions .
Best Regards.
################################
# Watthanachai KEKHUA (Golf)
# SYSTEM ENGINEER
# Tel: 02-2367227 Ext. 3155
# Direct Line Tel: 02-2366395
# NTT Communications (Thailand) Co., Ltd.
#################################
Mark Martinec
Apr 11, 2012, 6:19:18 AM4/11/12
to
Watthanachai Kekhua,
> Today we found some warning below,
> amavis[67002]: (67002-03-2) _WARN: Argument "undef" isn't numeric
> in addition (+) at (eval 123) line 307.
>
> My amavisd version = amavisd-new-2.7.0
> OS = FreeBSD 8.2 amd 64 bit
Are you using LDAP lookups? This looks like it is coming
from a LDAP lookup on an attribute which is supposed to
be numeric, but contains a string "undef".
If an undefined value was really intended, it should be
represented in LDAP (or in SQL) as a NULL, not some string.
Mark
> Today we found some warning below,
> amavis[67002]: (67002-03-2) _WARN: Argument "undef" isn't numeric
> in addition (+) at (eval 123) line 307.
>
> My amavisd version = amavisd-new-2.7.0
> OS = FreeBSD 8.2 amd 64 bit
from a LDAP lookup on an attribute which is supposed to
be numeric, but contains a string "undef".
If an undefined value was really intended, it should be
represented in LDAP (or in SQL) as a NULL, not some string.
Mark
Watthanachai Kekhua
Apr 11, 2012, 7:39:49 AM4/11/12
to
Dear Mark,
Thank you very much for your message and guide ,
I already checked and see some users have "amavisSpamTagLevel = undef" in ldap data.
If I input some value into this config , the warning will fix . Right ?
Please do not hesitate to contact us , If you have any questions .
Best Regards.
################################
# Watthanachai KEKHUA (Golf)
# SYSTEM ENGINEER
# Tel: 02-2367227 Ext. 3155
# Direct Line Tel: 02-2366395
# NTT Communications (Thailand) Co., Ltd.
#################################
Thank you very much for your message and guide ,
I already checked and see some users have "amavisSpamTagLevel = undef" in ldap data.
If I input some value into this config , the warning will fix . Right ?
Please do not hesitate to contact us , If you have any questions .
Best Regards.
################################
# Watthanachai KEKHUA (Golf)
# SYSTEM ENGINEER
# Tel: 02-2367227 Ext. 3155
# Direct Line Tel: 02-2366395
# NTT Communications (Thailand) Co., Ltd.
#################################
Mark Martinec
Apr 11, 2012, 1:15:43 PM4/11/12
to
>> If an undefined value was really intended, it should be represented
>> in LDAP (or in SQL) as a NULL, not some string.
>> in LDAP (or in SQL) as a NULL, not some string.
> Thank you very much for your message and guide,
> I already checked and see some users have "amavisSpamTagLevel = undef"
> in ldap data.
>
> If I input some value into this config, the warning will fix. Right ?
Right.
> I already checked and see some users have "amavisSpamTagLevel = undef"
> in ldap data.
>
> If I input some value into this config, the warning will fix. Right ?
Either put a numerical value there, or if you'd like for a LDAP
lookup on such attribute to fall back to a static default,
put a NULL attribute value there.
Mark
0 new messages