0

Bounces and Invalid Emails

There are many reasons why an email is not delivered to the recipient.

• Auto-responses and Vacation Replies
• Email delivered to “Junk” or “Spam” folder of recipient
• General undeliverable emails with no error specified by recipient’s server
• Recipient email server is down or unreachable
• “Connection timed out”
• Recipient mail box full
• Recipient email address not found
• Temporary non-delivery (server will keep trying for a few more days)
• Your server IP is blocked by recipient’s ISP (“Relaying Denied”)
• Your server IP is blacklisted for suspected spam

And the list goes on!

That should give you an idea why email delivery is so tricky and complicated, which is what created a niche for the email delivery industry, and which is why companies like Aweber, MailChimp and GetResponse even came into existence and have thrived while charging a hefty fee for what you would think is the simple act of delivering email over the interwebs.

When you use DAP for sending out emails (whether autoresponder or broadcast emails), the “From Name” and “From Email” you set up in the DAP Config are used to send out the emails.

If you use your own web host as the “carrier”, then your web host’s email server is the one that carries the email and tries to deliver to the inbox of the recipient. And web hosts are generally not very good at the intricate science of email delivery, which is why if you’re going to use DAP, we recommend that you bypass your web host and have a third-party email system like Amazon SES deliver your emails.

Regardless of the carrier (web host, Amazon SES, AuthSMTP.com, etc), all bounced and undeliverable emails come back to the “From Email” that you have used under DAP Config.

DAP by itself does not do anything with those emails, as those emails don’t come back to DAP, but they go straight to the inbox of whatever “From Email” you have specified.

We will surely address this in the future. But for now, you will have to manually review those email bounces, see which one of them sound more serious (like, say, recipient email id not found, or domain no longer in use, etc), and then de-activate those email id’s from your DAP database.

When you use Amazon SES, Amazon by itself also monitors email id’s that have a consistent history of bouncing back, and will automatically suppress those email id’s and won’t even deliver email to those email id’s even if DAP did send the actual email to those id’s.

1

Automated Reminder Emails For Admin

In DAP, you can not only send automated pre-scheduled emails to your members (Autoresponders), but you can also set up similar pre-scheduled “Reminder” emails to be sent to you (the admin) every time a member reaches a day milestone.

Eg: Let’s say you (the admin) want DAP to send you or someone on your team a reminder email to follow up with each member by email once they reach day #7 – meaning, it’s been 7 days since they signed up for a specific product.

This is how you do it in DAP:

1. Go to DAP Admin > Emails > Autoresponders
2. Click on “Compose New Email“
3. For subject, enter (say) “Follow Up with %%FIRST_NAME%%”
4. In the body of that email, you may use merge-tags for the member – like “Be sure to email %%FIRST_NAME %%LAST_NAME%% , ask them about their progress, see how they’re doing and upsell Platinum Coaching program. Their email id is: %%EMAIL_ID%%”
5. Further below on that page, in the “Send to 3rd Party (instead of member)” field, select “Yes (like admin or staff)” and you will see an additional text box show up below, where you can enter your (or your staff’s) email id where you want the reminder to be sent.
6. Save the email.
7. Go to the DAP Product where you want this email to be added to the sequence.
8. Go to “ContentResponder” tab.
9. Add this new email to the product, click on the “Edit” icon, and set it to be dripped on Day #7.

That’s it!

Now for each member that signs up for that product, regardless of when they join, every time they reach day #7, the reminder email will be sent to the 3rd party email id specified for that message (instead of being sent to member).

Reverse Dripping

If you want to be sent this same email say 3 days before member’s access expires to that Product, then set the email to be dripped on day “-3”. (See Expiration Notifications / Renewal Reminders)

0

Expiration Notifications / Renewal Reminders

We have a new feature starting DAP v4.4: “Reverse Dripping”

This is where you can drip emails “X” days (where “X” is a number of your choice) before the access to a product ends for a member. So this is what you would use to send expiration notification / renewal reminder emails to your members.

To setup a renewal reminder email, you would set up the email as usual, and drip it as a negative day. So if you set up the email to drip on Day “-1”, then it means the email will be sent out 1 day prior to product expiry (for that product).

