I'm currently integrating Sendgrid (Back-end API) with Phplist (front-end). However, I realised that there are many features that Phplist doesn't support such as autoresponders, different management levels (sub/superusers) and is unable to send high volumes. May I know if there is a better front end that I can use to integrate it with sendgrid?
Yes! OpenEMM seems to have the features you're looking for. You can see the full list here, but the highlights are:
Configuration of different users with different rights/roles
Autoresponder mails and error messages (bounce management)
It looks a little tricky to setup, but they have good documentation. Also, the code is hosted on SourceForge and the reviews look solid too.
In terms of setting it up with SendGrid, you have to configure your sendmail to use our SMTP servers. Luckily, we have a tutorial already that shows you exactly how to do that:
http://docs.sendgrid.com/documentation/get-started/integrate/examples/sendmail/
Related
I have a problem. We've designed some beautiful, responsive email templates that work across mobile/tablet using media queries but contain MSO conditionals to work on Outlook. Turns out, the client now claims they can only send through an exchange-based mailing list. Ouch.
Problem:
If I send from Mac OSX's Mail, it retains the media queries and works (they are then stripped in Outlook when opened by receiver, but that's inevitable)
If I send from Outlook, it strips media queries completely and sends without them
From my thinking, the only solutions are:
Distribute through a different email client that supports both viewport media queries such as Mac Mail and allows connection to Exchange (know any? Thunderbird?)
Somehow obtain the mailing list and distribute through MailChimp or similar
Appreciate any advice anyone may have.
Depends on how good you care in code and whether you'll need clients to access your system. You can go with user friendly, feature packed options like Mailchimp or Campaign Monitor.
Much cheaper but less featured (relies heavily on you integrating through their api) is Sendgrid
If you want to stick to free, PHPList might be a good option.
I have a domain registered and AWS EC2 with LAMP used as a online game server.
Now I wish to set-up a e-mail server on it. But after some research, I found it to be some kind complicated.
The e-mail server will only be used to send forgot-password emails to players. So I am seeking a simple way to set-up a send-mail server without mailbox or any other functions that will compliate the things. Is there any way to do that?
I definitely advise you to use Amazon SES. You will use Amazon's infrastructure to send emails as a service.
To me, it seems to be the best solution to your use case. You won't pay much, won't need to worry about downtime or scalability, and will simply need to use their SDK in whichever language you prefer.
Take a look at the pricing, it is quite attractive.
I've done quite a bit of searching for a CMS platform or robust framework that will perhaps facilitate the management of signup and subscriptions right of the box with a Twilio tie in.
Thus far I've only been successful at finding how many startups have been funded by the Twilio fund, who's building the nextgen voice enabled app, and various other things of that nature vs any real meat. Seems that there's a dearth of meaningful information without applying a plethora of negative google filters to reduce matches and even then it's still not giving anything real meaningful wrt my search.
So, I'm hoping that someone may have a better eye on the lay of the Twilio landscape as far as already existent systems go that can handle the bulk of needs that exist for a "regular" CMS esque site that needs to also handle subscriptions and e-commerce related tasks.
Hitherto I've just planned to build something out myself, but I wanted to do a sanity check before I spend a lot of time that could perhaps be obviated.
My suggestion would be to find a CMS that does everything you want (except the twilio links), on the platform you want, and then just add the Twilio stuff in. Twilio is simple to use, and should be simple to add-on to most open source CMS's. It'll probably be the easiest part of the project....
I'm trying to figure out a solution to manage our transaction emails (such as the welcome email, you've got a bid, etc...)
We would like to be able to allow marketing to manage the content of the emails, and create split tests to test content / subject lines / etc...
Ideally we could invent our own success metrics to report back to the email management system (such as user completed registration, accepted bid, etc...).
Right now we have our emails in templates using stringtemplate. The code replaces tokens with the correct content for that email.
Strongmail is a potential solution, but it is pricey - anybody have experience with alternatives?
I'm looking for the same kind of service, and https://www.sendwithus.com/ seems to do the job.
Have you taken a look at PostageApp?
Currently, it's a layer between your web app and your SMTP server which has additional features for your transactional emails.
With PostageApp, you are able to create two different templates and have them triggered alternately with different content and subject lines. However, the metrics that you would want to use for A/B testing aren't built into the system yet, so I'm not sure if it would be a good fit for you.
Full Disclosure: I work for The Working Group, the company that created PostageApp.
But if you do have questions about what we can help you with and what we can't, definitely let me know and I can answer plenty of questions for you!
Try http://www.cakemail.com/
It is a third party, you design your workflows and give them your contacts.
I work for a 6 million a year website company and we direct all our clients to them, so far so good, everyone is happy.
You have to contact them to have a price but you can get a free account for testing
I've been looking at these too, both seem to provide fully functional XMPP servers in Java. I know Tigase is designed in a very modular way, not looked at Openfire in as much detail yet.
My intended use would be to create a custom IM-based app, using XMPP for convenience rather than to open my server up to talk to other XMPP servers.
I'm trying to evaluate my needs based on the following, roughly in order of importance:
Documentation coverage & community
How easy to plug in own functionality
Licensing/cost - I don't plan to release my code
Maturity and stability
Do not use Openfire if you expect to scale beyond a couple of thousand concurrent connections.
Tigase is amazing at handling hundreds of thousands concurrent connections and is wonderfully architected for largely distributed platforms where XMPP is simply the external interface. It comes with a price of rather poor documentation. You often need to go and read the source code to understand what's going on.
Openfire is perfect for small setups and its API is simple and very well documented. Unfortunately, it's not architected to scale even nearly close to what tigase is capable of.
Tigase is GPL(even version 3) licensed opposed to OpenFire being under Apache license ... for closed source application is OpenFire the go.
It is embaddable and proven to be reliable - 1000s of concurrent users. It even has gateways to communicate with legacy networks - like ICQ.
Only drawback I can se here is that it can handle only one domain per instance(port), however from your description that should not be a problem.
I totally agree with #Yuriy in that Tigase is great for high scalability whereas Openfire is more suitable for small, novice IT running chat for a SMB. I have gone into more detail on this in my blog on Tigase vs Openfire.
And Openfire 3.7.0.beta is out since some days now.
Lots of bug fixes, now also support Solaris as host system.
Concerning openfire ... it seems to be more or less abandoned and certainly not because of lack bugs to fix ;)