Install

General eFa discussion
Post Reply
phil57
Posts: 7
Joined: 20 Oct 2017 12:21

Install

Post by phil57 » 20 Oct 2017 12:40

Hi Guys
Hopefully someone here can help a relative novice with an install please. I previously used xeams and once set up worked well but there new pricing policy is just too heavy for a company of 3 people and 4 domains, having looked around I came across the efa project and I am hoping it will be a good solution. I have set up the efa server on a hyper v server on a local ip address (192.168.2.21) to filter the mail coming in from our pop collector and forward it to our main mail server (192.168.2.51) all was going well until the mail was received at the efa server when the smtp connection to our mail server was rejected and no mails could get through the efa server to our main mail server. I checked the log on the main mail server to find it was rejecting the connection because the efa server was trying to send all mail to a user root@sweetdreams.local (our local in house domain from our 2008r2 domain controller) log paste below. I have racked my brains (doesn't take long) and trawled for an answer, I expect its a set up issue somewhere I have gone wrong but I am at a dead end. Any help greatly appreciated.
log read out from main mail server :
192.168.2.21 [0E50] 13:18:14 <<< STARTTLS
192.168.2.21 [0E50] 13:18:14 >>> 220 2.0.0 Ready to start TLS
192.168.2.21 [0E50] 13:18:14 <<< EHLO EFA-610c.sweetdreams.local
192.168.2.21 [0E50] 13:18:14 >>> 250-sweetdreamsbeds.com Hello EFA-610c.sweetdreams.local [192.168.2.21], pleased to meet you.
250-ENHANCEDSTATUSCODES
250-SIZE
250-EXPN
250-ETRN
250-ATRN
250-DSN
250-CHECKPOINT
250-8BITMIME
250-AUTH PLAIN LOGIN DIGEST-MD5 CRAM-MD5 GSSAPI
250-VRF
192.168.2.21 [0E50] 13:18:14 <<< MAIL FROM:<> SIZE=3239
192.168.2.21 [0E50] 13:18:14 >>> 250 2.1.0 <>... Sender ok
192.168.2.21 [0E50] 13:18:14 <<< RCPT TO:<root@sweetdreams.local> ORCPT=rfc822;root@sweetdreams.local
192.168.2.21 [0E50] 13:18:14 >>> 550 5.1.1 <root@sweetdreams.local> User unknown; rejecting
192.168.2.21 [0E50] 13:18:14 <<< RSET
192.168.2.21 [0E50] 13:18:14 >>> 250 2.0.0 Reset state
192.168.2.21 [0E50] 13:18:14 <<< QUIT
192.168.2.21 [0E50] 13:18:14 >>> 221 2.0.0 sweetdreamsbeds.com closing connection
192.168.2.21 [0E50] 13:18:14 *** <> <> 0 0 00:00:00 INCOMPLETE-SESSION
192.168.2.21 [0E50] 13:18:14 Disconnected

TheGr8Wonder
Posts: 97
Joined: 01 Jul 2017 02:32

Re: Install

Post by TheGr8Wonder » 20 Oct 2017 17:41

On one of your users, you should assign the alias of "root@sweetdreams.local"

Depending on how you configured your receive connector with exchange (I'm assuming you are running exchange), either by IP or to use the default, it will only accept mail destined to authoritative domains. Depending on the volume of mails that are currently back logged, exch could be seeing that as hitting its connection limit from a single IP as well.

Make sure that your local domain is still marked as an auth domain.

phil57
Posts: 7
Joined: 20 Oct 2017 12:21

Re: Install

Post by phil57 » 20 Oct 2017 19:38

Hi
Thanks for the reply - we have an icewarp server as our main mail server which uses active directory from our 2008r2 domain controller to authenticate users. I did try creating a "root" user to accept mail which didn't work either. I wonder why the efa server forwards the emails as user root ? And not to the original email recipient. I will try adding an alias to one of the users tomorrow but does this mean they will get all email for every user.
Still a bit baffled but thanks for the help.

User avatar
shawniverson
Posts: 2782
Joined: 13 Jan 2014 23:30
Location: Rushville, Indiana, USA
Contact:

Re: Install

Post by shawniverson » 21 Oct 2017 11:54

Are those messages actually bounce notifications, and nothing is being delivered?
Version eFa 4.0.0 RC3 now available in testing repo. Come join us in advancing eFa!

phil57
Posts: 7
Joined: 20 Oct 2017 12:21

Re: Install

Post by phil57 » 21 Oct 2017 14:59

Hi
If I divert my pop collector to deliver the mail directly to my icewarp the mail gets through no problem. If I divert it through efa I get the errors and nothing gets through at all. It looks like efa is trying to deliver to root@seeetdreams.local mailbox but of course there isn't one. I wonder why the mail is not parsed through efa heading for the same mail box it was intended for ?
I still have Xeams running with no spam filtering and mail passes straight through to our mail server no problem.
Thanks for your help much appreciated, unfortunately I am a novice at how the efa mail server handles the mail.

User avatar
shawniverson
Posts: 2782
Joined: 13 Jan 2014 23:30
Location: Rushville, Indiana, USA
Contact:

Re: Install

Post by shawniverson » 21 Oct 2017 15:09

1) Do you have your mail server added to your eFa as a transport destination? Is it correct?

EFA-Configure, option 8, then option 4

2) Are you seeing the delivery issues in /var/log/maillog ? If so, can you share a sample?
Version eFa 4.0.0 RC3 now available in testing repo. Come join us in advancing eFa!

