amavisd-new 2.2.1 and amavisd-maia.patch

[segr@…]

I believe I may have stumbled across a problem with the amavisd-maia patch with 2.2.1 of amavis. When I went to restart amavisd-new on my freebsd system.. I got the following:

luna# /usr/local/etc/rc.d/amavisd.sh start<BR>
Starting amavisd.
syntax error at /usr/local/sbin/amavisd line 8559, near ");"
syntax error at /usr/local/sbin/amavisd line 8560, near ") )"
syntax error at /usr/local/sbin/amavisd line 8844, near "if"
Global symbol "$maia_user_id" requires explicit package name at /usr/local/sbin/amavisd line 8844.
Global symbol "$maia_user_id" requires explicit package name at /usr/local/sbin/amavisd line 8845.
Global symbol "$mail_type" requires explicit package name at /usr/local/sbin/amavisd line 8845.
syntax error at /usr/local/sbin/amavisd line 8847, near ")) "
Execution of /usr/local/sbin/amavisd aborted due to compilation errors.
No entry "log_level" in policy bank "" at /usr/local/sbin/amavisd line 1361
END failed--call queue aborted at /usr/local/sbin/amavisd line 8854.
luna# 

is the patch file 2.2.1 compatible, and if not, can it be?

[rjl]

There is no patch for amavisd-new 2.2.1 yet (coming very soon, however). A patch for 2.2.0 is available, however. Fetch the "amavisd-maia" file from the svn repository (or get it here)--it is already pre-patched for amavisd-new 2.2.0, and just needs to be renamed to "amavisd". Your amavisd.conf file from 2.2.1 will work with this, as long as you comment-out the lines that define "$pax" and "$ripole".

[segr@…]

I tried as suggested and get the following now:

luna# /usr/local/etc/rc.d/amavisd.sh start
Starting amavisd.
Problem in the Amavis::Cache code:  at /usr/local/sbin/amavisd line 10587.
Mar  6 18:13:44 luna.integer8.net [61475]: at the END handler: invoking DESTROY methods
luna#

NOTE: I also changed the amavisd.conf path in the file to /usr/local/etc/amavisd.conf since that's where the freebsd ports put it.

[dmorton]

That error has appeared elsewhere when the file was transported from a windows box to a unix box, and the line endings were mangled. Make sure you are downloading it correctly... If you use ascii to download it to windows, make sure you use ascii mode to transport it back to the freebsd box, or else use binary in all downloads.

[segr@…]

Thanks, that was in the problem indeed. I used the following command line to solve my problem:

tr -d "\015" < inputfile > outputfile

Thanks, stephane.