On Jul 6, 10:48am, Fernando Gleiser wrote:
}
} I've installed mimedefang-2.56 from source on a Solaris 8 system.
} Perl's version is 5.6.1 from sunfreeware.
}
} It seems to be working fine, except for one little detail: it doesn't
} log anything to syslog. the md_graphdefang_log_enable('mail', 1);
- Original Message -
From: "Fernando Gleiser" <[EMAIL PROTECTED]>
I've installed mimedefang-2.56 from source on a Solaris 8 system.
Perl's version is 5.6.1 from sunfreeware.
It seems to be working fine, except for one little detail: it doesn't
log anything to syslog. the md_graphdefang
I've installed mimedefang-2.56 from source on a Solaris 8 system.
Perl's version is 5.6.1 from sunfreeware.
It seems to be working fine, except for one little detail: it doesn't
log anything to syslog. the md_graphdefang_log_enable('mail', 1); line
in mimedefan-filter is enabled and syslogd is ru
Hallo, Kevin,
Du meintest am 20.03.06 zum Thema Re: [Mimedefang] error on some machines:
>> Mar 18 17:16:51 Arktur mimedefang.pl[32460]: Problem running virus
>> scanner: code=0.0234375, category=swerr, action=tempfail
> It's an error with your virus scanner. What virus scanner are you
> using?
On Mon, 20 Mar 2006, Helmut Hullen wrote:
"BitDefender". And there seems to be an error; "BitDefender" tells
"glibc detected *** double free or corruption".
What OS? Newer versions of glibc (ie in Fedora) do extra sanity checking
on memory access. You can control it with the MALLOC_CHECK_ e
Hallo, Kevin,
Du meintest am 20.03.06 zum Thema Re: [Mimedefang] error on some machines:
>> Mar 18 17:16:51 Arktur mimedefang.pl[32460]: Problem running virus
>> scanner: code=0.0234375, category=swerr, action=tempfail
>> What does that mean?
>> What does "code=0.0234375" mean?
> It's an error
Paul Murphy wrote:
>>You may consider cutting back to two slaves to save system
>>memory. You certainly don't need 5 slaves with this mail load.
> Ah, but I do, because the mail pattern is such that I tend to get mail in
> bursts on a regular basis, where 4-5 slaves are busy for a couple of min
Schu,
>> I have a small system at home using 5 slaves and which receives about 120
> > connections per day, almost all of which are between 0700 and 2300, so
some
> > of the slaves will be idle for longer than 8 hours overnight.
> >
>
> You may consider cutting back to two slaves to save system
Paul Murphy wrote:
>
> Note that this only happens on very low volume servers or where you have many
> more slaves than you actually need - if each of your slaves can be guaranteed
> to process one connection every 8 hours, you'll never see this! In my case,
> I have a small system at home using
It's an error with your virus scanner. What virus scanner are you using?
KAM
> Mar 18 17:16:51 Arktur mimedefang.pl[32460]: Problem running virus
> scanner: code=0.0234375, category=swerr, action=tempfail
> What does that mean?
> What does "code=0.0234375" mean?
>
> Where shall I search for
Hallo,
I have installed "mimedefang" on 4 servers (Slackware 10.2). On 2 of
them it works fine.
One of them tells in "/var/log/mail"
Mar 18 17:15:49 Arktur sendmail[32496]: starting daemon (8.13.5): SMTP
(Mail from "root" sent to "postmaster")
Mar 18 17:16:38 Arktur sendmail[32503]: k2IGGcE
Damrose, Mark wrote:
> What about doing a query in filter_tick every 2 hours?
That won't work, because you have no idea which slave runs filter_tick.
Much better to fix the broken MySQL behaviour; there's no reason to shut
down a TCP connection just because it's idle.
You also should (as Jan Co
> -Original Message-
> From: Paul Murphy
> I've finally found what I think is the cause of the problem -
> MySQL drops idle client connections if nothing has been heard
> from them in 8 hours (28800 seconds).
What about doing a query in filter_tick every 2 hours?
_
> Your software will probably become a lot more robust if you solve
> this problem in MIMEDefang, by testing the database handle before
> using it.
The problem with this approach is that the test has to identify that the
handle is stale, close it, and then re-open it again - and all outside of
"
On Mon, Mar 20, 2006 at 12:19:58PM -, Paul Murphy wrote:
> I've finally found what I think is the cause of the problem - MySQL drops
> idle client connections if nothing has been heard from them in 8 hours (28800
> seconds). This is controlled by the wait_timeout system variable, which can
[..
Hi,
Over the last couple of years, I've been using the MySQL version of
greylisting with an excellent level of impact on incoming spam. However, as
I reported before, my slaves were dying occasionally:
> Paul Murphy pmurphy at ionixpharma.com
> Fri Apr 8 06:12:19 EDT 2005
> I've been getting p
16 matches
Mail list logo