phil57
Posts: 7
Joined: 20 Oct 2017 12:21

Re: Install

Post by phil57 » 21 Oct 2017 20:55

Hi
File attachments for transport options and log file
Thanks again for all help offered
Attachments
IMG_3410.JPG
IMG_3410.JPG (724.45 KiB) Viewed 2230 times
IMG_3409.JPG
IMG_3409.JPG (582.41 KiB) Viewed 2230 times

User avatar
shawniverson
Posts: 2782
Joined: 13 Jan 2014 23:30
Location: Rushville, Indiana, USA
Contact:

Re: Install

Post by shawniverson » 21 Oct 2017 22:36

Yeah, it appears it is attempting to deliver a message to "clam@sweetdreams.local" which your mail server rejects, then it attempts to deliver an undeliverable to "root@sweetdreams.local" (the from) which also doesn't exist either and is rejected.

What happens if you send a message to an existing user on your mail system?
Version eFa 4.0.0 RC3 now available in testing repo. Come join us in advancing eFa!

phil57
Posts: 7
Joined: 20 Oct 2017 12:21

Re: Install

Post by phil57 » 22 Oct 2017 07:46

Hi
I think the clam email is efa generated. it looks like for some reason efa turns every email coming through into a root@sweetdreams.local intended recipient instead of the original recipient. I am struggling to send an email insternally via the mail server as our mail server is designed to recognize internal emails and deliver them directly to the inbox. Not knowing enough about how the efa server parses emails and how it changes the recipients is leading me to a dead end. I retried the xeams server again today directing all emails from our pop collector via xeams to our mail server and all emails cames straight through no problem so the transport network seems ok at least.
Thanks for all your help

TheGr8Wonder
Posts: 97
Joined: 01 Jul 2017 02:32

Re: Install

Post by TheGr8Wonder » 22 Oct 2017 13:03

Just sent you an email via the forum. If you dont know how to reply to it (some folks get confused), just shoot me a PM back.

User avatar
shawniverson
Posts: 2782
Joined: 13 Jan 2014 23:30
Location: Rushville, Indiana, USA
Contact:

Re: Install

Post by shawniverson » 22 Oct 2017 16:54

phil57 wrote:
22 Oct 2017 07:46
Hi
I think the clam email is efa generated. it looks like for some reason efa turns every email coming through into a root@sweetdreams.local intended recipient instead of the original recipient. I am struggling to send an email insternally via the mail server as our mail server is designed to recognize internal emails and deliver them directly to the inbox. Not knowing enough about how the efa server parses emails and how it changes the recipients is leading me to a dead end. I retried the xeams server again today directing all emails from our pop collector via xeams to our mail server and all emails cames straight through no problem so the transport network seems ok at least.
Thanks for all your help
Can you provide a maillog of the initial conversation to a recipient? So far I cannot observe this actually happening, based on the logs screenshots your are providing. I am not even sure that your setup is actually relaying anything to the appliance, for unknown reasons. I need to see an actual connection from your pop collector to eFa. Now, the bounces you shared are going to your mailserver because both your eFa and mail server have the same domain name, so postfix is using the transport to deliver to your mailserver instead of local linux accounts on the system. Simply changing the domain name of your eFa can resolve that. But again, those emails are system messages, not actual emails going through the system.
Version eFa 4.0.0 RC3 now available in testing repo. Come join us in advancing eFa!

phil57
Posts: 7
Joined: 20 Oct 2017 12:21

Re: Install

Post by phil57 » 23 Oct 2017 15:00

PM Sent

Post Reply