If you set it up to drip on “-3”, it will be sent out 3 days prior to access end date.

If you set it up to drip on “-7”, it will be sent out 1 week prior to access end date.

Renewal Reminder Email Setup

Warning: This is something you should set up only for recurring products that require manual renewal. Do not set up these emails to go out for automated subscription products, because the members will be charged automatically on the designated day every month, and asking them to renew will only confuse them.

1. Create a new Autoresponder email with the product expiration notice, at Email > Autoresponders. In this email, you would say something like “Hey, your subscription is expiring in 1 week, so click on this link to renew… (followed by link to renewal page)”.
2. Create another email that says “Hey, your subscription is expiring tomorrow…”.
3. Go to Products > Manage and choose product for which you wish to set up renewal reminder.
4. Switch to “Autoresponder” tab.
5. Select the 7-day renewal reminder email from step 1 and add it to the product.
6. Then click on the “Edit” link and set the drip day as -7
   
7. Do the same for the 1-day reminder email as well, and this time set the dripping to be “-1”.

That’s it!

0

Troubleshooting Amazon SES Integration

DAP’s Amazon SES integration has been heavily tested, and we use it ourselves at DigitalAccessPass.com . So you can rest assured that there are no “bugs” of any kind.

Here are some troubleshooting steps if SES integration is not working even after you’ve followed the documentation exactly.

Troubleshooting SES

1. MOST COMMON MISTAKE: Have you whitelisted the DAP “From” email in Amazon? And have you used exact same “case” for the email id in both places (DAP and Amazon)? Double-check spelling and case in both DAP and Amazon – they must be EXACTLY the same. For eg., you@yoursite.com is NOT the same as You@YourSite.com as far as Amazon is concerned. So if you’ve set the “From Email” in DAP to be you@yoursite.com, then you must whitelist exactly the same email id you@yoursite.com within your Amazon SES account as well. If you are not sure, delete the whitelisted email in your SES account, then COPY the from-email from DAP config (be sure to copy, and not re-type) and then PASTE the exact from-email into your Amazon SES account and whitelist it again.
2. IMPORTANT: Have you requested Amazon for “Production Access” to your SES account? Being in “Sandbox” mode has its disadvantages (you can only send “from” and “to” whitelisted” emails ONLY). So your account MUST, MUST, MUST be in “Production” mode before Amazon SES lets you send emails to your customers.
3. Are you using the exact ports as mentioned in our documentation? Ignore the port #s that Amazon recommends.
4. IMPORTANT: Double-check with your web host to make sure that they actually allow a plugin like DAP to connect to a third-party server like Amazon SES to send out emails. Some hosts don’t even allow that to begin with (like BlueHost, for eg.)
5. Turn on the logs by setting DAP > Setup > Config > Log Level to “Log All Activity”.
6. Then go to System > Logs and clear the logs. Then go to one of your test accounts, and edit the user.
7. On the “User Edit” page, click on “Resend Login/Password”.
8. Check the email inbox to see if you got the email. If you didn’t, go to System > Logs and take the entire logs shown there, and paste it into a support ticket, and don’t forget to give us your WP login info and FTP info (and if possible, Amazon login info as well), and we’ll troubleshoot it.

1

Automated Email Dripping

In dap 4.4, we have added a new feature where when you setup content for dripping, dap will automatically setup an email auto-responder to drip corresponding to each dripped content. The autoresponder drip setting will match the content drip setting. When you enable the automated dripping, an email will automatically get dripped ( you will find it in dap products page -> autoresponder tab) for every content you have dripped. An automated email alert will get sent to your participants and you can configure what you want in that email in the dap setup->templates section.

You can configure/customize the email you want sent automatically when any content is dripped and the email will automatically get sent at the top of the hour (when dap hourly cron runs).

But there are a few things that it does not support :

1) You cannot control what type of content should result in automated dripping (post/page/files etc). It will apply to all dripped content.

2) If you have content already dripped before you install the autodrip module, then when you install the autodrip, it will get a list of ALL of your dripped content .. even the ones you had dripped in past (and not just the ones you drip from that point onwards).

And it will set up an automated email to drip for each of your post/page regardless of when it was actually created. in this release, you CANNOT set a point in time to make the autodrip apply to posts created only after that point in time.

