Atomicorp

We too will probably stick with the php 4.4 / mysql 4.1 tree for a while as we have apps that depend on it. I love the ART archive, but big moves like this cause us some problems. Have you ever considered providing commercial archives that don't change in version numbers? I'm sure for a small yearly...

scott wrote:4.4.2 is linked against Mysql 4.1, so it wont work without it.

Cheers Scott. Does this mean there's no way around it (could it be built with a link against MySQL 4.0 instead?).

Hi Scott / All, First, this is a wonderful resource, many thanks Scott. We've been using it for 12 months now, however when you upgraded to MySQL 4.1 we had to stay at 4.0 ( I set up a local repository with your last 4.0 rpms and excluded them from the ART repository in yum.conf) as we have a large ...

It's far from perfect but... You can include the line touch($filename); before the relevant imagejpeg command. Obviously $filename must contain the correct filename, you'll have to code this in to your script. You can find affected files by running the following in your htdocs directory: grep -i --i...

Clearly 4.4.1 has issues with some apps, from what I've been seeing in the way its coded is that they're trying to push more security features into php. So we're seeing the fallout from that, and I definitely expect to see a lot more as time goes by. This warrants a different approach from my side,...

The newest version of phpadsnew is compatible with 4.4.1, so just update that and you're set. As I understand it it's not just phpadsnew but any php script that has this particular coding. We don't run phpadsnew but we do have a large amount of custom code, and I'm not keen on breaking live sites :...

ditto. Am keen to apply latest update but if our developers have used this code anywhere and I go ahead and break it then they'll strangle me! Do I have to wait for php 4.4.2?

We have a 7.5.3 server with all the latest patches/updates. When we run yum update the following apps are ready for update. [update: php-pear 4.3.11-8.rhfc2.art.i386] [update: php-xslt 4.3.11-8.rhfc2.art.i386] [update: spamassassin 1:3.0.3-1.rhfc2.art.i386] I will install/upgrade these to satisfy t...

thanks scott, the thing about the tcpserver thing is that it's just setting the environment variable QMAILQUEUE in the same way... i wonder why it doesn't work when you use tcp_wrappers. wierd!

if anyone else has any ideas?

Well, i've added the following line to hosts.allow: tcp-env: 127.0.0.1: setenv QMAILQUEUE "/var/qmail/bin/qmail-queue" Which I think is the tcp_wrappers equivalent of the tcpserver rules from the qmail-scanner homepage: (http://qmail-scanner.sourceforge.net/), yet it still doesn't work. An...

Hi, Since installing the ART qmail-scanner install, I've noticed that mails that arrive at our server and are then forwarded on are getting scanned twice. The problem seems to be that it is scanned before it is delivered - then when it is delivered it is redirected back to the smtp server for outgoi...

Thanks Scott, your hard work continues to be appreciated

That particular package was ver 3.1 in the base, the update wanted 3.4; the DAG version works great though

Cheers scott, figured out the clamav thing in the end.

I saw this on my system:

http://www.atomicrocketturtle.com/forum ... .php?t=367

The symptoms were the same, after today's update antivirus wasn't working until I'd installed that Perl package, rerun the qmail-scanner configuration script and restarted qmail.

note to get spamassassin to work after I fixed this, I had to rerun /usr/bin/qmail-scanner-reconfigure headers now show: Received: from 66.111.4.27 by munged.host.name (envelope-from <chris.james@munged.email.address>, uid 2020) with qmail-scanner-1.25st (perlscan: 1.25st. Clear:RC:0(66.111.4.27):. ...