Your message dated Fri, 3 Jul 2009 16:19:30 +0200
with message-id <[email protected]>
and subject line [AMaViS-user] amavisd-new 2.6.2-2 failure: PRESERVING EVIDENCE
in /var/lib/amavis/tmp/amavis-20090524T224325-13688 (fwd)
has caused the Debian Bug report #530614,
regarding [AMaViS-user] amavisd-new 2.6.2-2 failure: PRESERVING EVIDENCE in
/var/lib/amavis/tmp/amavis-20090524T224325-13688 (fwd)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
530614: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530614
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: amavsid-new
Version: 2.6.2-2
I am running amavsid-new on Debian Testing and spotted this in the logs
the other day:
May 25 10:32:37 p34 amavis[13688]: (13688-06) (!)SEND via SMTP:
[email protected] -> <[email protected]>,
[email protected]
401 4.1.7 TempFailed, id=13688-06, from MTA([127.0.0.1]:10025):
401 4.1.7 Bad sender address syntax
Looks like this bug, fixed in 2.6.3:
amavisd-new-2.6.3 release notes
BUG FIXES
- if $mailfrom_notify_admin was not specified in a configuration file but
defaulted to an e-mail address in $hdrfrom_notify_admin, the following
was reported (due to missing angle brackets) on an attempt to submit
a notification:
(!)SEND via SMTP: [email protected] -> <[email protected]>...
501 5.1.7 Bad sender address syntax
(!)FAILED to notify admin: 501 5.1.7 Failed, id=40690-23,
from MTA([::1]:10027): 501 5.1.7 Bad sender address syntax
Notification was not sent, the rest of the processing was unaffected;
reported by Peter Pechnik, Thomas Mueller, and Stefan Förster;
A workaround is to explictly specify the $mailfrom_notify_admin addess.
Mark
Thanks Mark, I've implemented the workaround for now until the newer/upstream
release makes it to Debian Testing.
Justin.
--- End Message ---
--- Begin Message ---
Hi,
this has been fixed with 1:2.6.3-1, for some unknown reason I missed to close
this
bugs.
Thanks
Alex
--- End Message ---