3) When automated dripping is configured, it will apply to all products. You cannot configure it at product level. It’s a global setting. So any post/page you drip under any product.. an automated email will get setup for that page/post. If you have product A and B, then you cannot have the autodrip only apply to say product A. It will automatically apply to both products – A and B.

4) You cannot use it if you are ALSO using SSS/ Credit Store. It’s not compatible currently.

Here’s how it works :

If you have a content set to drip day 10 as shown below:, then an automated email will get setup and it will get sent to users that’s on day 10 of their membership. If you have new users that just joined, they will not receive the email until they reach day 10.

If you have content set to drip day 1 as shown below:

 

Then an automated email will get setup (as shown below) and it will ONLY get sent to users that’s on day 1 of their membership. If you have new users that are on day 2 or more, they will never receive the email as they are already past that drip day.

Setup Instructions :

Just like the hourly dap cron (dap-cron.php), you will have to configure another cron for autodripping.

The name of this cron script is  /dap/dap-autodrip.php. You can configure it to run once every 1/2 hour. This way it will pick up any new posts added in the 1/2 hour and create autodrip entries for it.

Say your cron command for the hourly dap cron (dap-cron.php) in your webhost cpanel -> cron tab is :

/usr/bin/php /var/html/wordpress/dap/dap-cron.php

Then for autodrip, the command will be:

/usr/bin/php /var/html/wordpress/dap/dap-autodrip.php

Set it up in your webhost cpanel -> cron tab to run once every 1/2 hour. Everything for this cron will mirror the dap-cron.php except the name and it will run once every 1/ 2 hour instead of once every hour like dap-cron.php.

Here’s how can test this feature :

1) Lets say you have a NEW product
2) Now add a new user to that product via dap admin -> add users page
3) Now say you dripped testpost1 under that product. Set drip start day = 1
4) Now go to autoresponder tab and make sure there are NO automated emails set for drip
5) Now either wait for the dap-autodrip.php cron to run (depending on whether you set it to run once every 1/2 hour or 1 hour)
OR
For testing purpose, you can run the cron manually by visiting this URL in a browser:
http://YOURSITE.com/dap/dap-autodrip.php

6) After you run it manually or after it runs via cron, if you go and check the Email Autoresponder tab for that product, you shd see a new AUTOMATED autoresponder email dripped for that testpost.

7) Now wait for the main dap cron job to run. It will run once every hour.
When it runs the email will get sent. To make sure email got sent, go check dap system -> job queue. See if you find the email there with “completed successfully” status. If yes, the email got sent and you are all set.

NOTE: If you dont want to wait that long and want to quickly test it, then just run dap-cron.php manually by visiting this URL in a browser:
http://YOURSITE.com/dap/dap-cron.php

3

AuthSMTP Integration

If you’re having email delivery issues on your host, you can connect DAP to 3rd-party email systems like Amazon SES and AuthSMTP.

In this article, you’ll see how to integrate DAP with AuthSMTP.

1. Signup for an account at AuthSMTP
2. Log in to your AuthSMTP account
3. Go to Registered From Address tab
4. Take the email id from DAP Admin > Setup > Config > From-Email Id and enter that email here and register it here (basically, you’re whitelisting your DAP Admin email id as a registered sender – if you don’t do this, AuthSMTP will reject and discard all emails sent via DAP). You will need to “Confirm” the registration by clicking on an activation link that they will be sending you.
5. In your AuthSMTP account, go to SMTP Details tab.
6. Make a note of the SMTP Server (usually mail.authsmtp.com), SMTP Username, SMTP Password.
   
7. Now log in to DAP Admin, and go to Email > SMTP
8. On this screen, use the section Add a New SMTP Server to create a new SMTP row as follows:
   Description: AuthSMTP
   Server: mail.authsmtp.com (or from Step 6 above)
   Port: 2525 (must be exactly that)
   SSL: N (must be exactly that)
   User Id: Your AuthSMTP Username (from Step 6 above)
   Password: Your AuthSMTP Password (from Step 6 above)
   Email Sending Limit Per Hour: 500
   (Max 500 if on shared server. Max 2000 if VPS or dedicated server)
   Activated: Y
