>
> Sounds like you've been hit by bug 5519 [1] before the upgrade in Oct.
> Setting rules scores to 0 did *not* prevent these tests from being
> evaluated for SA 3.2.x before 3.2.3.
>
> Fixed since 3.2.3. Plugin eval rules with 0 scores are meant no not be
> evaluated, and of course to not sho
On Sat, 2008-01-12 at 18:03 +, Arthur Dent wrote:
> Hello All,
>
> I'm afraid that I might have wasted your time - Hence the change to the thread
> Subject.
>
> I guess that what triggered my original question was the fact that I was
> trying to check that everything was working following an
Gary V wrote:
>> From: marc
>>
>> postconf -n
>>
>> alias_database = hash:/etc/aliases
>> alias_maps = hash:/etc/aliases
>> broken_sasl_auth_clients = yes
>> command_directory = /usr/sbin
>> config_directory = /etc/postfix
>> content_filter = amavis:[$myhostname]:10024
>> daemon_directory = /usr/li
Ralf Hildebrandt wrote:
> * mouss <[EMAIL PROTECTED]>:
>
>> This really belongs to the postfix list, but ...
>>
>> Marc Perkel wrote:
>>
>>> [snip]
>>> mydestination = $myhostname, localhost.$mydomain, $transport_maps
>>>
>> remove $transport_maps. reusing unrelated maps is horrible.
>
> Well here is what I have...
>
> [EMAIL PROTECTED] ~]# ls -la /etc/mail/spamassassin/
> total 148
> drwxr-xr-x 3 root root 4096 2008-01-11 22:54 .
> drwxr-xr-x 3 root root 4096 2007-12-29 19:48 ..
> -r--r--r-- 1 root root 4706 2008-01-11 22:54 Botnet.cf
> -r--r--r-- 1 root root 28616 2008-
> From: marc
>
> postconf -n
>
> alias_database = hash:/etc/aliases
> alias_maps = hash:/etc/aliases
> broken_sasl_auth_clients = yes
> command_directory = /usr/sbin
> config_directory = /etc/postfix
> content_filter = amavis:[$myhostname]:10024
> daemon_directory = /usr/libexec/postfix
> debug_pe
* mouss <[EMAIL PROTECTED]>:
> This really belongs to the postfix list, but ...
>
> Marc Perkel wrote:
> > [snip]
> > mydestination = $myhostname, localhost.$mydomain, $transport_maps
> remove $transport_maps. reusing unrelated maps is horrible. if a
> transport entry is added for say hotmail.com,
I know that it didn't happen under 3.2.3 because A) no config files changed,
and B) very clearly my per-user settings are not being processed.
Vpopmail should be the user spamd runs as because the per-user settings are
in a directory that is owned by vpopmail:vpopmail.
Per-user files are in /var/
This really belongs to the postfix list, but ...
Marc Perkel wrote:
> [snip]
> mydestination = $myhostname, localhost.$mydomain, $transport_maps
remove $transport_maps. reusing unrelated maps is horrible. if a
transport entry is added for say hotmail.com, postfix will accept and
mis-deliver (or bo
Hello All,
I'm afraid that I might have wasted your time - Hence the change to the thread
Subject.
I guess that what triggered my original question was the fact that I was
trying to check that everything was working following an OS upgrade. Looking
back through my spam corpus it seemed that I wo
postconf -n
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
broken_sasl_auth_clients = yes
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = amavis:[$myhostname]:10024
daemon_directory = /usr/libexec/postfix
debug_peer_level = 2
home_mailbox = Maild
> Gary V:> > > I think Postfix may know it's the final destination for the
> domains in> > question,> > No, it could also be a relay domain. In that case
> the mail would loop,> since it goes back to the MX (the other machine) and
> comes backe etc.> etc.> > -- > Ralf Hildebrandt
Right, I ac
> It's not required to point the MX to the Postfix server! The problem is
> the Postfix server does not accept mail addressed to it. If you were
> to set the MX back to pointing to the Postfix server, the server would
> continue to reject mail addressed to it because it is not configured to
> acce
> I think Postfix may know it's the final destination for the domains
> in question, otherwise ALL mail would be rejected.
>
>
> Actually that's what is happening. When they moved the MX to point to
> our spam filter servers their server started rejecting ALL their email
> that we are forwardin
* Gary V <[EMAIL PROTECTED]>:
> I think Postfix may know it's the final destination for the domains in
> question,
No, it could also be a relay domain. In that case the mail would loop,
since it goes back to the MX (the other machine) and comes backe etc.
etc.
--
Ralf Hildebrandt (i.A. des IT-Z
Gary V wrote:
Sorry for the OT question but just need a quick answer from a postfix
expert.
Here's the problem. I run a front end spam filtering service. Email from
the world comes in, I clean it, and send the good email to the original
server. However sometimes because my service is now the p
> Sorry for the OT question but just need a quick answer from a postfix
> expert.
>
> Here's the problem. I run a front end spam filtering service. Email from
> the world comes in, I clean it, and send the good email to the original
> server. However sometimes because my service is now the primary
Bill Randle wrote:
On Sat, 2008-01-12 at 08:14 -0800, Marc Perkel wrote:
Ralf Hildebrandt wrote:
* Marc Perkel <[EMAIL PROTECTED]>:
Sorry for the OT question but just need a quick answer from a postfix
expert.
Here's the problem. I run a front end spam filtering service.
Marc Perkel wrote:
>
>
> Ralf Hildebrandt wrote:
>> * Marc Perkel <[EMAIL PROTECTED]>:
>>
>>> Sorry for the OT question but just need a quick answer from a
>>> postfix expert.
>>>
>>> Here's the problem. I run a front end spam filtering service. Email
>>> from the world comes in, I clean it, and
On Sat, 2008-01-12 at 08:14 -0800, Marc Perkel wrote:
>
>
> Ralf Hildebrandt wrote:
> > * Marc Perkel <[EMAIL PROTECTED]>:
> >
> > > Sorry for the OT question but just need a quick answer from a postfix
> > > expert.
> > >
> > > Here's the problem. I run a front end spam filtering service.
Ralf Hildebrandt wrote:
* Marc Perkel <[EMAIL PROTECTED]>:
Sorry for the OT question but just need a quick answer from a postfix
expert.
Here's the problem. I run a front end spam filtering service. Email from the
world comes in, I clean it, and send the good email to the original server
* Marc Perkel <[EMAIL PROTECTED]>:
> Sorry for the OT question but just need a quick answer from a postfix
> expert.
>
> Here's the problem. I run a front end spam filtering service. Email from the
> world comes in, I clean it, and send the good email to the original server.
> However sometimes
Sorry for the OT question but just need a quick answer from a postfix
expert.
Here's the problem. I run a front end spam filtering service. Email from
the world comes in, I clean it, and send the good email to the original
server. However sometimes because my service is now the primary MX when
On Fri, Jan 11, 2008 at 07:20:59PM -0500, Dave Koontz wrote:
>
> Arthur Dent wrote:
>> Nope sorry..
>>
> Please confirm... that your botnet.pm file is where your other plugin PM
> modules reside. And that the botnet.cf file is where your custom rules
> live (may be a different path depending
Hi
2008/1/11, Bret Miller <[EMAIL PROTECTED]>:
> > New upgrade is running GREAT here :)
>
> Running fine here on Windows Server 2003 with CommuniGate Pro. :)
>
>
Well, scan times went DOWN a LOT!!! According to Amavis-Logwatch:
=
(Please keep it on the list...)
Gene Heskett wrote:
PS. I'm very sceptical to the idea of --allowplugins.
Oh, openprotect seems to want it..
I know. I just think you should decide for yourself what plugins
to load, rather than trust a third party. YMMV of course.
(Also, if the OpenProtect
>> (Please keep it on the list...)
Gene Heskett wrote:
Have you checked in the key ring to see that it's really there?
The command is cat, but what file?
I don't know from memory, but my guess is that reading the man
pages would give an answer to this.
gone, but it also isn't updating a
Matthew Goodman wrote:
I am also having this error in my spamd.log file.
Spamd is being run with:
SPAMD_OPTS="-c -d -v -m 40 -s local4 -q -u vpopmail
--virtual-config-dir=/var/vpopmail/domains/%d/%l/.spamassassin/ -H
/var/vpopmail"
And spamc is being called by qmail-scanner-2.01 with /usr/bi
On Saturday 12 January 2008, Arthur Dent wrote:
>On Fri, Jan 11, 2008 at 09:46:30PM -0500, Gene Heskett wrote:
>> That's possible I suppose. In watching what pup wants to update, I've had
>> bigger fish than gpg to monitor. Is there a history file I can consult to
>> find out?
>
>If you use a Red
On Saturday 12 January 2008, Arthur Dent wrote:
>On Fri, Jan 11, 2008 at 09:46:30PM -0500, Gene Heskett wrote:
>> That's possible I suppose. In watching what pup wants to update, I've had
>> bigger fish than gpg to monitor. Is there a history file I can consult to
>> find out?
>
>If you use a Red
On Fri, Jan 11, 2008 at 09:46:30PM -0500, Gene Heskett wrote:
>
> That's possible I suppose. In watching what pup wants to update, I've had
> bigger fish than gpg to monitor. Is there a history file I can consult to
> find out?
If you use a Red Hat based system try:
# cat /var/log/yum.log
(as
Le 11-janv.-08 à 18:00, Mark Martinec a écrit :
Pascal,
it seems that since my upgrade to spamassassin 3.2.4, the DKIM an
DomainKeys verifiers are no more used.
All I see in the debug test are the following line :
# spamassassin -D < testmail.txt |& grep -i dkim
[4163] dbg: plugin: loading
> If I'm not mistaken it doesn't show non standard headers
> and also doesn't appear to allow the viewing of mime
> attachments. So it's quite difficult to see exactly what
> the spam assassin headers/report look like from an
> iphone's native mail client.
iPhone sucks. Nokia has models running D
33 matches
Mail list logo
