efa-project.org

Did you ever resolve your problem?

Hi Ovizii,

Sorry for the delay in responding, I'm slowly working my way backwards through old posts.

It works perfectly for me.

Without logging into your system and diagnosing your settings, I cannot say why you are having the problem while I am not. Something must be modifying the message ...

Ok,

I've changed my mind slightly. I don't think I can call it an actual mailwatch bug. The full explanation is at the above "bug" report link.

The solution? Edit your viewmail.php file and change following line
$v = htmlentities($v);
to
$v = htmlentities($v,ENT_NOQUOTES,"utf-8"));
It's ...

definitely a problem in viewmail.php.

raised a bug report in the mailscanner project for this:
https://github.com/mailwatch/MailWatch/issues/773

It should be a simple fix.

Verified. Problem is in viewmail.php. Debugging.

yeah, problem seems to have gone away in 3.0.2.2.

henk: depending on which files you modified, you should find a copy in the backup copy efa makes when upgrading. That's how I quickly recover my customizations (via vimdiff new old).

will test and get back to you.

yes, 3.0.2.2. it autoupdated overnight. and i still have all the same timeout errors and invalid access errors.

wait， it autoupdated, so my timeout x 10 changes would have reverted. let me add back and test again.

AUGH! I cannot stand it.

When I am training the bayesian filter on multiple messages, the bloody UI will time out and log me out, which means, logging back in, finding my place, reselecting and retrying the operation with fewer messages.

Ultra @#$%@#! annoying!

Is there anyway we can make this ...

FYI: I'd previously opened a feature request for this at https://github.com/mailwatch/MailWatch/issues/765

ovizii wrote: 29 Dec 2016 16:43 turns out the files now have new names, its called: /usr/sbin/ms-update-bad-sites All good!

yes, it appears the cron files were reorganized during one of the mailwatch upgrades.

Any joy?

One problem I find with find with the bayes filter is that the spammers are finding new ways to defeat it temporarily until the filter is retrained which is why I cannot just rely on it solely.

yes.

by all means!

There are a few other attributes to include that I've not included due to laziness. They are all around line 313 or above in style.css.

It's a nice simple change that shouldn't cause any problems.

I've also done it to rep_total_mail_by_date.php, but that requires a few more changes.

Fuck yes!

I am constantly getting "invalid security tokens" for no apparent reasons. Mailwatch has gone from being usable to unusable.

Also, the damn timeouts are still a problem. Even after I changed the session timeouts to 10 times longer in the code, I am still getting timeouts, even when I ...

Ramas,

Can you provide the raw headers to that email, like I did in https://github.com/mailwatch/MailWatch/issues/742 (3rd comment down).

It will make the debugging a bit easier.

Or, you can follow what I did in that comment thread and see if your headers are being stored correctly?

1/ Find out how the guys email was hacked and prevent it from happening again.

2/ Make sure that your EFA box scans outgoing mail for spam, and if it detect spam, to stop it from going out.

In my opinion, EFA should remain focused on providing the best mail/antispam gateway service as possible.

Spending time adding monitoring features by the EFA developers is not a good use of their time given that others have already specialized in providing monitoring systems that are already very ...

Useful information.

cd /etc/MailScanner
grep -r "Attempt to hide real filename extension" *
archives.filename.rules.conf:#deny \.[a-z][a-z0-9]{2,3}\s*\.[a-z0-9]{3}$ Found possible filename hiding Attempt to hide real filename extension
filename.rules.conf:#deny \.[a-z][a-z0-9]{2,3}\s*\.[a-z0-9]{3}$ Found possible ...

( people! you can change your vote! fight against the oppression that is systemd! join us in this glorious revolution! )

Ok, you have to make a decision as to what is important and what is not.

If getting a high availability connection to the internet is not possible, or not important enough to the necessary money on, then your options are very limited. Think about it for a moment.

You have several scenarios you ...

I have two solutions to the problem

1/ all mail is filtered through messagelabs. they act as my primary mx host, so if I'm down, they'll hold the mail for me until I'm back up. They're a large company so I I expect their stability to be much, much greater than mine.

2/ at the office level, I have ...

I think this needs to be added to the regular maintenance to clear these useless files out.

Can you post a line showing the "bad content" message? That'll help me track down the setting.

[edit] it's probably related to one of the files in /etc/MailScanner/