How to customize the EFA interface?

[ovizii]

So I was wondering what one can and what one shouldn't customize:

What I found so far is the signature content:
/etc/MailScanner/reports/en/inline.sig.out.html

then there is /etc/MailScanner/MailScanner.conf
and of course I have placed my own custom sa rules and scores and plugins inside /etc/mail/spamassassin/

but I'm wondering waht files we shouldn't touch as they willö be overwritten by updates.

What's the procedure to make EFA our own, aka add our own links/signatures/logos/colors for the interface/rules and settings?

any advice?

[pdwalker]

The web based interface is "mailscanner", now part of the mailwatch project. Everything there is in /var/www/html/mailscanner. Anything changed there will be overwritten in the next update. (I modified a report and lost the changes twice. doh! I'm getting good at making the changes though).

In general, I try to be careful about what I change so I won't cause problems with the updates, but after a year, I've made so many little tweaks that my system is a lot farther from the base installation than I originally planned. So far, it has survived 3 updates without problem.

What exactly do you want to change?

[ovizii]

Thanks for the reply.

So for one, I wanted to customize the emails/footers/signatures so I edited inside: /etc/MailScanner/reports/en/ and was now wondering whether those are update-proof or not and how to make them so.

I think that should be all for now (except my custom .cf and .pm files inside /etc/mail/spamassassin/ but I guess those area safe from being overwritten).

Anything else that comes to mind when talking about customizing an EFA installation?

[pdwalker]

Hmmm, I've never touched the footers, so I don't know about those.

The customized files seem safe in /etc/mail/spamassassin/, or at least mine have been so far.

I think the files in /etc/MailScanner/reports/en/ may get overwritten, so make sure you keep a copy elsewhere.

As I previously mentioned, the UI files in /var/www/html/mailscanner/ do get replaced, so again, keep a copy of your changes elsewhere.

Changes to /etc/postfix/main.cf seem to be preserved.

My best suggestion is to just go ahead and make your changes, but keep an exact record of what you have changed somewhere that you can refer to and check after an upgrade.

[shawniverson]

Preserved files:

/etc/mail/spamassassin/local.cf

/etc/MailScanner/reports/* (working on this for the next MailScanner upgrade)

/var/www/html/mailscanner/conf.php

/etc/postfix/*.cf

As a precaution, all these files are conveniently backed up to /var/EFA/backup during updates