Bug 231250 - possible data type bug in security/amavisd-new
Summary: possible data type bug in security/amavisd-new
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Florian Smeets
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-09 02:22 UTC by dnewman
Modified: 2019-01-18 05:46 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (flo)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dnewman 2018-09-09 02:22:43 UTC
FreeBSD-11.2-p2, amavisd-new-2.11.0_3,1, p5-DBD-mysql-4.046 (also 4.037), mysql57-server-5.7.23_1

When using p5-DBD-mysql releases after 4.037, amavisd-new creates false positives and erroneously adds a "tagged_above=0" label to message headers.

This is due to a change in p5-DBD-mysql-4.038 and later releases so that p5-DBD-mysql "now returns mysql doubles as perl doubles and mysql floats as perl floats (and not as a string anymore)." 

Due to this change in data types, the p5-DBD-mysql client obtains erroneous '0' results from queries. The MySQL client obtains the correct values.

This thread describes the problem in more detail and includes a link with configuration files and debug logs:

https://lists.amavis.org/pipermail/amavis-users/2018-August/005399.html

The changelog for p5-DBD-mysql describes the changes instituted with its 4.038 release:

https://fastapi.metacpan.org/source/CAPTTOFU/DBD-mysql-4.046/Changes

Please let me know if you need further info.
Comment 1 Martin Matuska freebsd_committer 2019-01-05 11:39:41 UTC
I am experiencing the same problem but with all versions higher than 4.0.38. This is why I keep a patched private port for now.
Comment 2 dnewman 2019-01-18 05:46:26 UTC
This issue is still present in p5-DBD-mysql-4.050, released this week. Other amavisd users report seeing the same issue.