Bug 129636 - amavisd-new-2.4.0 error in amavisd.conf
Bug#: 129636 Product:  Gentoo Linux Version: 2006.0 Platform: All
OS/Version: Linux Status: RESOLVED Severity: normal Priority: P2
Resolution: FIXED Assigned To: antivirus@gentoo.org Reported By: dfgweb@dfg.homedns.org
Component: Applications
URL: 
Summary: amavisd-new-2.4.0 error in amavisd.conf
Keywords:  
Status Whiteboard: 
Opened: 2006-04-11 14:30 0000
Description:   Opened: 2006-04-11 14:30 0000
The new gentoo config file patch have an error in QUARANTINEDIR declaration.

This result in error in logs when email need to be quarantined:
--------- mail.err ----------
Apr 10 12:02:16 serveur amavis[32127]: (32127-16) (!!) TROUBLE in check_mail:
quar+notif FAILED: temporarily unable to quarantine: 451 4.5.0 Local
delivery(1) to $MYHOME/quarantine failed: Can't create file $MYHOME/quarantine:
No such file
or directory at (eval 55) line 147., id=32127-16 at /usr/sbin/amavisd line
8379.
-----------------------------

Part of the amavisd-new-2.4-amavisd.conf-gentoo.patch file with error:
------ part of patch --------
@@ -679,7 +704,7 @@
 #   or a directory (no trailing slash)
 #   (the default value is undef, meaning no quarantine)
 #
-$QUARANTINEDIR = '/var/virusmails';
+$QUARANTINEDIR = '$MYHOME/quarantine';

 #$quarantine_subdir_levels = 1;  # add level of subdirs to disperse quarantine
-----------------------------

The declaration
$QUARANTINEDIR = '$MYHOME/quarantine';
must be changed to 
$QUARANTINEDIR = "$MYHOME/quarantine";

A double quoted string must be used to allow $MYHOME evaluation.
No more error after this change.

David

------- Comment #1 From Andrej Kacian (RETIRED) 2006-04-11 16:56:29 0000 -------
I'll fix this right after I'll get back from work (can't commit from here),
unless someone else beats me to it.

Sorry about this inconvenience.

------- Comment #2 From Andrej Kacian (RETIRED) 2006-04-11 22:36:28 0000 -------
Fixed in CVS. Thanks for the report!

------- Comment #3 From Tuan Van (RETIRED) 2006-04-12 07:53:46 0000 -------
*** Bug 129678 has been marked as a duplicate of this bug. ***