Zhang,
On 5/19/09 10:21 PM, Zhang Huangbin wrote:
> Hi, list
>
> When running amavisd-nanny, i got below msg, however the execution
> of amavisd-nanny appears to be correct. Configure error or whatever?
>
>
> # amavisd-nanny
> Useless use of hash element in void context at /usr/sbin/a
Hi, list
When running amavisd-nanny, i got below msg, however the execution
of amavisd-nanny appears to be correct. Configure error or whatever?
# amavisd-nanny
Useless use of hash element in void context at /usr/sbin/amavisd-nanny
line 61.
Useless use of a constant in void context at /usr/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oenus Tech Services wrote:
> Hi there!
>
> Can anybody tell me how can I either whitelist or bypass all emails
> coming from a backup mx server IP so amavis won't score them when mail
> arrives to the master mx server?
Assuming you have scanning and
Hi there!
Can anybody tell me how can I either whitelist or bypass all emails
coming from a backup mx server IP so amavis won't score them when mail
arrives to the master mx server?
Thanks in advance,
Ignacio
--
Crystal
Eric,
> > You may have been the victim of a Perl problem:
> > http://rt.perl.org/rt3/Public/Bug/Display.html?id=63054
> > see also:
> > https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6060
> >
> > If using perl 5.8.9 on FreeBSD, I'd recommend to switch
> > to 5.10.0 form ports. The 5.8.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Martinec wrote:
> Eric,
>
>> I have a mysterious problem. After upgrading amavisd-new to 2.6.2 on
>> FreeBSD (port version 2.6.2_3,1), it simply dies after about 20 seconds
>> with no errors or core dumps.
>> I cranked the debug level up to 5 and
> i have amavisd 2.6 running fine and blocking some file
> extensions/type, using banned_filename_re.
> so far, so good. It's working fine.
>
> what i was needing now is to exclude some senders/recipients from
> the exclude list. For example, mails coming from @something.com wouldnt
> be subjected
Thomas,
> Amavisd-nanny is a great tool to get a quick overview of amavisd-new's
> current state. Some time ago I've used a modified version, as there as
> been no "-c" switch - now it is even easier to script it. We are for
> example parsing and embedding it's output in a web application allowing
On Tue, May 19, 2009 at 11:41 AM, Mark Martinec
wrote:
> Murilo,
>
>> I'd like to know how mail IDs are created by amavis. I mean I'd like
>> to have two 2 mysql servers replicating as master-master, so the field
>> msgs.mail_id cannot be duplicated.
>
> Entropy is being collected from passing mai
Karsten,
> this doesn't seem to change anything
>
> @spam_kill_level_maps = ( ...
> The domains I use are in @local_domains_maps = (
> read_hash("$MYHOME/local_domains") ); and normal Spam tagging works.
> But the kill level doesn't seem to change.
>
> The header still states 6.31
>
> X-Spam-Stat
Mark Pote,
> I'm running on Fedora 7 with amavisd-2.5.3, postfix-2.5.0. This has been
> working like a dream for at least a year but yesterday I saw this in the
> logs.
> 451 4.5.0 Error in processing, id=04327-01-4, quar+notif FAILED:
> Can't find Unicode property definition "a" at /usr/loc
Murilo,
> I'd like to know how mail IDs are created by amavis. I mean I'd like
> to have two 2 mysql servers replicating as master-master, so the field
> msgs.mail_id cannot be duplicated.
Entropy is being collected from passing mail and other system sources
readily available to amavisd, then a m
Stanislas,
> > For the time being, one can either:
> >
> > - snatch a message from a quarantine (easier with file-based quarantine),
> > and feed it to 'spamassassin --report' or --revoke, or to sa-learn
> >
> > - release from a quarantine to a dedicated recipient address
> > (overriding reci
Hi all,
I'd like to know how mail IDs are created by amavis. I mean I'd like
to have two 2 mysql servers replicating as master-master, so the field
msgs.mail_id cannot be duplicated.
Thanks in advance.
--
Murilo Opsfelder Araújo
mopsfel...@gmail.com
{murilo,pan...@bsd.com.br
Don't learn to hack
> Dan,
>
> > Another question I have is that these weights don't seem to add up
> > correctly? From that last one:
> > (1.37 + 0.001 + 1 + 0.992 != 1.956)
>
> Probably the same cause as above.
> Does it now add up after updating the plugin?
>
[DH] Yes, indeed it does add correctly now.
---
rickygm,
> > $spam_quarantine_to = 's...@domain.org.ni';
> > $spam_quarantine_method = 'smtp:localhost:25';
> ok works me, but the problem is that I receive it to the spam account
> 22 copies of that mail with spam , and the percentage of my processor
> ascends to 29%
>
> why sends so many copies
Eric,
> I have a mysterious problem. After upgrading amavisd-new to 2.6.2 on
> FreeBSD (port version 2.6.2_3,1), it simply dies after about 20 seconds
> with no errors or core dumps.
> I cranked the debug level up to 5 and sent it all to syslog. [...]
> As far as I can tell, there is no way to ru
Grant,
> any one else able to maybe offer pointers ? I've been looking through
> the code at add_forwarding_header_edits_per_recip
> but it is a bit deep for me.
As a message id to be inserted is probably not dependent on the
recipient (so there is no need to split a message if different
recipien
Peter,
> afte having rearead a lot of the documentation, and emails from the past,
> I realised that I hab been wrong about my assumption regarding the
> variable
>
> @bypass_banned_checks_acl = qw( t...@example.com huetm...@example.com );
>
> This, I now realise, makes sure that the emailaddresse
Pete McNeil wrote:
> For the sake of other SpamAssassin / AMAVIS developers:
>
> The SNF4SA antispam plugin that did not work had this line in snf4sa.pm
> $permsgstatus->{scoreset}->[$set]->{"SNF4SA"} =
>
> This version appeared to work correctly when used with SA alone but did
> not work correc
Jason,
> am using Gentoo and have emerged Postfix, ClamAV, SpamAssassin and Amavis
> (amavisd-new-2.6.1-r1)
>
> Postfix server accepts and sends email fine but upon configuring Amavisd my
> log upon recieving an email shows the following and the mail is not placed
> in the mailbox:
>
> amavis[2974
Bruno,
I cannot receive any from a specific domain, amavisd (2.3.2) stops
emails and always returns a bad header check error:
> May 15 11:38:32 newton amavis[810]: (00810-06) BAD HEADER from
> <2...@agglo-belfort.fr>: Non-encoded 8-bit data (char 84 hex) in
> message header 'Message-Id': Messa
22 matches
Mail list logo
