Date: Tue, 24 Nov 2015 16:21:50 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 204787] [patch] security/amavisd-milter: fix incompatibility with amavisd-new (!) Message-ID: <bug-204787-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204787 Bug ID: 204787 Summary: [patch] security/amavisd-milter: fix incompatibility with amavisd-new (!) Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Keywords: patch Severity: Affects Only Me Priority: --- Component: Ports Framework Assignee: portmgr@FreeBSD.org Reporter: dgeo@centrale-marseille.fr CC: freebsd-ports-bugs@FreeBSD.org Keywords: patch Created attachment 163485 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=163485&action=edit svn diff security/amavisd-milter As I said to maintainer by private mail some months ago without response: On two different mail servers, amavisd-milter gives me: postfix/cleanup[10153]: 060685525: milter-reject: END-OF-MESSAGE from mel0.serv.int[10.3.0.88]: 4.5.0 Failure: Suspicious temporary directory name '/var/run/amavis/tmp/afcokTMBJlIs' This line comes from amavisd l.21082, where tempdir is checked against amavis's TEMPBASE and MYHOME (by default in /var/amavis). amavisd-milter use /var/run/amavis/tmp by default (--with-working-dir=tmp) => I don't understand how it can work ? (by overriding amavis's TEMPBASE ?) Attached patch fixes this by using ${AMAVISDIR}/tmp as working dir I'm also using an 'inet' socket (maybe that changes something ?). I also add a simple test in rc script to NOT TRY chmod'ing socket if socket is not on filesystem. 'poudriere testport'ed, 'port test'ed, production-tested since 2015-05. not fixing portlint here (I may propose a patch later after further testing) -- You are receiving this mail because: You are on the CC list for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-204787-13>