efa-project.org

no, this doesn't accomplish what I need.

my case is a little different I have an upstream mail provider that removes all viral laden messages before passing them back to us (essentially they are our "smart host" for those particular domains. The messages they send us are greylisted when any traffic from their IPs should immediately be acce...

...I used ASSP in the past but setup was always very difficult and getting everything to work properly together was a very tedious job... I was looking at both EFA and ASSP at the same time. Your observation about ASSP is both correct and completely understated. I did manage to get it working after...

successful integration using the following settings LDAP_URI="ldap://<ip address of domain controller>:389" LDAP_BASE="DC=<domain name>,DC=<domain extension (local in my case>" LDAP_USER="<windows domain>\<login name>" LDAP_PASS="<my windows login password>" MYSQL_HOST="localhost" MYSQL_PORT="3306" ...

andyitc wrote:Tried adding the Class C but it didn't help

Andy

Any joy with solving your problem?

Keep in mind that it doesn't show where SQLGrey goes which I believe is part of the MTA process at the very start.

exactly as Charles says.

Look in the Mailscanner-Guide.pdf documentation on page 229 if you want to change the formatting of the warning The text added into the message is set in 2 settings in the [ ed: /etc/MailScanner/reports/en/ ] languages.conf file, one placed before the real address of the link, and the other placed b...

Look in the Mailscanner-Guide.pdf documentation on page 228 onwards for a description of the related options.

And that's much easier.

You only need to look at the spam assassin rules if you want to find out exactly what that condition is, assuming you can parse the regexes that is.

Nevermind, it is a function of Mailscanner controlled by /etc/MailScanner.conf, specifically

1/ Non Spam Actions =
2/ Spam Actions =
3/ High Spam Actions =

It is clear that EFA-Configure only modifies the first two MailScanner configuration options.

I just got bitten by this problem. There are three solutions that I can think of 1/ quick and dirty because you need it fixed now - comment out the "Attempt to hide real filename extension" rule in /etc/Mailscanner/filename.rules.conf and archives.filename.rules.conf 2/ whitelist the senders so the ...

I've configured EFA to store a copy of non spam into quarantine Non Spam Settings [EFA] Do you want to DISABLE storing non spam ? [y/N]: n and I've configured spam to be delivered (so people can check for false positives) Spam Settings [EFA] Do you want to ENABLE spam delivery? [y/N] y With these se...

Have a look at the mailscanner document on page 24 of the MailScanner User Guide and Training Manual at http://www.mailscanner.info/files/MailScanner-Guide.pdf It contain's a flowchart that should be mostly correct for EFA (since EFA is based on Mailscanner). Also keep in mind that the MTA (postfix)...

Hi All,

[edit: see below]

I'm looking to implement DKIM and I was wondering if anyone has already done so successfully with EFA.

I'm trying to avoid doing something that will break my efa installation in horrible ways during future updates.

Any advice appreciated.

I think the information is are here now:
https://efa-project.org/wiki/Beginners_Setup_Guide

or via webadmin
/viewtopic.php?f=14&t=537

Also consider using the webadmin module under
- servers
- Postfix Mail Server
- General Resource Control
- Max size of a message

You'll need to examine the Spamassassin rule sets, find the rule and then work out yourself why it was triggered (in 3.0.0.7, built from scratch) cd /var/lib/spamassassin/3.004000/updates.spamassassin_org [root@efa updates_spamassassin_org]# grep SPOOF_COM2OTH * 20_uri_tests.cf:uri SPOOF_COM2OTH m{^...

Also recommended: This creates a separate file for each innodb table, which allows you to optimize and shink them separately.

relevant?

AutoWhiteList for MailWatch
http://mailwatch.sourceforge.net/doku.p ... owhitelist

testing...

Is there a way to avoid the greylist for certain incoming ip address network ranges, e.g. "192.168.1.0/24" Some of our mail comes from a could email service provider with well defined service ip addresses, and everything they send us is "clean", thus we never want to slow them down. Possible? Thanks...

Excellent! :D I will work on this for the update. Shawn, If we attempt to "fix" this now using the suggested changes, will this cause a problem with the 3.1.0.0 update? Or would it be safest just to wait? (for what it's worth, I'll be dealing with a lot of UTF8, GB2312 and possibly BIG5 encoded mes...

If we have users sending mail to others, is there a way to automatically consider these addresses whitelisted?