For the archive:
TROUBLE in check_mail: spam_scan FAILED: panic: swash_fetch at
/etc/mail/spamassassin/70_sare_specific.cf, rule SARE_SPEC_SHORTQ, line
1, GEN6 line 1706.
The problem turned out to be missing perl library directory 'unicore'
in chroot jail. The need for it is documented in
Peter,
TROUBLE in check_mail: spam_scan FAILED: panic: swash_fetch at
/etc/mail/spamassassin/70_sare_specific.cf, rule SARE_SPEC_SHORTQ, line 1,
GEN6 line 1706.
Search the amavisd-new web page for 'swash_fetch'.
It is consequence of Perl bugs when handling UTF-8 characters.
What version of
Peter wrote:
False alarm. I wasn't aware I needed outgoing port 80 open for RDJ.
Strange I never got these errors before. Does it only use curl when it
detects (how?) an update is required?
Nope.. it always needs to go out over port 80. The check for update is done
using HTTP
From: Matt Kettler [EMAIL PROTECTED]
Peter wrote:
False alarm. I wasn't aware I needed outgoing port 80 open for RDJ.
Strange I never got these errors before. Does it only use curl when it
detects (how?) an update is required?
Nope.. it always needs to go out over port 80. The check for
From: Matt Kettler [EMAIL PROTECTED]
jdow wrote:
From: Matt Kettler [EMAIL PROTECTED]
Peter wrote:
False alarm. I wasn't aware I needed outgoing port 80 open for RDJ.
Strange I never got these errors before. Does it only use curl when it
detects (how?) an update is required?
Nope.. it
--- Matt Kettler [EMAIL PROTECTED] wrote:
Peter wrote:
False alarm. I wasn't aware I needed outgoing port 80 open for RDJ.
Strange I never got these errors before. Does it only use curl when
it
detects (how?) an update is required?
Nope.. it always needs to go out over port 80.
--- Matt Kettler [EMAIL PROTECTED] wrote:
Peter wrote:
False alarm. I wasn't aware I needed outgoing port 80 open for RDJ.
Strange I never got these errors before. Does it only use curl when
it
detects (how?) an update is required?
Nope.. it always needs to go out over port 80.
Hello Peter,
Wednesday, January 11, 2006, 7:31:39 PM, you wrote:
P Looks like I had two problems simultaneously. The update issue was not
P causing the error it seems. The real problem I'm encountering appears to
P concern a particular SARE rule. I am running amavisd-new with SA and this
P is
--- Robert Menschel [EMAIL PROTECTED] wrote:
Hello Peter,
Wednesday, January 11, 2006, 7:31:39 PM, you wrote:
P Looks like I had two problems simultaneously. The update issue was
not
P causing the error it seems. The real problem I'm encountering
appears to
P concern a particular
