Outgoing email configuration

Junior Member
Posts: 5
Joined: Sun Jun 01, 2014 9:57 pm

Outgoing email configuration

Postby chrisk » Mon Jun 02, 2014 1:33 pm

Good Day!

How should outgoing emails be configured through eWall?

We setup our mail server to use the eWall proxy as an outgoing mail relay. Outgoing mails are delivered after several minutes, but looking through the SMTP header shows many local loops before the mails are delivered.

We're eager for this - as your feature (with the filter) to automatically add domains sent-to to the 'Good' list is very attractive.

Thanks,

Chris

Developer
User avatar
Posts: 4431
Joined: Tue Apr 20, 2004 3:43 pm

Re: Outgoing email configuration

Postby Alexander Telegin » Mon Jun 02, 2014 3:53 pm

eWall is primary designed to filter incoming emails. Working in relay mode is an additional option that was added later and this mode is not recommended. Ideally scenario is to let eWall work in direct mode, filter spam, and let your mail server's MTA forward emails to the target recipient (or store for local user).

Junior Member
Posts: 5
Joined: Sun Jun 01, 2014 9:57 pm

Re: Outgoing email configuration

Postby chrisk » Mon Jun 02, 2014 6:31 pm

Wow! Thanks for the lightning fast response!

Makes sense.

Accordingly, how can we configure eWall to auto-white list domains we send to? Or is this not available, given the recommended deployment scenario?

Chris

Developer
User avatar
Posts: 4431
Joined: Tue Apr 20, 2004 3:43 pm

Re: Outgoing email configuration

Postby Alexander Telegin » Mon Jun 02, 2014 9:08 pm

There's a repository filter, that autowhitelists recipients (accounts, not domains), if session was successfully authenticated. So, when that account sends back the email passthrough. I think this is what you mean. If whitelisting domains instead of accounts is critical, that filter's code can be modified.

Junior Member
Posts: 5
Joined: Sun Jun 01, 2014 9:57 pm

Re: Outgoing email configuration

Postby chrisk » Thu Jun 05, 2014 8:23 pm

Thanks!

Yes; exactly.

Here's an example:

Local mail server sends an email to YYY@Domain.com

Since we've initiated the correspondence with someone @Domain.com, we would like to assume that they are legitimate - and whitelist their domain for future incoming emails.

Can you provide PHP (etc) code for this to update the filter?

Also, since the filter is only receiving incoming (untrusted) emails, how does it know that this is indeed a return email? You use the word 'authenticated' in your first response below - but I do not understand when/where any authentication occurs. eWall appears to be referencing the 'local users' list (which is fine) - but how will it know that the email is a valid reply to an email generated by a local user - if the outbound emails dont flow through eWall?

Thanks!

Chris

Developer
User avatar
Posts: 4431
Joined: Tue Apr 20, 2004 3:43 pm

Re: Outgoing email configuration

Postby Alexander Telegin » Fri Jun 06, 2014 5:48 am

Chris, eWall compares sender/recipients against own list of local domains/accounts. If sender's domain is local, this email is considering as outgoing. If it's successfully authenticated with mail server, eWall trust is alot and adds recipients to the good list. Next time when they send back to local address, eWall trust them and pass through.

I wouldn't recommend whitelist as there could be a problem with public mail services, e.g. whitelisted "gmail.com" will open hole for all Gmail accounts.

Return to General

Who is online

Users browsing this forum: No registered users and 2 guests