I seems that this morning (it is morning i Spain ), scanLog.php is working fine again.
It must be some code/characters in some of the mailadresses or similar that make the maillog file unreadable for scanLog.php.
Running daily cron /etc/cron.daily/yum.cron results in a lot of errors, what are those errors?
The e-mail I receive is more or less one big list of errors like:
//var/cache/yum/base/repomd.xml:12: parser error : Input is not proper UTF-8, indicate encoding !
Bytes: 0xA9 0x20 0x20 0x32
...and towards the end the errors are more like:
//var/cache/yum/base/repomd.xml:626: parser error : Premature end of data in tag meta line 8
P.S. how long does ESVA keep quarantined messages?
Greetings all, thanks for the assistance so far.
I have noticed that when I manually teach mailwatch that a clean email is actually spam, nothing seems to happen. Has anyone seen this?
If you are referring to the funktion in MailWatch called "Message Operations" Under "Reports", I do not get any output from MailWatch either.
This does not automatically mean that nothing happens, but I suspect it also.
Can anyone tell us wether it is working or not?
As I am using ESVA for multiple customers with multiple domains and mailservers, I also get multiple requests to customize the behavior of ESVA.
For that I have used rulesets, and now I found an easier way to come about that. The Webmin has a fine editor, but it is manual, meaning it is just a text-editor.
There is a script at http://sourceforge.net/projects/msre/ that make it a lot easier, and it can be implementet into MailWatch.
Download it, unpack it (Winrar does the job), and upload the folder to /tmp using WinSCP.
Then on the VMware server console, go to the ESVA virtual machine, log on as root, write the following commands:
then just press enter for all the questions until you return to the command prompt.
You also have to change permission for the file /etc/msre/msre_reload.sh. I have changed it to 777, but I am not sure that is the best, any of you linux guys, please confirm or alter this.
Now when you log on to Mailwatch as administrator you have a link to a ruleset editor under the menu "Tools/Links"
I am in the process of setting up a new forum at http://www.global-domination.org/forum/
This will allow much greater flexibility for ESVA discussion than is available here in the VMTN forums.
There will be some more work done on the new forums, but they are ready for registration (no content yet, but someone has to be first!)
Thank you very much for your script. I have made some modifications to it so i can use it in the mailscanner directory and use the global settings for specific users.
I posted this on Andy's new forum:
The topic is: Official scanLog 0.1 Thread!.
The sent items i removed, because i think me users will not understand.
Thanks again for posting the initial script.
Message was edited by:
I'd like to expand ESVA's default disk size from 4GB to 10GB.
I'm going to use "vmware-vdiskmanager -x" command, however esva has three vmdk files such as ESVA16-f00*.vmdk.
f001 and 002 is 2GB and 003 is 512KB.
Which one should I expand? I suppose expand f001 and 002 to 5GB each may satisfy my requirement, but I want to clarify before doing.
Please post in the new forum at http://www.global-domination.org/forum
There is actually only one VMDK - the f001 and 002 are 2GB portions of the same VMDK (it's split into 2GB chunks for Linux/ESX import compatibility, as well as being able to be defragged under windows).
Run your command against ESVA16.vmdk - it will know what to do...
Also see http://www.global-domination.org/ESVA/howto/howto-esvabigdisk.pdf to add more capacity (This is a better way...)
Andy, thank you so much for your information. I'll post to new forum from next time.
I tried the script to import the user from the AD with ldap.
I get an error when I try it, anyone did try it? and if so anyone have a idea why its not working.
Error I get is :
Can't locate MIME/Base64/Perl.pm in @INC (@INC contains: /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl/5.8.4 /usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl/5.8.4 /usr/lib/perl5/vendor_perl/5.8.3 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.6/i386-linux-thread-multi /usr/lib/perl5/5.8.6 .) at ./eric line 14.