9. Click on the “Add” button to create and save the new AuthSMTP server setting.
10. And now you should see two rows under Manage Existing SMTP Servers: One for “Local Web Host” and another for “AuthSMTP”.
11. For the “Local Web Host” row, be sure to set “Active” to “N” – because now that you have set up AuthSMTP, you want all instant welcome emails, autoresponder and broadcast emails to be sent out through AuthSMTP, and not your web host’s email server.

That’s it!

5

Gmail Integration With DAP

WARNING: Gmail integration may not work for everyone. Many factors – including, but not limited to, your physical location, the location associated with your Gmail account, location of server, IP address, etc – appear to play a role in whether or not this will work for you with your Gmail account. So please note, that if it doesn’t work for you, then there isn’t anything the DAP team can do to overcome or “fix” that. It’s Google, after all. We don’t know what rules and monitoring they have in place for this. So, if Gmail integration doesn’t work for you, then you may want to consider Amazon SES integration, which has a 100% success rate with DAP users at this time.

To increase deliverability of your autoresponder, broadcast and instant emails (like “Welcome” email), you can make DAP completely by-pass your web host’s email server, and send emails out through third-party email servers, like Gmail or Amazon SES. This article is about setting up DAP to send out emails through Gmail’s email servers.

Sending Email Through Google’s Gmail Servers

Before you start sending out mass emails through Google’s Gmail Servers, please note this…

Sending out emails through Gmail instead of your web host, will surely boost your deliverability, no doubt. But remember that Gmail is NOT meant to use for mass emails. It is not really meant to be used as a list service. Plus they have a very strict restriction of 500 emails per 24-hour period.

You exceed that quota even by one, and they probably will temporarily disable your Gmail account for about 24 hours. Sending a large number of un-deliverable emails (resulting in bounces) could also get your entire Gmail account permanently suspended. And if you lose your Google username, it may (no confirmation available) affect your other Google accounts too – like AdWords or AdSense.

Anyway, DAP has a round-robin emailing system – so you could set up and use multiple Gmail accounts – each with its own 500 email limit per day – and combine them to send out a larger broadcast. However, remember – we’re talking about Google here – which means they can suspend/cancel/delete your account for any reason at all, even more so when you’re going against their TOS.

So use Gmail with caution, and only for smaller lists. If you want a larger sending email limit, check out the DAP integration with Amazon SES which allows you to send out tens of thousands of emails a day.

1. Log in to your DAP Admin Panel, and go to DAP Admin > Email > SMTP.
2. On this screen, use the section Add a New SMTP Serverto create a new SMTP row as follows:Description: Gmail (can be anything really)
   Server: tls://smtp.gmail.com (must be exactly that)
   Port: 465 (must be exactly that)
   SSL: N (must be exactly that)
   User Id: youremail@gmail.com (your gmail email id)
   Password: yourpassword (your gmail password)
   Email Sending Limit Per Hour: 500 (don’t go more – less is ok)
3. Click on the Add button to create and save the new Gmail SMTP server setting.
4. Once it is saved, now you will see 2 rows on the screen: One for “Localhost”, and the other is the new “Gmail”.
5. Towards the end of each row, you’ll see a setting called “Activated?”. Set it to “N” for Localhost and “Y” for Gmail.
6. That will now make all of your outgoing emails (listed below) go out only through Gmail, totally bypassing your web host’s email server. Which means, your email deliverability will go up substantially.
7. List of outgoing emails for which your Gmail account will be used, include:
   – Real-time Welcome Emails
   – Third-party Notification Emails (to Admin, other third-parties, Aweber, etc)
   – All notification and transactional emails to DAP Admin – like payment receipt, new user signup, error notifications, user unsubscription notifications, etc
   – All autoresponder and broadcast emails
   – etc…

 

37

Amazon Simple Email Service (SES) Integration With DAP

DAP/Amazon SES Integration

You can hook up DAP to Amazon’s Simple Email Service (Amazon SES) and have all of your emails go through Amazon’s beefed up, high-performance, high-deliverability email servers.

The document below explains how to connect DAP to Amazon SES. (troubleshooting info for DAP/SES integration)

