efa-project.org

There you go. The problem is that their mail server is not responding. That could be for many reasons, but the main reason is not EFA in this case. - Paul PS: if the mail remains in the queue for a long period, the sender should eventually be notified that the message cannot be delivered, or is dela...

It will have more information than that. For example, I currently have one message in the queue. connect to mail-sunshine.com[204.11.56.48]:25: Connection timed out What does yours show? Are all the hosts the same? Or are all the queued messages going to the same host? Try pinging the hosts. Are the...

I also need to figure out how to turn off the "{Spam Not Delivered}" email notifications. I assume these settings are in the mail watch web interface which I can no longer get admin access to. Any thoughts? Thank you! Look in /etc/MailScanner/MailScanner.conf. You'll need to be a root user to edit ...

What is ispconfig and what product is it from?

Do you mean http://www.ispconfig.org/page/home.html? If so, you'd be better off asking the question in their public forums (https://www.howtoforge.com/community/#ispconfig-3.23)

If you're comfortable using the command line, you can use the "mailq" command after logging into the EFA management account and accessing the Shell.

That will give you the same information.

You need to find out why the mail is queued up. What I do is check the mailq using Webmin https://<your efa hostname>:10000/ and login using the root account. Select "Servers, Postfix Mail Server" from the left hand side. Select "Mail Queue" on the right hand side. The "Status" column will tell you ...

But that would be a simple and logical solution. Why would I want to do something smart like that?*


*(translation: such an obvious idea, it didn't even occur to me)

Maybe, I haven't checked that.

However the DKIM rules means that if someone sends mail to mydomain.com that is not an authorized mail server for the domain means it is likely to get junked, so I'm not too worried about it.

It certainly hasn't been a problem so far.

I'm not sure I follow you. All my internal domains for which EFA handles mail for only whitelists outgoing mail, not incoming mail. e.g. mydomain.com With the above rule: - someone sending mail from mydomain.com through EFA to the outside world does not get spam checked - someone sending mail to myd...

Try the combination you used during the initial configuration.

Because you have to add it into your local.cf file yourself.
You can score it more or less according to your preference.

Ah, I understand. Then I am not sure. All I know is that once I whitelisted my internal domain, all spam checking stopped. My settings: Lists / Add to Whitelist from: mydomain.com to: <left it blank> @ <left it blank> and then clicked "add". It shows up in the whitelist as: From: mydomain.com To: de...

find an outgoing that was marked as spam in the message listing

when you view the message details, you should see the spam assassin score breakdown

can you post the break down for 2 or 3 messages? let see if spam assassin will tell us why it thinks it is spam

[root@efa ~]# cd /var/lib/spamassassin/ [root@efa spamassassin]# grep -R FREEMAIL_FORGED_REPLYTO * 3.004000/updates_spamassassin_org/30_text_pt_br.cf:lang pt_BR describe FREEMAIL_FORGED_REPLYTO Email gratuito usado no Reply-To, mas n▒o no From: 3.004000/updates_spamassassin_org/50_scores.cf:score F...

Sure, but you'll have to provide more information. First question: Where are the messages being marked as spam? By your EFA appliance, or by the remote mail systems? If it's the former, the problem should be simple to fix. If it's the latter, you'll need a full spam report from the receiving systems...

That's a good question. I've a similar configuration, with the Exchange users whitelisted to prevent their messages from getting quarantined. Typically, when users get infected with a program that sends junk, the malware tries to send mail directly. Since I block all outgoing mail except from the ef...

This is all handled by the postfix configuration in EFA. Specifically, if I look in /etc/postfix/main.cf, I can see the following options are set smtpd_helo_restrictions = check_helo_access hash:/etc/postfix/helo_access, reject_invalid_hostname smtpd_sender_restrictions = permit_sasl_authenticated, ...

Look here for instructions on setting the # of days to keep the Archive/Audit/Quarantine messages.

Don't forget to test "releasing" the message to see if it will get sent correctly.

header MCP_TEST2 To: =~ /pdwtest\@ddguidelines.com/i describe MCP_TEST2 testing header To checking score MCP_TEST2 10 You have to "escape" the @ symbol in order to get the match to work correctly. That's why it didn't work for you initially (or for me :D ) Remember this rule only works for "To:" It...

ok, that's good news. It means MCP is working.

All we have to do is figure out a correct rule for handling "To:" in the header.

Give me a few minutes to test this.

ok, so we need to diagnose the problem. Did you reload MailScanner after changing the rules? What file did you edit and put your rules into? Can you create a rule using just the subject (like my example above) and see if that triggers MCP? We need to figure out where it is failing before we can fix ...

it looks ok.

test it, see if messages to all@domain.com are quarantined properly.

testing will only take a couple of minutes

Thanks for the info.

I'll delete it from my system now.

(I prefer using vim to edit the configuration file anyway)

https://sourceforge.net/projects/msfron ... p_redirect

Is this of any use? It seems to provide a "gui" for editing the MailScanner.conf file and to control the MailScanner process. It seems to work, but the code hasn't been touched in quite a few years.