ConfigServer Community Forum

Sarah found the issue when I failed. So there is a file %etc-dir%/archives.filename.rules.conf in the etc directory. It does not have a corresponding file in the rules directory. There is no archives.filename.rules.rules file, so it can't be turned on and off like the filename.rules.rules can be use...

I'm having an issue. I have a client who sends emails with files that break the rule for file names: Report: MailScanner: Attempt to hide real filename extension (10CWCY-221047Spectrum.pdf8.pdf) This isn't a problem, I normally just bypass the client with a change to filename.rules.rules which I hav...

I did the script one line at a time and got this:

You appear to lack the pcap(3) library.

Sep 9 11:21:33 mag osmd[82629] [osmd]: daemon started Sep 9 11:21:33 mag osmd[82629] [osmd]: Main Process: Can't locate Net/Pcap.pm in @INC (you may need to install the Net::Pcap module) (@INC contains: /etc/osm/Modules /usr/local/cpanel /usr/local/cpanel/3rdparty/perl/532/lib/perl5/cpanel_lib/x86_6...

I've been using OSM for over a year and today I went in and it wasn't running saying it needs PCAP? I'm not sure what has happened, obviously, its been running for a while, so PCAP must have been installed. As I remember OSM isn't a self install, so I don't have the install documents.

My experience has been that URIBL_BLOCKED is fairly useless. It hits ham as often as it hits spam.

One thing I did notice is that the ALL_TRUSTED flag has changed from 0 to -1. I was using ALL_TRUSTED to identify local mail, but now all mail from SMTP shows up under ALL_TRUSTED. This seems to make more spam go through since it is hitting most spam with a -1.

The fix worked for me, but since I don't get a lot of spam, I AGAIN didn't notice it was down until someone notified me very late in the day. Is there a way to track this and get a warning when this happens? It would be nice to know if spam scanning is broken through an automated system.

Sounds like more of a job for a log scanner, like logwatch.

Yea, I'm guessing it did. I ran Update Apache and PHPSuExec was back along with Zend, so it seems to be an easy fix. Odd that it would do that.