Limitations on campaigns from non-custom email providers (such as Gmail)

Your From email address identifies you as a sender of the emails you’ve sent to your contacts. When using a non-custom email service provider, such as Gmail, Yahoo or AOL, you can be limited in terms of what you can do with that email. 

The problem arises because when you’re using a non-custom email service, you do not own the domain name. Here’s what that means for you: 

  • Non-custom email services have policies in place that limit spam and bulk sending and could inadvertently cause delivery issues and mess up your email blasts. 
  • Non-custom email addresses can’t be added to your verified email domains in PosterMyWall.

Here’s how to fix this

Option 1: Use PosterMyWall to send your emails

PosterMyWall helps you send your emails even if you’re using a free email domain by making a small change in your From email address when you send your emails. 


Add your sender email address, without any modification. We will then add the subdomain to your email and this will all be handled from our end. You don’t need to worry about doing anything. 

Here’s an example of what your email will look like with the added subdomain: 

Original email address:

Updated with PosterMyWall’s subdomain

This will ensure your emails are delivered without any error, because when receiving servers will look at your email, your From email address will be consistent with the domain the email is being sent from, i.e via PosterMyWall.

Note: You can bypass adding the PosterMyWall subdomain if you're on the Premium Plus subscription plan. However we do allow doing this for non-custom domains as this may negatively effect campaign performance.  

Option 2: Preparing a custom domain

To improve campaign deliverability for your email campaigns with a custom domain, we recommend setting up a DMARC policy, SPF record and DKIM to improve email deliverability and reduce chances of your emails into going to recipients' spam folders. 

Note: If you're using a non-custom domain, you don't need to do the following. 

Set up a DMARC policy

If you're sending emails from your own email client, setting up a DMARC policy is crucial. This improves the chances for your email campaigns to not be labeled as spammy. DMARC is a first line of defense used by many email clients to protect their users from spammy and fraudulent emails.

Having an active DMARC policy indicates to the receiving email server that the sender is taking active steps to authenticate their email, which can lead to better email deliverability and reduced likelihood of emails being marked as spam.

Here's how you can set up your DMARC policy: 

  1. Determine Your Policy: Decide on the policy (none, quarantine, or reject) and how you want to receive reports.
  2. Craft the DMARC Record: Formulate a DMARC TXT record for your DNS. This includes specifying the version (v=DMARC1), the policy (p=none/quarantine/reject), and the email addresses for aggregate (rua=mailto:) and forensic (ruf=mailto:) reports.
    For example: 
    v=DMARC1; p=none;
  3. Update DNS Records: Add the DMARC TXT record to your domain's DNS settings. This is usually done through your domain registrar's control panel.

Implement SPF

The SPF record helps prevent email spoofing by specifying which mail servers are permitted to send email on behalf of your domain.

To implement SPF:

  1. Craft the SPF Record: Start with v=spf1. Use the include mechanism with the specific domain provided. E.g. if your sending domain is Amazon SES, your record might look like: v=spf1 ~all
  2. Update DNS Records: Add this SPF TXT record to your domain's DNS settings, typically through your domain registrar's website.
  3. Test Your Setup: After updating the DNS, use an SPF record checker online to verify that it's correctly set up.

DKIM setup

DKIM adds a digital signature to every email, which allows the receiving email server to verify that the email was indeed sent and authorized by the owner of that domain. This helps to prevent email spoofing.

To implement DKIM:

  1. Generate a DKIM Key: Use a tool or service to generate a DKIM key pair (private and public).
  2. Configure Your Email Server: Configure your email server (or email service like AWS SES) to use the private key to sign outgoing emails.
  3. Publish the Public Key: Add a DKIM TXT record to your domain's DNS settings, containing the public key. This allows recipient servers to retrieve the key and validate the signature. An example of how the DKIM TXT record would look like:
    s1._domain. IN TXT "v=DKIM1; k=rsa; p={PUBLIC KEY}"
  4. Test the Setup: Ensure your DKIM is set up correctly by sending test emails and using DKIM validation tools.
Was this article helpful?
17 out of 30 found this helpful

Articles in this section

See more
New to PosterMyWall?
Check out our one stop resource to learn everything you need to start creating professional designs for your business in no time.
Want unlimited downloads?
Get unlimited video and image downloads, social media scheduling, one-click background removal and more with PosterMyWall Premium.