ConfigServer Community Forum

This is not a bug, it is the way the upgrade process works. If you have customised any files you should of course always make backup copies of any files that you have modified. There may be changes in the new files, so you should compare them to your backed up files to ensure that you include any ne...

Hi Gabrielle,

If you want to do system-wide filtering in exim you can edit the /etc/antivirus.empty file and add your filters to it, although you should keep a backup copy of it as you may need to replace it after upgrading Mailscanner.

Have you run MailScanner in debug mode? We have seen problems with the IO perl module with a recent CentOS update. You just need to manually upgrade IO using /scripts/perlinstaller. The 500 errors is probably completely unrelated. We have not seen this issue on our server running R25133. Regards, Sa...

There is a FAQ with full information on this subject:
http://www.configserver.com/techfaq/index.php?faqid=60

You will need to email us with the old IP address and new IP address so we can update the MSFE license database.

Glad you got it working in the end. That was an odd one.

Regards,
Sarah

Try adding this line just above the double file extensions rule in /usr/mailscanner/etc/filename.rules.conf:

# Allow .rel files
allow \.rel$ - -

Be sure to put tabs in between the fields.

Regards,
Sarah

We have not seen this before. Make sure that you're not running out of disk space for the /tmp/ partition and that the permissions of the /tmp/ directory are 1777. Could be that you ave a corrupt /tmp/ partition.

Regards,
Sarah

The clue is in the SpamCheck report in the headers: X-Spero-MailScanner-SpamCheck: spam(no watermark or sender address) MailScanner's watermarking rule has been triggered because there was no sender. Go into the MailScanner Configuration and search for Watermarking. There is a whole section with mul...

Have you been through all the suggestions in this FAQ?
http://www.configserver.com/techfaq/index.php?faqid=58

If you need support for this please log a support ticket on our helpdesk.

You are running Fedora Core 4, which has a known bug in gcc as stated in the error message you're getting when trying to upgrade: checking for gcc bug PR28045... configure: error: your compiler has gcc PR28045 bug, use a different compiler, see http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28045 You w...