I want to send one email using mail chimp v 3.0 API, but I am not sure which exact end point we need to use. I am checking [this].(http://developer.mailchimp.com/documentation/mailchimp/reference/overview/)
But still not exactly sure which end point can send the email.
Campaign Creation and Sending are not yet in MailChimp API v3.0.
Related
My main goal is to setup an email address for my server to use for sending emails only.
I did some research, and it looked like Amazon Simple Email Server and/or Amazon Workmail could provide me with what I needed. I've gotten as far as setting up SES and Workmail so that I can set my server to be able to send emails. However, I saw that once the Workmail inbox is full (50GB), the account would be unable to send emails. Given that this is going to be used by the server and not a human, I didn't want the inbox to get filled with auto replies, spam, or failed to send messages, and then be unable to send emails. So, I went looking for a way to either:
A) prevent emails from being received and stored in the inbox
B) a rule I could setup to delete anything that didn't match the company domain
C) be able to read the inbox and delete email messages using the AWS CLI, and I'd setup my own script to manage how and what was deleted when
So far I haven't had any luck.
Again, I'm not particular how I achieve the goal, but I do preferably need to find a way to have an email address for a server to use exclusively for sending messages. I worry that if I leave it to employees to remember to login and clear the inbox, someone will forget, and then the server will stop sending emails.
Any direction or advice would be greatly appreciated.
I'm not well versed in email protocols; could I setup the address to return a bounce back always, and that would prevent it from receiving emails into it's inbox?
How are you generating these emails? If you are generating them programmatically (via an app/script), you may not need to set up a server. If you just route the outgoing mail through your app to SNS, the emails will be valid, however, there will be no "inbox" for incoming mail and they will just be dumped. This way you don't have to actually worry about an inbox getting full as it will just drop anything coming in.
https://docs.aws.amazon.com/ses/latest/DeveloperGuide/receiving-email.html
In order to receive emails though SNS, you have to go through the setup linked above, but if you do not set this up, then emails will just bounce. At least, that is how I have been doing it.
I'm developing a CEP application prototype using WSO2 DAS. As a result of my flow, I have a final event stream (attr.: email address, subject, text,...) wich I want to send by mail to the address from the attribute of current event. But using WSO2 DAS I can send only simple letter to the fix address list.
I've started to read WSO2 EI documentation. I suppose, I will be able to use HTTP publisher in WSO2 DAS to send request to WSO2 EI and develop additional logic there.
Is it right way for my case?
Alex,
In DAS email publisher's 'to email address' and subject are treated as dynamic fields which means you can injects values from event to those fields. To do that you can use double curly braces. Ex:
Subject = {{subject}}
https://docs.wso2.com/display/DAS310/Email+Event+Publisher
Hope this answers your question.
Yes! Send message to wso2ei give you potential change your notification to sms or logs it or add guarantee delivery for your notification. For example whats would be happen if after event your email server will be not respond. In wso2ei you can do sequence of it.
Currently sending emails with Django, and was wondering if there was any way to periodically check my inbox with Django (or ideally somehow alert the server upon receipt of a new email), and have Django extract the message and save it in the database.
You could use an email service such as SendMail or Mandrill (latter definitely has free accounts, former may have).
Each of these services provide inbound email support via webhooks. You provide them an endpoint to hit (make sure to use HTTPS) and when they receive an email to an address you have registered they will send the data via HTTP POST to you.
It is then just a simple case of storing this data to the database. There are a number of 3rd party packages that can help you with this:
http://djrill.readthedocs.org/en/v1.4/usage/webhooks/
https://github.com/yunojuno/django-inbound-email
https://github.com/jpadilla/mandrill-inbound-python
https://github.com/michaelhelmick/python-mailsnake
Although it's rather simple to roll your own should need be.
I know that we can receive emails into rails app using ActionMailer configuration or using griddler/mailman gems. But is that possible to receive unique emails?
Ex: When a user is signed up into the app I create him a unique email address.
When the user sends an email to that unique email address rails app should receive that email.
I used google to find the solution but couldn't get the answer. Please help me(reference links are also much appreciated).
no complete solution, but an idea: you could set up a catch all email address on your mail server that receives all mail sent to your domain.
then, in rails you use the mailman/mail gem to receive mails sent to this catch-all address and process it depending on the To header.
I am working on django and sending emails to multiple users at once. in the given scenario it only tells me that if it has sent or not.
I want to display the report of same page that how many emails has sent to user successfully and how many not. more if i want to get details why email has failed to sent.
How would i do such things via SENDGRID APIs.
There are two options that I know of:
Connect to SendGrid Event Webhooks and start parsing events for every email to flag ones that were not sent. I believe you can configure SendGrid to only send certain events, so if you're interested in bounces you don't need to worry about handling all events.
The second option is to use a service like sendwithus which will connect to your SendGrid account on your behalf and track all bounces/opens/clicks for you and provide a simpler API/UI to view the data. I believe they do this via SendGrid's webhooks, so it's effectively the same solution but written for you.
Happy to elaborate on either, I've used both before.