efa-project.org

Posted: **31 Aug 2017 18:32**

Dear all,
we are using the EFA for over a week now really happy with the performace and spam catch.
emais are arriving fine with 3 domains, our Exchange is a multiple domain hosting.
Today we have added the latest domain to the exchange and EFA however the emails are not arriving.
the log eror shows

Code: Select all

Aug 31 20:22:03 filter postfix/smtpd[2965]: NOQUEUE: reject: RCPT from mail-oln040092069083.outbound.protection.outlook.com[40.92.69.83]: 454 4.7.1 <info@domain2.com>: Relay access denied; from=<julien.nl@hotmail.com> to=<info@domain2.com> proto=ESMTP helo=<EUR02-VE1-obe.outbound.protection.outlook.com>
Aug 31 20:22:03 filter postfix/smtpd[2965]: disconnect from mail-oln040092069083.outbound.protection.outlook.com[40.92.69.83] ehlo=2 starttls=1 mail=1 rcpt=0/1 quit=1 commands=5/6
Aug 31 20:22:16 filter postfix/smtpd[2965]: connect from mail-oln040092066105.outbound.protection.outlook.com[40.92.66.105]
Aug 31 20:22:16 filter postfix/smtpd[2965]: Anonymous TLS connection established from mail-oln040092066105.outbound.protection.outlook.com[40.92.66.105]: TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)
Aug 31 20:22:16 filter postfix/smtpd[2965]: NOQUEUE: reject: RCPT from mail-oln040092066105.outbound.protection.outlook.com[40.92.66.105]: 454 4.7.1 <info@domain2.com>: Relay access denied; from=<julien.nl@hotmail.com> to=<info@domain2.com> proto=ESMTP helo=<EUR01-VE1-obe.outbound.protection.outlook.com>
Aug 31 20:22:16 filter postfix/smtpd[2965]: disconnect from mail-oln040092066105.outbound.protection.outlook.com[40.92.66.105] ehlo=2 starttls=1 mail=1 rcpt=0/1 quit=1 commands=5/6

Code: Select all

Aug 31 20:08:17 filter postfix/trivial-rewrite[14328]: warning: database /etc/postfix/transport.db is older than source file /etc/postfix/transport Aug 31 20:08:17 filter postfix/trivial-rewrite[14328]: warning: database /etc/postfix/transport.db is older than source file /etc/postfix/transport Aug 31 20:08:17 filter postfix/smtpd[13036]: NOQUEUE: reject: RCPT from mail-eopbgr40103.outbound.protection.outlook.com[40.107.4.103]: 454 4.7.1 <info@doman1.com>: Relay acc

we can send with this domain but not recieved .
please advies

Posted: **01 Sep 2017 02:09**

Re-check your efa settings to ensure you've configured efa to accept mail for this domain and forward it to your exchange server.

Re-check your exchange transport setting, just in case.

I don't know if you need to restart mailscanner after adding a new domain, but it cannot hurt.

Let me know if it makes any difference.

Posted: **01 Sep 2017 02:15**

Sorry, on a mobile phone at the moment so it's hard to read your log files.

The key line is regarding the transport file being out of date. You need to rebuild the transport database file from the updated transport file so postfix knows about the new domain.

If you used the efa interface to add in the new domain, that should have happened automatically. In your case, this step hasn't happened.

When i get to a computer, I'll give you the command line version of how to rebuild the transport database so you can do it manually if necessary.

(Or someone may post the command here before I get to a computer - hint hint!)

Posted: **01 Sep 2017 03:31**

I believe you want to SSH in, shell and then;

Code: Select all

sudo postmap /etc/postfix/transport
sudo service postfix restart

Posted: **01 Sep 2017 03:52**

Thank you Jase72, that will indeed do the trick. Much appreciated.

Jamerson, you'll know it worked when you no longer see the following error in your log file

warning: database /etc/postfix/transport.db is older than source file /etc/postfix/transport

Posted: **01 Sep 2017 07:54**

Thank you guys for the support

sudo postmap /etc/postfix/transport
sudo service postfix restart
those commands has fixed the problem,
sinds we start using the EFA all our relay has stopped working,
like printers for sending the warning
servers,.....
anyway to add our subnet to the relay?

Posted: **01 Sep 2017 09:27**

In my network, my printers, network devices and whatnot all sent mail to via my exchange server (which then handed it onto efa).

How are your devices configured to send mail? Do your exchange server? or have to changed it to send it send it to EFA directly?

- Paul

Posted: **01 Sep 2017 09:51**

Hi Paul,
thank you
all devices are sending the emails through the Exchange ( mail.domain.com ) using the FQN.
we have changed it to the IP and it still not sending.
Do we have to allow the relay somehow ?

Posted: **01 Sep 2017 11:23**

Have you confirmed that Exchange is accepting the email? If your printers etc are sending direct to Exchange then I'd check there first. Enable logging on the receive connector and then check that log.

If they're sending to external recipients then you'll either need to use auth or create an anonymous relay connection. If it's just sending to internal addresses then make sure the printers are connecting to the correct receive connector (e.g. if they're not authenticating then make sure the connector they're using allows anonymous connections).

Posted: **01 Sep 2017 16:35**

What Jase72 says. If you are sending mail to exchange, you have to make sure that your exchange is configured to accept the mail from these mail clients.

Internally, I allow all devices to relay mail to exchange for example.com/example.local and my exchange server just passes it on to EFA to check.

You can use the email track and trace feature of exchange to view the connection attempts from your clients. Or enable the logging as Jase says. Track and Trace usually enough for my troubleshooting purposes.

Posted: **03 Sep 2017 21:42**

Than you guys
after I have rebooted the EFA box emails start working.
I don't know what was the issue !
is it possible whenever the EFA blocks a spam, will inform the user when it does so the user will have to allow the email or not.

Posted: **04 Sep 2017 02:28**

jamerson wrote: 03 Sep 2017 21:42 is it possible whenever the EFA blocks a spam, will inform the user when it does so the user will have to allow the email or not.

Yes, you can configure MailScanner to "notify" the recipient. If you look at /etc/MailScanner.conf and search for "What to do with spam" around line 2370, you can read what the options are.

The two relevant options are:

Code: Select all

Spam Actions = 
High Scoring Spam Actions =

My settings (for comparison) are:

Code: Select all

Spam Actions = store deliver header "X-Spam-Status:Yes"
High Scoring Spam Actions = store header "X-Spam-Status:Yes"

which means,
(1) store all spam
(2) add a header to the delivered message
(3) deliver possible spam, don't deliver stuff that is almost certainly spam.

You'd need to adjust your settings to include the "notify" for the messages you are not "deliver"-ing.

Finally, there is almost certainly a way to do this through the EFA configuration program. I almost never use it because I am too much of a command line junkie.

I think the options are (9) Spam settings, (2) Spam Settings. How exactly you change it at that point, I'm not sure since I prefer to edit the config file myself.

Posted: **07 Sep 2017 13:25**

a big thank you guys for the help,
Spammy has helped me on the chat

efa-project.org

email not arriving

email not arriving

Re: email not arriving

Re: email not arriving

Re: email not arriving

Re: email not arriving

Re: email not arriving

Re: email not arriving

Re: email not arriving

Re: email not arriving

Re: email not arriving

Re: email not arriving

Re: email not arriving

Re: email not arriving