1. Go to http://aws.amazon.com/ses/ and sign up for Amazon SES. You must already have an Amazon account and you can add SES to that same account.
2. Then go to https://console.aws.amazon.com/console/home , log in if required, and click on the SES link there.
3. That will bring you to the SES “Dashboard”.
   
4. When you first sign up for SES, you will be assigned a “Sandbox” account. Which means that you will only be able to send emails TO and FROM verified email addresses (a verified email address is something you add yourself to your SES account and then click on a confirmation link that Amazon sends you, to prove that you are the owner of that email id). Also, Sandbox access allows you to send out a maximum of just 25 emails per day, both FROM and TO verified email id’s only.
5. So the first step is to add a Verified Sender. So click on the “Verified Senders” link in the menu on the left.
   
6. That will bring you to this page. Click on the Verify a New Email Address link with the green check-mark next to it.
   
7. In the popup, enter the email id that you wish to use as your FROM email id to send out emails. Please note that you can ONLY use verified email id’s to send out emails from your Amazon SES account. So whatever email id you wish to use in DAP Admin as the sender for outgoing emails (see DAP Admin > Setup > Config > From-Email Id : For all outgoing DAP emails), that’s the email id you should verify.IMPORTANT: The email address is case sensitive. So if you white-listed You@YourSite.com at Amazon SES, then you must enter the email address with the exact same cAsE within DAP Config too (You@YourSite.com is NOT the same as you@yoursite.com for the purposes of Amazon SES. Crazy, we know! But that’s how it is.)

   

8. You will then receive an email from Amazon at that email id which has a confirmation link. Once you click on that link, your email id in your Amazon SES account is now “Verified” (also known as whitelisted). Please note that at this time, you still have Sandbox access. Which means you can send email both FROM and TO the same verified email id. Not very useful, but that’s ok. Now time to go back to the SES Dashboard and Request Production Access.
9. Click on Request Production Access and you will be taken to a form that you need to fill out and submit. Amazon then reviews it, and it can take up to 48 hours for your account to be granted Production Access – which basically means, you can now use SES and start sending out real emails, and your per-day limit is now 10,000 emails per day.
10. Now, you need to get a SMTP Username and SMTP password for sending out emails. This username & password is NOT the same as your Amazon account email and password. Neither does it have anything to do with your Amazon Public or Secret keys. This is a completely different (and new) username and password used JUST for sending emails, and it needs to be generated newly.
11. To generate a new set of SMTP Username and Password, click on the SMTP Settings link in the menu. And then on the next page, click on Create My SMTP Credentials.
    
12. In the resulting popup, click on Create.
    
13. That will create your SMTP credentials. But to see it, you have to click on Show User SMTP Security Credentials
    
14. Once you click on Show User SMTP Security Credentials, you will be shown your SMTP Username and Password.
    
15. Be sure to note down the username and password in a safe place where you can get to it again, because Amazon will not show this same set of username and password ever again. If you lose them, of course, you can always generate a new set of username/password again for free, but you’ll never get the same pair again – it will be a fresh pair.
16. Go to the SMTP Settings link in the menu and note down the Server Name.
    It will be one of the following:
    email-smtp.us-east-1.amazonaws.com (as in the image below)
    email-smtp.us-west-1.amazonaws.com
    email-smtp.eu-west-1.amazonaws.com (European Union users)
    You need to determine what your host name is, and then add the text “ssl://” to it at the front.

    So if the server name displayed in your Amazon SES account is this…
    email-smtp.us-east-1.amazonaws.com

    …then the text you would enter into the DAP Email > SMTP page is this…
    ssl://email-smtp.us-east-1.amazonaws.com

17. Now log in to your DAP Admin Panel, and go to DAP Admin > Email > SMTP.
18. On this screen, use the section Add a New SMTP Server to create a new SMTP row as follows:
    
    (Click on image above to see full-size screenshot)
    Description: Amazon SES
    Server: <what you noted down above>
    Port: 465 (must be exactly that – ignore port numbers recommended by Amazon SES)
    SSL: N (must be exactly that)
    User Id: Amazon SMTP Username (that you generated and noted down in Step 15 above)
    Password: Amazon SMTP Password (that you generated and noted down in Step 15 above)
    Email Sending Limit Per Hour: 500 (ideal number – don’t go more – less is ok)Click on the “Add” button to create and save the new Amazon SES SMTP server setting in DAP.
