On 7/30/07, Sergio Restrepo [EMAIL PROTECTED] wrote:
Hello,
I am working with mailzu and I have the following lines in the amavis config
file:
## Policy
$interface_policy{'9998'} = 'AM.PDP';
$policy_bank{'AM.PDP'} = {
protocol = 'AM.PDP',
#inet_acl = [qw( 127.0.0.1 [::1]
On 7/5/07, Michael Scheidell [EMAIL PROTECTED] wrote:
In SQL based quarantine, if I run a script to delete quarantined email
after (x) days, but want to keep the LOG entries, what is best to do?
Just find quarantined chunks and set to ''? Or point id to a phony
(blank) record?
The former
On 7/5/07, Michael Scheidell [EMAIL PROTECTED] wrote:
Brian Wong wrote:
If you just delete records from the 'quarantine' table there would be
no problem. Because the reference is to the 'msgs' table, not the
other way around.
if you then 'clean out logs' (ie, delete records from msgs
On 6/14/07, Sam Tran [EMAIL PROTECTED] wrote:
- Isolate OR statements in convertEmailaddresses2SQL
Just for clarification, the message index when using recipient
delimiters was displaying mail it should not have. The bugfix was just
the inclusion of specific OR statements within parentheses of
snip
Thanks Michael and Brian. Do you get these also when it tries to
perform RBL checks?
fatal: alarm time out at /usr/local/share/perl/5.8.4/Net/RBLClient.pm line 85.
I think that is just Net::RBLClient complaining that a particular RBL
didnt respond in time and is skipping it. Im not
If you only want SQL quarantine, then start from the section in the
README.sql where it says...
-- R/W part of the dataset (optional)
-- May reside in the same or in a separate database as lookups database;
-- REQUIRES SUPPORT FOR TRANSACTIONS; specified in @storage_sql_dsn
The four
Sorry for top-posting
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1
Dear Mailzu and Amavisd-new Users,
The MailZu Team is pleased to announce the availability of MailZu 0.7b
which is a quarantine management interface for amavisd-new 2.3.0 or
later. It is based on amavisd-new SQL reporting and AM.PDP protocol.
This version and future versions of MailZu needs an
On 5/3/06, Paolo Cravero as2594 [EMAIL PROTECTED] wrote:
We have a 50GB (fifty GigaB) quarantine table on the production server,
and the last quarantine purge run took 14 hours to complete. All traffic
was queued because of DB locks and timeouts. We clean every second day
for spam 30 days
On 4/26/06, Cami [EMAIL PROTECTED] wrote:
The time_num on tables quarantine and msgrcpt was used in
some on the pre-releases of 2.4.0, but I decided not to include
it in the final 2.4.0 in favour of DELETE CASCADE, as on
my setup (still at MySQL then) there was no noticeable
advantage of
On 4/4/06, Kai Lauterbach [EMAIL PROTECTED] wrote:
Dear Mailinglist,
i got the following error message while amavis send any spam or virus
mails into the database.
Apr 4 15:23:18 localhost amavis[26510]: (26510-01) ERROR sql_storage:
too many retries on storing preliminary, info not saved
On 4/4/06, Kai Lauterbach [EMAIL PROTECTED] wrote:
Ok, here are the other Messages...
thanks for the fast reply! :)
Kai
---
Apr 4 16:13:22 localhost amavis[26538]: (26538-01) WARN
save_info_preliminary: sql execute: sts=, Insecure dependency in
parameter 10 of
On 3/27/06, Mark Martinec [EMAIL PROTECTED] wrote:
Hopefully the last release candidate before the final release:
http://www.ijs.si/software/amavisd/amavisd-new-2.4.0-rc5.tar.gz
It is probably too late to bring up, but instead of adding a
'time_num' column to 'msgrcpt' and 'quarantine'
On 2/28/06, Mark Martinec [EMAIL PROTECTED] wrote:
Brian,
Can anyone else confirm that reconnection does not work with
PostgreSQL? Im suspecting that the line:
eval { $self-dbh-begin_work(@_) }; # line 9575 of amavisd 2.3.3
always returns true for the DBD::Pg module regardless of the
List,
Can anyone else confirm that reconnection does not work with
PostgreSQL? Im suspecting that the line:
eval { $self-dbh-begin_work(@_) }; # line 9575 of amavisd 2.3.3
always returns true for the DBD::Pg module regardless of the state of
the connection. Therefore constantly making false
On 2/15/06, Andrew A. Neuschwander [EMAIL PROTECTED] wrote:
2) The filename prefix used by amavis, i.e. banned-, is configurable
in the amavis config and NOT supplied in the SQL tables. The SQL
reporting tables (msgrcpt msgs) only contain the mail_id for the
quarantined message. For MailZu
List,
I am looking for a configuration on outbound email server. Basically
what I want to do is pass all attachments if it is destined for a
domain that we are not responsible for. If it is internal mail, apply
banned rules and route it to the message store servers. What I am
thinking is that the
On 1/13/06, Mark Martinec [EMAIL PROTECTED] wrote:
I use LDAP, and the attribute 'amavisBannedRuleNames' has me believing
I can create a named set of banned rules and reference them in the
users lookup table. Much like having different behavior in a policy
bank. Am I misinterpreting this
List,
I would like to exclude a recipient from my site-wide banned rules,
yet be subject to another set of banned rules which is slightly
different from the site-wide one. Is this possible?
In my specific case, these users need to receive a certain file type,
yet everyone else shouldnt be
On 9/21/05, Rocco Scappatura [EMAIL PROTECTED] wrote:
Thanx,
do you know a solution based on the options of amavisd-new??
Use policy banks.
$policy_bank{'MYNETS'} = { # mail originating from @mynetworks
bypass_spam_checks_maps = [1] # or: don't spam-check internal mail
};
On 9/21/05, Rocco Scappatura [EMAIL PROTECTED] wrote:
Hello,
this is my @mynetworks definition:
@mynetworks = qw( 127.0.0.0/8 ::1 10.0.0.0/8 172.24.0.0/16 172.25.0.0/16
80.74.176.0/20 );
This looks fine, have you restarted amavisd after the configuration
change? Can you verify that the
On 8/31/05, Mark Martinec [EMAIL PROTECTED] wrote:
Perhaps there should be two flags to reflect each of the kill / tag2 levels.
I do not think that is necessary.
The idea behind the current choice is the same as for quarantining:
- if mail is not delivered, it goes to quarantine and content
So the 'content' field of the msgs table is only updated with an 'S'
if it at or above kill level. Can someone explain to me why this is?
It is somewhat confusing when the score is between
$sa_tag2_level_deflt and $sa_kill_level_deflt. The database would say
'C' (clean) yet the logs would say
I tried indexing the quarantine table by one of its fields mail_id:
CREATE INDEX quarantine_idx_mail_id ON quarantine(mail_id);
and the query now takes a reasonable 1 second for 85000 rows.
I thought the 'PRIMARY KEY' in the 'CREATE TABLE quarantine' statement
created an implicit index.
24 matches
Mail list logo
