efa-project.org

There is a spamassassin results cache database in MailScanner. You can

sudo rm /var/spool/MailScanner/incoming/SpamAssassin.cache.db

and

Code: Select all

sudo systemctl restart mailscanner

to reset it.

You can add the bank's domain to /etc/sqlgrey/clients_fqdn_whitelist.local and run

Code: Select all

sudo update_sqlgrey_config

Thank you for bringing this to my attention. I will drop this configuration from postfix for new installations since it is not recommended. For existing installations I'll see if I can add the return code range to the definition.

Are you releasing this message to your mailserver or to someone out on the Internet?

:text-welcomewave: If you use two of them you get the added flexibility of customizing your inbound and outbound filtering separately and not have to worry about making your customizations distinguish between inbound and outbound mail flows. On the other hand, you would have to manage two boxes, so ...

This is expected behavior.

I looked at the queue logic in MailWatch and can't figure out how you are getting this warning.

In /etc/MailScanner/MailScanner.conf, what is the value for the following:

MTA
Incoming Queue Dir
Outgoing Queue Dir

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

MS_CONFIG_DIR

This could be MailWatch trying to monitor the queues, but I'm not sure why it would be trying to use sendmail for that. Does it only log when the MailWatch UI is open for about every 30 seconds?

Yes, you can. What you need is a ruleset. Create a new file in /etc/MailScanner/rules such as spamactions.rules Define your rules in the file, using tabs to separate fields. Be sure to look at your Spam Actions setting in MailScanner.conf to see what parameters you are using in case you need to put ...

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

Code: Select all

define('QUARANTINE_MSG_BODY', 'Please find the original message that was quarantined attached to this mail.

Regards,
Postmaster');

I'd like to know how "hash:/etc/postfix/transport" ended up here.

mynetworks is initialized out of the box as:

eFa-base-5.0.0-1.eFa.el9.noarch
postfix-config-5.0.0.sh, line 35:

Code: Select all

postconf -e "mynetworks = 127.0.0.0/8 [::1]/128"

Delete the file, should go away.

Please test the following:

Change the following line in /etc/mail/spamassassin/mailscanner.cf:

From:

Code: Select all

bayes_store_module               Mail::SpamAssassin::BayesStore::SQL

To:

Code: Select all

bayes_store_module               Mail::SpamAssassin::BayesStore::MySQL

Report back results.

I am able to reproduce the same behavior. sudo su - postfix -s /bin/sh -c "spamassassin -D bayes -t < /var/spool/MailScanner/quarantine/20241110/spam/4XmZWK3SLgzcDDsV" Run #1 Nov 11 21:38:24.182 [2892651] dbg: bayes: tokenized header: 62 tokens Nov 11 21:38:24.183 [2892651] dbg: bayes: tok...

Given that bayes is doing this unpredictable behaviour for you it is essentially unreliable and useless. I am going to populate bayes and try to reproduce the same behaviour on my end to continue troubleshooting with you. I reached out for help from spamassassin on IRC and they want us to: 1) Try ba...

Uhhhh.... :crazy: :crazy: :crazy: :crazy: Do me a favor, can you temporarily disable SELinux and run some more tests? Can you confirm that bayes autolearning is off in the context of the postfix user? (see below) Do you have a /etc/MailScanner/spamassassin.conf that is a regular file and has a valid...

This is pretty much it.

Yeah, if you change the cron job, you'll have to be mindful that an update to MailWatch could potentially add the default cron job back to cron.daily.

What happens if you execute spamassassin as the user that MailScanner runs as?

Code: Select all

sudo su - postfix -s /bin/sh -c "spamassassin -D -t < msg"

To ways to potentially resolve. One is to remove the recipient address validation cache. (best) sudo mv /var/lib/postfix/verify_cache.db /var/lib/postifx/verify_cache.db.bak Another is to disable recipient address verification using eFa-Configure (under mail settings) or adjusting the postfix main.c...

This option enables validation via opendkim and opendmarc. Enabling signing for opendkim requires additional setup.

Setup should be the same as in previous versions, so those posts should still apply.

https://github.com/E-F-A/eFa5/issues/24

You should get to eFa4 first...

Looks like appstream was moved to vault.

Give this a try:

https://medium.com/@bonguides25/fixed-f ... 1ad6db8f16

You are getting a service unavailable. Is your milter functioning properly? msmilter must be running and available on port 33333.

Sounds like you have a mail loop occurring in that direction somehow. I'm not sure why with the information you provided. You may need to check your /etc/postfix/transport file and see if it makes sense for both servers.

This is not one of the roles that MailWatch has out of the box.

It is possible to make MailWatch do this, but it will require some modification.

I think this would make a good feature request for MailWatch.

efa-project.org

Search found 3783 matches

Re: Spamassassin local.cf ignored

Re: Greylist vs banking auth code

Re: EFA's incorrect handling of zen.spamhaus.org

Re: Release: error (Failed to send data [SMTP: Invalid response code received from server (code: 554, response: 5.7.1 Me

Re: Howdy

Re: Quarantine email - View Links

Re: postfix chdir permission denied

Re: postfix chdir permission denied

Re: Only send spam notifications to specific domain

Re: Edit release message

Re: Postfix mynetworks default setting

Re: Anacron Job error: gzip: /etc/MailScanner/phishing.safe.sites.conf.master.gz: unexpected end of file

Re: eFa v5 bayes behaviour

Re: eFa v5 bayes behaviour

Re: eFa v5 bayes behaviour

Re: eFa v5 bayes behaviour

Re: Daily Quarantine Report Timing

Re: eFa v5 bayes behaviour

Re: Problem with transport

Re: V5 - 16) DKIM and DMARC

Re: Fail2ban does not start initially

Re: efa3 to efa4

Re: Connection Refused

Re: same antispam problem

Re: Restricted administrator account for email quarantine access