19. Once it is saved, now you will see 2 rows on the “Email > SMTP” screen. One is for the server “Localhost”, and the other is the new “Amazon SES”.
20. Towards the end of each row, you’ll see a setting called “Activated?”. Set it to “N” for Localhost and “Y” for Amazon SES.
21. That will now make all of your outgoing emails (listed below) go out only through Amazon SES, totally bypassing your web host’s email server. Which means, your email deliverability will go up substantially.
22. List of outgoing emails include:
    – Real-time Welcome Emails
    – All transactional emails to DAP Admin – like payment receipt, new user signup, error notifications, user unsubscription notifications, etc
    – All autoresponder and broadcast emails
    – etc…

Watch this video for details:

8

Testing Autoresponder And Broadcast Emails

Here’s how you test emails in the system before making them live.

Testing Autoresponder Emails

1. Create a test DAP Product called “Test Product”
2. Set up the email drip for this product
3. Give yourself (or a new test user, but with a real email id that belongs to you) access to this DAP Product on the Users > Manage page (for existing users) or Users > Add page for new users
4. Run the hourly-cron manually, by going to http://YourSite.com/dap/dap-cron.php . That should send out the day 1 drip for that test user.
5. Go to Users > Manage page, and back-date the Access Start Date for this test user for the test product, back by one day. So DAP now thinks he bought the product “Yesterday”.
6. Now run the cron manually again. This time, DAP will send out the day #2 drip for this user.
7. So every time, move the user’s access start date back by as many days as you want, to trigger that day’s autoresponder email. And each time run the cron manually.

Testing Broadcast Emails

1. Create a test DAP Product called “Test Product” (or if you have previously created one above, then use the same one)
2. Add 3-4 test users to this product
3. On the Emails > Broadcast page, schedule a broadcast email to be sent to “All Users of Product <<Test Product>>”
4. Run the hourly-cron manually, by going to http://YourSite.com/dap/dap-cron.php . That should send out the broadcast to that test product.
5. Log in to the email id’s of all the test users that you added to this product, and make sure the email arrived in the inbox.

0

Troubleshooting Email Broadcasts

* When you schedule a broadcast email, it’s added to the job queue with a status of NEW
* When the cron job runs at the top of the hour, then the job status changes to COMPLETE (C) and the emails get sent.

So to test it, do this.

1. set up an email broadcast to a test user using the CSV format (option # 5)
2. Go to DAP Admin > System > Job Queue and see if the job was added with a status of NEW
3. Now manually run the cron by running this cron script in a browser (just for testing)
   http://yoursite.com/dap/dap-cron.php (replace yoursite.com with the name of your site)
4. Then go back to the job queue and see if the status for the email job has changed to ‘C’ (complete)
5. If yes, check if the email was received.

Troubleshooting “Payload Format Incorrect” Error

If you see this error when trying to send out a broadcast to a default group from the Email > Broadcast page, then the most plausible cause for this is that there are some special, non-standard characters in the body of the email that you’re trying to broadcast.

This could happen if you copied text that you composed in a Microsoft Word doc, or you cut/pasted from a WordPress blog post. And both Word and WordPress (some themes) are famous for creating special characters out of normal characters.

Example:

If you take a closer look at the body of your email, especially the single quotes and double-quotes characters, you will find that these may not be the standard single quote and double quote characters that you get from a plain text editor.

And these special characters trip up the DAP email broadcasting system.

So please take a closer look at all of the following characters:

• Single quotes
• Double quotes
• Hyphens
• Special symbols like trademark and copyright

And just type over them again just to be sure with the normal equivalent using your keyboard, and try the broadcast again.

And this time, it should work.

Email Body Showing Up Partially On Job Queue

When you view the broadcast emails that you just scheduled on the System > Job Queue page, if you see that the email body in the saved job has been randomly cut off at one point (usually at the point where there would normally be a single or double quote), then that’s also an indication of non-standard characters in the email that you tried to send out. So see the above example for how to weed out any non-standard single or double quotes or hyphens, and try the test again with just one test email, and see if it goes out to just that one email. Because if it fails for one email, then it will fail for all emails being sent via the DAP Broadcast system.