Having two different SMTP servers for a domain

I have a domain which uses Amazon SES for sending transactional and marketing email. For human emails (i.e my personal address on the domain) I want to use a normal SMTP server I run on one of my servers.

I have SPF, Sender ID and DKIM configured on the domain for Amazon SES but I'm not sure how to add in my own SMTP servers DKIM configuration. Do I just add another DKIM records and the receiving server will pick the correct DKIM record or do I need to specify something else in addition to that?

7 Replies

@Cromulent:

…marketing email…

Spam. We don't want to help you do anything that's going to get the same netblocks we use on a spam blacklist.

@Cromulent:

I have a domain which uses Amazon SES for sending transactional and marketing email. For human emails (i.e my personal address on the domain) I want to use a normal SMTP server I run on one of my servers.

I have SPF, Sender ID and DKIM configured on the domain for Amazon SES but I'm not sure how to add in my own SMTP servers DKIM configuration. Do I just add another DKIM records and the receiving server will pick the correct DKIM record or do I need to specify something else in addition to that?

The DKIM records themselves go into DNS, so it's not on any server at all except your nameservers.

You'll need software that can sign emails on the SMTP server you'll install on your Linode. I use OpenDKIM, but there are others. You can configure a key per domain and other tidbits like this. Then your MTA needs to talk to your OpenDKIM instance so that it can sign the email.

There are plenty of tutorials on how to do this online, it really depends on what mail stack you use.

Here's one for OpenDKIM and Postfix: https://help.ubuntu.com/community/Postfix/DKIM

The receiving server will query DNS to find your DKIM record, and then do something to validate that the DKIM signature in the email headers.

@sednet:

@Cromulent:

…marketing email…

Spam. We don't want to help you do anything that's going to get the same netblocks we use on a spam blacklist.

If you had read my original post you'd see that I sent my marketing material via Amazon SES. The Linode based SMTP server is for human to human email not automated emailing.

@Cromulent:

I sent my marketing material via Amazon SES
Ah! Helping you spam on Amazon is completely different - carry on.

@Cromulent:

I have a domain which uses Amazon SES for sending transactional and marketing email. For human emails (i.e my personal address on the domain) I want to use a normal SMTP server I run on one of my servers.

I have SPF, Sender ID and DKIM configured on the domain for Amazon SES but I'm not sure how to add in my own SMTP servers DKIM configuration. Do I just add another DKIM records and the receiving server will pick the correct DKIM record or do I need to specify something else in addition to that?

You can use different DKIM selectors for your linode based emails and ses based emails. The recipient server will pick the corresponding DNS record based on selector.

Thanks for confirming that, I didn't remember exactly how it worked and I didn't want to say something that wasn't true. :)

@vonskippy:

@Cromulent:

I sent my marketing material via Amazon SES
Ah! Helping you spam on Amazon is completely different - carry on.

Sending marketing material to people who sign up for your mailing list is completely fine. This isn't spam. In order to receive the content I am sending users have to sign up on a web page and then click a link in an email sent to that email address to confirm membership to the mailing list.

Unsubscribing from the list is as easy as sending an email to a certain address or clicking a link at the bottom of one of the mailing list emails. Please explain how this is spam.

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct