efa-project.org

For incoming, or outgoing mail?

You're still providing no specific information and no one can help you until you do.

So, if you want to receive the spam, then you need to disable the use of the RBL. Instead, use the RBLs inside spamassassin so they get a score instead of being blocked.

Any spam that gets delivered and is not scored properly can use used to train the bayesian filter.

- disable the use of the RBL ...

I want it to go to the junk box

Can you tell me what you mean by that?

EFA will mark a message as one of three things:
Not Spam (pass it through)
Spam (might be spam, but might not be)
High Spam (definitely spam)


What your system does with the different types is configurable.

On my system ...

Not enough information.

Where are you seeing this error? Is it from the sending or receiving side? Can you provide any more information than just that single line?

Huh. I didn't realize that option was there in Mailscanner.conf!

Let me investigate further.

Question: How are you using the RBLs?

Are you using it at the postfix level? or at the spamassassin level?

If it is done by postfix, the mail will immediately be rejected and no message will be received.

If it is done by spamassassin, then you will have a record and a spamscore addition added to ...

Welcome!

Can you show me the spamassassin rule hit you are getting that causes the emails to be flagged as spam?

In my installation, I have two rules containing the string SORBS and they are
1/ RCVD_IN_SORBS_DUL
2/ RCVD_IN_SORBS_WEB

Letsencrypt will leave log files telling you what went wrong. Find them, and you will find your answer.

[user@efa4 MailScanner]# grep "No programs allowed" *.conf
archives.filetype.rules.conf:#deny executable No executables No programs allowed
archives.filetype.rules.conf:#deny ELF No executables No programs allowed
filetype.rules.conf:#deny executable No executables No programs allowed
filetype ...

Sorry for the delay in getting back to you.

The messages you sent me passed into my system without any trouble at all and I cannot yet figure out why you can't get the messages but I can.

You need to provide the spamassassin headers so we can work out why this message is being marked as spam.

Looks like this will do the trick: https://github.com/E-F-A/v4/blob/master/rpmbuild/SOURCES/eFa-base-4.0.0/mariadb/bayes_mysql.sql

CREATE TABLE bayes_token (
id int(11) NOT NULL default '0',
token binary(5) NOT NULL default '',
spam_count int(11) NOT NULL default '0',
ham_count int(11) NOT ...

If the document says 1 domain per line, then that's that.

Until the configuration UI is changed to support multiple IPs per domain in the transport file, you'll have to maintain it by hand.

Just a wild guess, but would this work in your transport file instead? The proper solution is to allow the efa configuration to support multiple destinations correctly. That should be an enhancement request for Shawn.

Sorry for the delay.

Can you tell me what your host OS is, what database you are using and what version of EFA you are running?

I'll need to find the correct SQL creation command from the installer as I don't want to guess and give you the wrong command.

Do you have a backup?

If not, then you will need to recreate the related tables, make sure they are in innodb format and then repopulate the tables by retraining your bayes filter with known spam.

Good luck!

Feel free to convert it to InnoDB. It will do no harm.

Any luck setting it up?

It should be just as those instructions describe.

You'll need to post some headers of messages where the rules were not applied.

I added the following rules into /etc/mail/spamassassin/local.cf
header ZZ_GMAIL_TEST From =~ /\@gmail\.com/i
score ZZ_GMAIL_TEST -0.01
describe ZZ_GMAIL_TEST gmail scoring test using local.cf

I don't know if it ...

AITCS wrote: 30 Aug 2022 11:45It took about 4 months for someone to realise the regex was malformed, so I don't think they're losing anything valuable at this stage.

Good to hear you found a solution.

Another way to have handled it would have been to add a .biz handling rule to the spamassassin local.cf to give .biz domains a bump up in spam score.

That way if a message really did come through that was legitimate, you could train the system to recognize it ...

I think it's time for me to add another domain into the dkim pool. I'll let you know if your notes are better than my half arsed, hodgepodge collection of notes and half remembered things.

Weird.

Thanks for letting us know the fix. It'll be useful in case it ever happens to someone else.