Sending Emails On Behalf Of

Posted on

Sending Emails On Behalf Of – In many cases you will want to send us on behalf of your customers. For example, if you use help desk software but want to use Postmark to support your emails, you can set up all the authentication you need for your domain, but your customers will probably prefer their brand, customerdomain to see. .com instead of you.

Watch our webinar recording that covers everything you need to know about sending on behalf of your users.

Sending Emails On Behalf Of

Sending Emails On Behalf Of

If you ship on behalf of your customers, you have several options that vary in both technical complexity and effort. In this guide, we’ll explore the pros and cons of each of these approaches at a high level, then show you how a hypothetical help desk company could use Postmark to implement each shipping tactic. API endpoints and requests vary by ESP, but the interface and concepts should remain the same.

Examples Of Use

Before we dive in, here’s a quick overview of the pros and cons of each option when looking to postmark on behalf of your clients.

In an ideal world, every shipment on behalf of your customers will use the customer’s domain with fully aligned authentication. This includes DKIM and SPF/return path. However, your customers aren’t always comfortable with changing DNS, or in some cases can’t add their company’s DNS records. Another challenge with this approach is that it requires either significant development effort or significant manual intervention to set up authentication for each client’s domain. While domain authentication does not guarantee delivery, it increases your customers’ chances of reliable delivery.

If your customer cannot fully authenticate their domain to send with your service, you can still send from their email address. However, without authentication, some email clients such as Gmail and Outlook display “via” or “with” tags along with the sending address. Although Postmark offers this option, it is not available with all email providers.

However, during this process, you’ll want to confirm that your customer verifies the sender address you’re using. To do this, you must use a verification process to send an email to this address and have the user follow a link to confirm ownership or use a one-time code sent to this email address. With Postmark it is included. Postmark sends a confirmation email to this address with a link that the recipient can click to confirm ownership.

Send An Email On Behalf Of Your Teammates

The last option is the easiest in terms of both your and your customer’s configuration efforts. You can send emails from your own domain and simply specify a different “From” name when sending an email. You can also potentially set up unique email addresses for each customer. For example, you can use

With this approach, it is worth keeping in mind that some email clients aggressively add new contacts to the address book, and someone may inadvertently be added to the address book with the wrong email address associated with their name. One solution is to update the name to say “Jane Client via (seller)” to make it clear that this is not the sender’s primary email address.

We’ll look at how the shipping setup process should work for your customers, and we’ll also discuss how the process can educate them to make the best decisions for their situation. What can you do if your client is unfamiliar with DNS or doesn’t feel comfortable making changes to their company’s DNS settings? There’s a lot of room for error, so let’s break it down into a simple process.

Sending Emails On Behalf Of

What all options have in common is that you want to create a server for each client in Postmark. It allows you to organize statistics and e-mail streams from the client. Not all ESPs offer the concept of servers, but you can think of them mainly as organizational concepts so that your different clients do not mix up their emails. It’s completely optional, but it’s helpful.

Solved: Send Email From Someone Else

You can offer all three options to your customers, or you can limit the choices. In any case, you should provide guidance on the pros and cons of why they want to use the option or not.

Having a customer authenticate their domain so you can send emails using their domain is a great solution, but it’s also the most technical challenge for you and your customers. It is also believed that they have the ability to make DNS changes.

Although it is the most difficult to build and configure, it is the best overall process for customers who have switched to hosting their own domain.

To get an idea of ​​what is involved in providing DNS configuration instructions to customers, visit the “Sender Signatures” section of your Postmark account and add a new domain.

Untangling Email: Spf, Dkim, & Dmarc

Confirmed sender address isn’t the smoothest user experience, but it’s much easier to set up. This only requires that your customer has the ability to check emails on the desired sender address. Then, when you use the Postmark API to create a sender signature for that address, Postmark will automatically send a confirmation email to that address.

Without authenticating customer domains, the workflow is a little easier, but your customers’ emails will show via tags in Gmail.

If you are sending emails on behalf of your clients and using their domain, the best way for them is to set up DKIM, SPF and backpaths to authenticate and verify the ownership of your domain. Since it is not always easy or possible for customers to make changes to their company’s DNS, you may want to consider sending from the customer’s domain without authentication. Although this is possible, it has some disadvantages.

Sending Emails On Behalf Of

This approach ensures that they have a verified email address and should be allowed to send emails, but it is

Shared Email Addresses For User Groups

It works. Sending on behalf of users without fully configured authentication for the sending domain can lead to situations where some email clients and services show that the sender’s address is being sent on behalf of or via an email service provider. To ensure that the authentication is fully aligned, the authenticated domain must match the From address domain.

Without fully aligned authentication, emails can appear unprofessional at best or unreliable at worst. Ideally, to send on behalf of your customers, you want to more than simply verify domain ownership and start authenticating your custom domain, encouraging them to set up DKIM and SPF/return paths.

This is the easiest and most convenient method for everyone, but it also means that your customers do not use their own domain. This is a great way to start with your first version because it is always relevant. Keep in mind that if someone signs up for your service to try it out, they may not be comfortable setting up DNS authentication right away. Giving them a quick and easy way to test it out before they fully commit can really help make your service more accessible.

Changing the display name requires the least effort, but the underlying email address still uses your domain, not your customers.

Batch Emailing Overview

The answer, of course, is that it depends on your priorities. Each of these options has significantly different advantages. If control over your brand is important to your customers, you may want to focus on full authentication for your customers’ domains. However, if your customers tend to be less technical, a simpler process with fewer steps is probably the right move. There are quite a few variables to consider.

An important thing to remember is that you can always start simple and expand over time. With the first version, you can simply offer an option and then wait to see what your customers are most interested in. You need to weigh your options and choose the one that best suits your goals. Any B2B SaaS platform that caters to users to deliver email messages to their customers will eventually have this question.

I just want my brand to be promoted, users need to think your emails are from us, can you do that?

Sending Emails On Behalf Of

, all emails we currently send are sent from SMTP server, but signed through our domain

How To Send Email On Behalf Of Someone Else

E-mail address, it appears to the user that our e-mails come directly from our servers. But when we try to send an email FROM

The email will still be sent, but it will trigger all email spoofing warnings in almost all email clients. And nobody wants that because it hurts your reputation and ultimately your performance.

There are many different methods a developer can use to implement this, and some email services or APIs do the heavy lifting for you (Wink Mailgun), but you have to weigh the pros and cons. Here I focus on Amazon SES due to its increasing traction due to its reliability and low prices.

SES lets you do just that

How Signatures Are Added To Emails Sent As / Sent On Behalf Of Other Users

Sending emails on friday, hotmail not sending emails on android, sending email on behalf of boss sample, sending an email on behalf of someone else example, sending email on behalf of, sending an email on behalf of your boss example, linkedin sending messages on my behalf, gmail limit on sending emails, sending email on behalf of someone example, sending emails on behalf of someone else, sending email on behalf of someone, sending group emails on iphone