efa-project.org

First off, great product; if I can be of help with just putting this through the paces I will do so although I'm not a developer. I went through the initial config, using my LAN internal hostnames & IPs. For example, spam.mydomain.local, 192.168.xxx.xxx

The problem I'm seeing now is that when I sent myself a test email I received the following NDR back:

This is the mail system at host spam.mydomain.local.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

The mail system

<username@mydomain.com>: host internalserver.mydomain.local[192.168.xxx.xxx] said: 530 5.7.1
Client was not authenticated (in reply to MAIL FROM command)

Final-Recipient: rfc822; username@mydomain.com
Original-Recipient: rfc822;username@mydomain.com
Action: failed
Status: 5.7.1
Remote-MTA: dns; internalserver.mydomain.local
Diagnostic-Code: smtp; 530 5.7.1 Client was not authenticated

I see two issues, 1)how do I not have the appliance contain my internal LAN settings but rather external FQDNs & IPs AND 2)why would my Exchange server not allow mail from this appliance? Is it any different from being forwarded through my firewall?

Thanks!

Ryan

the answers depend on your local network infrastructure so we can't really answer that.

if you use NAT and port forwards make sure you forwarded ports 25 and 80 to your E.F.A. box

Also make sure you have configured all domain's (http://efa-project.org/documentation/po ... l-domains/) if that has been setup correctly your exchange server should accept the mail.

In order to point others in the right direction, make sure that your "internet receive connector" on Exchange has the SPAM Appliance's IP value in the range of acceptable machines to receive mail from. I am now processing mail. Still working on my internal machine names and IPs showing up in the headers.