There are many reasons why an email is not delivered to the recipient.
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.
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:
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).
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)
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.
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.
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.
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 :
Then for autodrip, the command will be:
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)
For testing purpose, you can run the cron manually by visiting this URL in a browser:
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:
In this article, you’ll see how to integrate DAP with AuthSMTP.
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.
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.
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)
So if the server name displayed in your Amazon SES account is this…
…then the text you would enter into the DAP Email > SMTP page is this…
Watch this video for details:
Here’s how you test emails in the system before making them live.
* 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.
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.
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:
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.
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.