search

haraka / Haraka

A fast, highly extensible, and event driven SMTP server
https://haraka.github.io
MIT License
5.02k stars 662 forks source link

Forwarding question #1451

Closed enmartinson closed 8 years ago

enmartinson commented 8 years ago

I'm looking to move from a surgemail system to haraka for our email relaying, but am having a bit of confusion about configuring forwarding, hopefully someone can point me in the right direction. We have roughly 850 email addresses across ~400 domains that come in to us, then are forwarded to their corporate accounts through 5 potential relays based on the email address (almost all our email goes through sendgrid). An few examples would be:

info@site1.com -> forwarded to dave@client1.com and susie@client1.com through sendgrid office@site1.com -> forwarded to alice@client1.com through sendgrid sales @site2.com -> forwarded to sales@client2.com through gmail webmaster, abuse + support @all sites -> forwarded to our webmaster, abuse and support email addresses through gmail (but can go through sendgrid)

We only want to accept those addresses specifically setup and drop all the rest.

I see setting up the rcpt_to.routes.ini file for the mx server, but I don't see where I can specify the exact email addresses and their forwards (aliases?). It's quite possible I've been looking at this so long it's right in front of me. Maybe someone has an adjusted rcpt_to plugin that incorporates this?

I also need to be able to manage these with a web front end, so putting them in a database would be best, our internal support has to update from time to time. Any guidance would be appreciated.

Dexus commented 8 years ago

Hey, please have a look to aliases.

Am 09.05.2016 um 23:16 schrieb enmartinson notifications@github.com:

I'm looking to move from a surgemail system to haraka for our email relaying, but am having a bit of confusion about configuring forwarding, hopefully someone can point me in the right direction. We have roughly 850 email addresses across ~400 domains that come in to us, then are forwarded to their corporate accounts through 5 potential relays based on the email address (almost all our email goes through sendgrid). An few examples would be:

info@site1.com -> forwarded to dave@client1.com and susie@client1.com through sendgrid office@site1.com -> forwarded to alice@client1.com through sendgrid sales @site2.com -> forwarded to sales@client2.com through gmail webmaster, abuse + support @all sites -> forwarded to our webmaster, abuse and support email addresses through gmail (but can go through sendgrid)

We only want to accept those addresses specifically setup and drop all the rest.

I see setting up the rcpt_to.routes.ini file for the mx server, but I don't see where I can specify the exact email addresses and their forwards (aliases?). It's quite possible I've been looking at this so long it's right in front of me. Maybe someone has an adjusted rcpt_to plugin that incorporates this?

I also need to be able to manage these with a web front end, so putting them in a database would be best, our internal support has to update from time to time. Any guidance would be appreciated.

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub

enmartinson commented 8 years ago

This setup is FAR from clear. I can't seem to get aliases to register no matter what I try, and the documentation isn't helping. I don't see any errors in the logs or on the console, not sure how to get this working.

Here's my plugins config, is there anything in here that would be stopping aliases from starting?

watch
aliases
relay
access
connect.p0f
connect.geoip
connect.fcrdns
dnsbl
early_talker
helo.checks
tls
auth/flat_file
mail_from.is_resolvable
spf
rcpt_to.in_host_list
bounce
data.headers
data.uribl
clamd
spamassassin
dkim_verify
karma
queue/smtp_forward
max_unrecognized_commands
enmartinson commented 8 years ago

Damn. Nevermind. Looks like the node install only looks at the files it installed regardless of the configs you specify when starting up. I have configs in /etc/haraka, but the install put everything in /usr/lib/node_modules/Haraka and doesn't care if you specify a different location. I added the aliases link in that plugins file and it at least fired up.

This looks to be a bug in this type of install.

baudehlo commented 8 years ago

I literally just release 2.8.4 which should fix this problem. Please let me know if it helps.

On Tue, May 24, 2016 at 8:05 PM, enmartinson notifications@github.com wrote:

Damn. Nevermind. Looks like the node install only looks at the files it installed regardless of the configs you specify when starting up. I have configs in /etc/haraka, but the install put everything in /usr/lib/node_modules/Haraka and doesn't care if you specify a different location. I added the aliases link in that plugins file and it at least fired up.

This looks to be a bug in this type of install.

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/haraka/Haraka/issues/1451#issuecomment-221437984

enmartinson commented 8 years ago

Yep, that fixed it... was just in process of moving my configs to the other directory - Thanks!