Ran into some strange things today:
Seems like the RAR decoder (unrar) doesn't cope very well with large .rar
files (~15MB).
First of all I got this message in the log:
Decoding of p002 (RAR archive data, v1d, os: Win32) failed, leaving it
unpacked: timed out
And then I got (obviously with a h
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 state of
> the connection. Therefore constantly maki
> I understood him to mean that when a message is sent to an
> external domain from inside a local domain, the recipient's
> name(s) would be captured and placed into an amavisd-new
> whitelist. This could probably be done by scripting a program
> to scan mail logs, collect the data, and place
Aaron, Gary,
| 1. internal user x sends mail to external user y.
| 2. since we are sending mail to user y, user y must be ok to receive
| mail from.
| 3. amavis or SA sees that we are sending mail "to" person y and
| automatically adds user y to whitelist, either per recipient or global,
| for
Siegbert,
> Thanks for your info about the Signal 13 (SIGPIPE). Possible i have
> found the process tries to write ??
So it appears. It is unclear to which pipe this refers to.
> The logfile /var/log/mail (needed by amavisd, postfix and others) are
> logrotated after +4096k with wrong permission
Found it!
First I created ./dev/log using 'cp -a /dev/log /var/amavisd/dev/log'
Then I had to add 'unix-stream("/var/amavisd/dev/log");' into
syslog-ng.conf as a source.
It had nothing to do with /etc/rc.conf. :)
Thanks for leading me in the right direction!!!
-Mark
-Original Message---
Mark Martinec schrieb:
> Siegbert,
>
>>> - All latest perl-module are installed. (Perl 5.6)
>>> After update to the last amavisd 2.3.3, we have the following Problem
> ...
>>> The new (amavisd virgin child) is created (new pid), but only for 2-3
>>> seconds. After this time the new virgin child cr
Mark A Jenks,
> I'm running a Gentoo box running Amavisd-new 2.3.3-r2.
> I've been running it in chroot, but have since removed it from there
> since Logging to mail.log/mail.info is not working.
> I am running syslog-ng 1.6.8.
> I'm not sure what changed, but somewhere around the update from abou
I'm running a Gentoo box running Amavisd-new 2.3.3-r2.
I've been running it in chroot, but have since removed it from there
since Logging to mail.log/mail.info is not working.
I am running syslog-ng 1.6.8.
I'm not sure what changed, but somewhere around the update from about
2.1 it stopped worki
Mark wrote:
> Aaron,
>> I have searched for this on the SA, postfix and amavisd-new lists and
>> the only thing that i came up with is that SA never sees the "rcpt to"
>> address.
>> Essentially all i want to happen is for amavisd-new or SA to add the
>> person our users are sending mail to the w
MJ,
> I am running postfix 2.2.4 on Solaris 8 with amavisd-new.2.3.2,
> SpamAssassin 3.1.0 and Clamav 0.8.7.1 as an AV/AS gateway to my main
> email system. Twice in last week our Spamassassin didn't detected sort
> of Russion SPAM where most of the addresses were starting from "ann..."
> and most
Mark Martinec wrote:
Aaron,
I have searched for this on the SA, postfix and amavisd-new lists and
the only thing that i came up with is that SA never sees the "rcpt to"
address.
Essentially all i want to happen is for amavisd-new or SA to add the
person our users are sending mail to the whi
Felix,
> What is considered the best way to introduce a configuration value? I
> read about maps and policy banks but did not find a real solution what
> to do...
>
> I want to add a per-user setting for the spam filter to use. I thought
> about using something like
> > @spam_filter_maps = ({ '[EM
Aaron,
> I have searched for this on the SA, postfix and amavisd-new lists and
> the only thing that i came up with is that SA never sees the "rcpt to"
> address.
> Essentially all i want to happen is for amavisd-new or SA to add the
> person our users are sending mail to the whitelist automatical
Siegbert,
> > - All latest perl-module are installed. (Perl 5.6)
> > After update to the last amavisd 2.3.3, we have the following Problem
...
> > The new (amavisd virgin child) is created (new pid), but only for 2-3
> > seconds. After this time the new virgin child crash, and the amavisd
> > mast
Siegbert Laukas schrieb:
> - All latest perl-module are installed. (Perl 5.6)
> - postfix 2.1.5
> - spamassassin newest
> - clamav (have already change from antivir)
>
>
> After update to the last amavisd 2.3.3, we have the following Problem:
>
> Normal-Szenario:
>
> 1. mail is
- All latest perl-module are installed. (Perl 5.6)
- postfix 2.1.5
- spamassassin newest
- clamav (have already change from antivir)
After update to the last amavisd 2.3.3, we have the following Problem:
Normal-Szenario:
1. mail is received, and amavisd process is running:
7013
17 matches
Mail list logo
