If a recipient does not unsubscribe and files a complaint instead,
Amazon SES sends a notification.
As an intermediate measure it should be treated as hard bounce.
As a new feature idea:
Perhaps an option would nice to be able to add theses guys to the suppression list.
In order to meet Amazon's standards it's important to unsubscribe these recipients.
Otherwise Amazon may terminate your SES account.
I hired Michael at iCoder to configure my installation this time around (this is the third or fourth time I've used his services happily) and he configured the bounce and complaint handling for AmazonSES for me. Very happy that I was at LEAST able to pay to have it done successfully although it really belongs as a core feature. I'm just replying here to let you know that there at least IS an work around now.
1) I love having control over my own data and mailing... even with the hassles.
2) Single opt-in has meant a much faster and active list over time than forced double opt-in.
I've been a technologist for 30 years. Companies that cannot deliver regular updates either have a process problem or a resource problem (people, or the RIGHT people). It may be that arpReach has both. I am very very nervous about whether the software will be maintained and upgraded in 2015 and beyond. I've definitely gotten my value from it (we've mailed millions of emails), but I'm concerned about building the "next layer of automation" for our business in this solution.
Me too. (And don't forget the attachments bug, which I discovered the hard way a couple of weeks ago.) I think I'm on a much smaller scale than you are, a one-person business considering whether to move everything to Arpreach and cancel my Aweber subscription. That's seeming like less and less of a good idea.
I am looking right now at our yearly restructuring of our autoresponders, and I'm just not sure where to go with this when the core of our solution, arpReach, seems to be unsupported/un-updated on any kind of reasonable schedule.
In so many ways it is a really useful and cost-effective solution for companies with tech/email expertise inhouse. Compared to some other solutions, it really rocks. AND, the gaps left from the rewrite in terms of contact management, actions, tracking, and tagging are really stark for those of us implementing, say, The Machine from Digital Marketer.
Would dearly love a "come clean" from the developers at this point.
I share your disappointment.
Many announcements of important features.
But no updates since a year or so.
The reason I purchased arpReach was absolutely down to the fact that they have a long history in the autoresponder software business. Therefore I expected a solid software that would be updated.
As far as I can tell, support seams lacklustre and updates non-existent.
I passed on a $37 wordpress plugin because I expected that from it, I didn't expect it from a $400 software.
Just a quick reminder:
18 Months ago you wrote:
"We already have plans to add this and release during May."
I even provided you with the samples you requested.
A couple of other features were announced as "coming soon".
For October 2013 you guys announced:
arpReach 1.3.001 with API is coming soon
as well as Multi-Threaded Sending.
Why don't you publish these updates?
There wasn't anything since more than a year.
Why have you stopped working on the promised ARPREACH stuff?
In december arpreach support wrote:
an FBL feature is not yet available and we cannot guarantee if it will be available on the next minor update
Strange as 6 months ago Neil promised that "for next week".
However - should someone know how to set up a fbl with SES, please share your knowledge.
Thank you very much.
Under Email systems > Amazon SES > edit > options > advanced you can enter 'send failure strings' to trigger a removal from all lists and/or adding to suppression list. The question is what to put in the 'send failure strings' box. Does anyone know?
What do we put in here - Tim Bratton what did you put in here when using Amazon SES?
When you look at the sender score, it's clear why:
Amazon SES (sampled IP address): 88 - 92
My IP address: 99
That's exciting news Tim, I've been running my own mail server for years and my sender score is also quite high, I spent quite a lot last month on Amazon SES, so it seems maybe I can see if plain old Sendmail would do better deliverability - but can you tell me, do you really get better deliverability and speed with Sendmail vs. SMTP? I've always been told that SMTP should be used for assuring proper delivery, etc?
Also Tim Bratton - I noticed before you mention handling your own FBLs manually, are you still doing that manually? I don't see it's possible for me, and quite a time-consuming task. Or, do you have some automated FBL PHP code that you are using that works for you - for all the providers? Without an API, I assume you would just make calls to the arpReach command line to remove the subscriber?
Tim do you have FBL code for: GMail, Yahoo, AOL, Hotmail, LiveMail and any of the others I may have forgotten?