@Dirk, This is backscatter of undeliverable e-mails and not the SPAM directly so technically it is legitimate mail coming from ISP's/postmasters and won't get picked up by the usual spam filters. I don't think there is much you can do except block on the subject or possibly the sender "mailer-daemon". I would suggest you only do this temporarily, because if you send something to an incorrect recipient, you may want to see these messages to tell you your legitimate mail has failed.

To block on sender, have a look at /etc/postfix/access. Discard rather than reject. To block on subject, have a look at /etc/postfix/header_checks. You can also block on sender with header_checks but using access is preferable as it is less expensive with processing.

Finding a driver for that looks tricky. Probably the easiest answer is to install the latest kernel from ElRepo. If you then want QoS to work, you need to change "QOS_ENABLE_IFB" to "yes" in /etc/clearos/qos.conf.

If you do try an ElRepo kernel you will be living life on the bleedin' edge and I have no experience ot it.

As a halfway house, you could try the 7.6 kernel, just in case:Then reboot.

I can't help much unless you can see something to commonly identify these mails. It is possible to set up a generic filter just to kill these based on the subject or some other feature. You could do that temporarily.

If you're in luck the storm will die away again. Please can you post a couple of the mail headers?

I've added two more rules at the end, to effectively place the "RELATED,ESTABLISHED" rule above the rules we are entering or you could get problem with any further manual rules you enter.

There is some good news. Clearcenter are looking to move over to the Discourse type of forum. As an example, see the OSMC Forums. Timescale is as yet unknown.

Re VLANS/LAN's, it has been suggested by the devs that the default change from all LAN's and VLAN's being able to talk to each other, to all LAN's and VLAN's being isolated from each other. It does leave some issues. Currently LAN's are allowed to talk to HotLAN's and not vice-versa, so that would have to be thought about. This sort of change can't be made mid-release as it could break too many systems so would have to wait to 8.x.

I've no idea.

The other folders in /var/lib/transmission/.config/transmission-daemon are transmission:transmission

To isolate LAN from each other, create a file /etc/clearos/firwall.d/05-isolatedlans and in it put:

This is not proving so easy. HotLAN's differ from LAN's in that they are not allowed to access the server, so you almost need the concept of Isolated LAN's which are like LAN's but can't talk to each other. I've updated the script for HotLANs:The problem with this approach is that it does not integrate with other functions of ClearOS like OpenVPN. OpenVPN can be got round by adding the subnets to EXTRALANS in /etc/clearos/network.conf. I have no idea what other side effects there are.

As an alternative, you can just create a firewall script to cut communication between the LAN's. It would have to insert rules rather than append them and wit would be better if it ran as an 05- type rule, so before all the 10-rules. I'll have a think about that.

Well, mine is bust. It is showing transmission:299 and 755 permissions and my torrents still work. Check what your umask is set to in /var/lib/transmission/.config/transmission-daemon/settings.json. Mine is set to 18 but you can only change it when transmission is stopped. I may have tweaked umask but I can't remember.