I'm running amavisd-new 2.3.3 and it now refuses connections. It is up
and running according to ps but postfix cannot talk to it. The
postgres-db it uses is also up and running. Any ideas where to start
looking?
HM
--
We've been plagued by a very large (1.7 GB) bounce lately and wondered
if newer amavisd-news are smarter about this:
Basically what happens is: postfix hands mail over to amavis who hands
it over to clamav. Clamav spends so much time attempting to scan the
file that postfix times out, gives up
On 6/27/07, Hanne Moa [EMAIL PROTECTED] wrote:
On 6/27/07, Mark Martinec [EMAIL PROTECTED] wrote:
CREATE TEMPORARY TABLE unused AS (
SELECT id FROM maddr LEFT JOIN (
SELECT sid AS id, 1 AS f FROM msgs UNION ALL
SELECT rid AS id, 1 AS f FROM msgrcpt)
AS u USING(id) WHERE u.f
On 6/15/07, Mark Martinec [EMAIL PROTECTED] wrote:
The README.sql-pg in amavisd-new distribution suggests
the following SQL clauses to purge old records from a database:
DELETE FROM msgs WHERE time_iso now() - INTERVAL '3 weeks';
The script that does this on my amavis-setup had a convenient
I've been trying to change the sql backend from mysql to postgresql
(8.1), the latest hindrance leaves the following in mail.log:
Feb 21 11:13:47 censored amavis[16546]: (16546-01-5) WARN
save_info_preliminary: Insecure dependency in parameter 1 of
DBI::db=HASH(0xa678130)-prepare method call
I'm working on upgrading to spamassassin 3.1.7 and amavisd-new 2.4.2
(what's in backports, basically) and one mail (spam) fail with the
following log:
There are 19 image attachments, several with the same filename, here's
an example from the log:
Jan 19 14:36:43 liksom3 amavis[19850]: (19850-07)
On 10/22/06, techlist06 [EMAIL PROTECTED] wrote:
I am already tagging potential spam. Is there a relatively easy way I can
tag messages with the image spam, specifically the gif/animated gif's as
spam? I considered blocking them altogether, but figured that might be too
drastic. I'd like to
On 10/17/06, Ralf Hildebrandt [EMAIL PROTECTED] wrote:
* Ralf Hildebrandt [EMAIL PROTECTED]:
But why? How can I find out why SA takes up to 45s to process a mail:
Found it:
% amavisd -d dns,uri,uridnsbl debug-sa log 21
and I got:
# grep took log|sort -k 8 -n | tail
[12965]
On 10/13/06, Andrea Bencini [EMAIL PROTECTED] wrote:
I install postfix-2.2.8, amavisd-new-2.4.1 and spamassassin-3.1.3.
I tested $final_virus_destiny with virus Eicar-Test-Signature.
I tested $final_banned_destiny with my file tst.exe.
Now I would like test $final_bad_header_destiny.
How
On 10/9/06, Kai Risku [EMAIL PROTECTED] wrote:
The problematic emails have no problem at all if I manually scan them
with spamassassin (does not even take a long time), but then amavisd_new
chews on them, it chews for an indefinite amount of time and then gives
up (actually gets killed after
On 9/18/06, Num ber [EMAIL PROTECTED] wrote:
I'm using amavisd with clamav and SA for postfix MTA.
I would like to have some user pref. like : WhiteListe,Blackliste,Spam
score..
Because i use amavisd, it's not possibl to use sql pref with SA, i think is
possible with Amavisd.sql but, i would
11 matches
Mail list logo
