Re: [AMaViS-user] Per-domain selective scanning

2010-03-05 Thread Tim Howe
On Fri, 5 Mar 2010 22:16:57 +1100 (EST) "Voytek Eymont" wrote: > > On Fri, March 5, 2010 8:44 pm, Jack Knowlton wrote: > > On Fri, March 5, 2010 1:47 am, Tim Howe wrote: > >> On Fri, 5 Mar 2010 11:04:26 +1100 (EST) > >> "Voytek Eymont" wrote: &

Re: [AMaViS-user] Per-domain selective scanning

2010-03-04 Thread Tim Howe
On Fri, 5 Mar 2010 11:04:26 +1100 (EST) "Voytek Eymont" wrote: > I use amavis' viruslovers/spamlovers files to list users to be exempted Ah, yes. That's what I couldn't think of. These settings are also available if you use a database. --TimH -

Re: [AMaViS-user] Per-domain selective scanning

2010-03-04 Thread Tim Howe
On Thu, 4 Mar 2010 11:46:40 +0100 "Jack Knowlton" wrote: > Hi all, > > I host several domains on a single server. As of now every email is > scanned for both viruses and spam, but I would like to exclude one domain > from spam filtering. > Is that possible? > Thank you. There's a few wa

Re: [AMaViS-user] bogus HELO name used

2010-02-25 Thread Tim Howe
On Fri, 26 Feb 2010 00:44:49 +0100 Oscar Mauricio Cruz Lazo wrote: > thanks alot > > my postconf -n > > > here my config postconf -n > > [...] Maybe they have some kind of dorky regex check that doesn't like your hostname because it has more than two dots? I've seen stranger...

Re: [AMaViS-user] bogus HELO name used

2010-02-25 Thread Tim Howe
On Fri, 26 Feb 2010 00:44:49 +0100 Oscar Mauricio Cruz Lazo wrote: > myhostname = apac3.apac.org.ni This sure can't be helping... $ dig apac3.apac.org.ni ;; ANSWER SECTION: apac3.apac.org.ni. 599411 IN A 165.98.119.11 $ dig -x 165.98.119.11 ;; ANSWER SECTION: 11.119

Re: [AMaViS-user] bogus HELO name used

2010-02-25 Thread Tim Howe
On Thu, 25 Feb 2010 21:44:33 +0100 Oscar Mauricio Cruz Lazo wrote: > Hi all > > I runnig a postfix server but now i notice Emails from my server is being > blocked by some ISPs because they claim it has a bogus helo, > I just checked the list and my IP is not listed as a spammer, > > this only

Re: [AMaViS-user] policy bank options ignored?

2009-08-03 Thread Tim Howe
Thanks for your reply :) On Mon, 3 Aug 2009 19:11:45 +0200 Mark Martinec wrote: > The DSN for spam is suppressed when spam score exceeds spam_dsn_cutoff_level. Yes, that's why I set it so high, I was using the GTUBE email to test which scores around 1000. > Note that since 2.4.3 there

Re: [AMaViS-user] policy bank options ignored?

2009-07-28 Thread Tim Howe
On Mon, 27 Jul 2009 23:59:20 -0700 Tim Howe wrote: > I have the following for my originating senders: > > $interface_policy{'10026'} = 'ORIGINATING'; > > $policy_bank{'ORIGINATING'} = { # mail supposedly originating from our users > origina

[AMaViS-user] policy bank options ignored?

2009-07-28 Thread Tim Howe
I have the following for my originating senders: $interface_policy{'10026'} = 'ORIGINATING'; $policy_bank{'ORIGINATING'} = { # mail supposedly originating from our users originating => 1, # declare that mail was submitted by our smtp client virus_admin_maps => ["virus_adm...@$mydomain"],

Re: [AMaViS-user] Amavisd Wont Show X-Spam Headers

2009-07-17 Thread Tim Howe
On Fri, 17 Jul 2009 13:58:42 -0400 Carlos Williams wrote: > On Thu, Jul 16, 2009 at 1:37 PM, Tim Howe wrote: > >        One reason could be that it no longer sees the address as local.   > > Maybe > > your database is no longer there or looked at, or maybe @local_domains_

Re: [AMaViS-user] Amavisd Wont Show X-Spam Headers

2009-07-16 Thread Tim Howe
On Thu, 16 Jul 2009 10:06:28 -0400 Carlos Williams wrote: > No longer am I see the following in my incoming message headers: > > > X-Virus-Scanned: Debian amavisd-new at unixslut.com > > X-Spam-Score: -2.325 > > X-Spam-Level: > > X-Spam-Status: No, score=-2.325 tagged_above=-5 required=4 > >

Re: [AMaViS-user] PostgreSQL 8.3 requires changes to queries

2009-07-07 Thread Tim Howe
On Tue, 7 Jul 2009 08:08:43 -0700 Tim Howe wrote: > I haven't seen this mentioned yet, so if this is already being > discussed I apologize. > > As of Pg version 8.3, "Non-character data types are no longer > automatically cast to TEXT". See > http://www.postgre

[AMaViS-user] PostgreSQL 8.3 requires changes to queries

2009-07-07 Thread Tim Howe
I haven't seen this mentioned yet, so if this is already being discussed I apologize. As of Pg version 8.3, "Non-character data types are no longer automatically cast to TEXT". See http://www.postgresql.org/docs/8.3/static/release-8-3.html under section E.8.2.1. General This requires changes to