In looking at amazon's SES API documentation it looks as if there is no clear cut way for sending attachments unless a raw email is created. Where as when using an SMTP Client to amazons SES sending emails with attachments seems more manageable. Outside of the messageid returned from the SES API is there any benefit to using the api over the SMTP client? Or am I completely missing the boat and there is an easy implementation of adding attachments to an email in the SES API?
I use SES all the time, have never felt a need to use anything other than the SMTP interface - which is a simple drop-in replacement for any other SMTP service you may be using. Unless you have a compelling reason (and I can't think of any), use the regular old SMTP way. Then if you ever need to move off, it would be trivial to switch to another service.
Well, the main reason to use the api is you can set a domain key to improve delivery success rate. This is useful if you send a huge amount of emails. In general, unless you have an easy way to implement the api (like django-ses or similar) just stick with SMTP.
Related
Its really frustating that EmailComposeTask doesn't have any way to send attachments. I googled this and found MailMessage dll. I don't know whether it is secure or not because user gonna send his password.
Now I am thinking tot build my own service, send data from phone to service, and service will use smtp to send email with attachment.
Now I want to ask, Am I right? What kind of service I use?
I dont know about security concerns of MailMesssage.dll.
However, if you wish to send transactional EMails, then there are few services available. In such a case, you will not be required to create your own service. The popular one's are:
Sendgrid
Mandrill by MailChimp
MailGun by Rackspace
All services provide free tier and may be helpful, if you need to send, less EMails. Moreover, besides SMTP, these services provide Web APIs, so you can send mails using REST interface.
Does Gmail support RFC 821? I know it is using ESMTP. Based on understanding ESMTP is RFC 1869. But I must use RFC 821 commands with C# and want to test it. If Gmail doesn't provide support, is there any server provides this service for developers?
Thanks in advance
RFC1869 defines a set of extensions to the SMTP protocol that a server can support. They come in addition to the standard SMTP protocol described in RFC 821. In other words, any server that supports RFC 1869 must also support RFC 821. The newer standard makes this explicit:
4.1. Changes to STD 10, RFC 821
This specification is intended to extend STD 10, RFC 821 without
impacting existing services in any way. The minor changes needed are
enumerated below.
If a client connects to such a server and issues a standard HELO command, it should get a server that speaks SMTP. If you need to use any of the SMTP extensions, though, you need to instead issue the extension command EHLO, which indicates a client that also speaks RFC1869.
However, just because the server speaks SMTP doesn't mean it's going to speak it with you. In particular, the server may require authentication as per RFC 4954 (e.g. require an AUTH LOGIN or similar command, or a STARTTLS command for encrypted communication). If you fail to properly authenticate before issuing a command, the server could legally send an SMTP error. While this error would be a legal SMTP response per RFC 821, that's probably not going to help you out very much.
RFC 1869 (ESMTP) is a refinement of RFC 821 (SMTP), not a separate protocol. You can still talk basic SMTP to an ESMTP server -- in fact, ESMTP servers are required to support it.
Since it sounds like you're trying to build something that interoperates with GMail SMTP, keep in mind that it's not intended for use by anything other than a desktop mail client. Trying to send bulk mail via GMail will end badly.
Almost all Internet Service (connectivity) Providers (ISPs) offer an SMTP server for their customers to use to send email. Your ISP's help page undoubtedly explains how to do this -- it probably mentions something like smtp.comcast.net or smtp.whatver.net.
It is quite likely, though, that they won't let you send more than a certain number of email messages per day through that port. And, they certainly won't let you send any messages through it unless you're on a machine on their network.
You may also be able to use gmail's smtp server. But, in order to do this your client software will need to be able to use TLS, port 587, and authentication (using your gmail username and password). See here:
http://support.google.com/mail/bin/answer.py?hl=en&answer=86374
This need for authenticated and encrypted communication with the smtp server could prove to be quite a pain in the neck for your work of debugging. Best to find an open SMTP server you can test things with.
The good news: RFC821 is pretty doggone simple.
Yahoo can send email to rfc821 mail server.
And another tool that is amazin is https://www.wormly.com/test_smtp_server
A website that I used my password on was compromised and the monkeys in charge had stored everything in plaintext. The list was released publicly online. Needless to say, my password and email were among them.
I would like to send emails to everyone else who was listed (thousands) and inform them that to continue using their password is unsafe. My language of choice would be C# and I would be sending them from my gmail with the help of this code: Sending email in .NET through Gmail
I can pretty much assume gmail will lock me out before I finish 10 in under a minute. Apart from sending emails out intermittently, how can I do this?
edit: I agree with the responses. I should instead send one email. Is there a limit to the amount of recipients I send an email to from gmail?
If happy to spend a bit of money for a reliable solution, you could integrate (very easily) with http://sendgrid.com. Provides you with heaps of features to track delivery of email and reporting/analysis of email opening, clicking etc.
Gmail does have limitations on how many emails you can send per day, and I would not recommend for your usage.
Or use some online mail marketing tool like MailChimp http://www.mailchimp.com
This service can easily send thousands of e-mails without problems. They have a free service too. Where you can store up to 2,000 subscribers. Send up to 12,000 emails per month.
It even has a REST API available for interacting with it from a custom app.
However I don't know if you are legally allowed to sent e-mails to the addresses on the list. I know it's for a good cause, but please be warned that this sort of e-mails can be considered as spam.
Again, don't build it yourself, but use off-the-shelf specialized services: I suggest looking at
Amazon Simple Email Service (SES)
which is part of Amazon Web Services (cloud storage, computing and more).
Amazon SES lets you send bulk and transactional email to customers in a quick and cost-effective manner
Service highlights include:
Simple
Inexpensive
Reliable
Scalable
We have a website sending mail alerts to end users. The site has been developed in c# ASP.NET.
I want to find the best way to send the email alerts to my users. Making sure the mail is not trapped in any spam filters. I read on the internet it is best to sent the mail directly from the web server and not route via an SMTP mail service such as google apps or Postini.
Can anyone tell me if this is correct?
First of all
Making sure the mail is not trapped in
any spam filters
Is not possible - otherwise spammers would do this. You just have to make sure you're domain isn't associated with any spamming activities and watch for keywords within the email.
I read on the internet it is best to
sent the mail directly from the web
server and not route via an SMTP mail
service such as google apps or
Postini.
This point doesn't make sense - your e-mail will never be delivered if it doesn't get routed via an SMTP server, the average message will pass through multiple on its route to the recipient.
The answer is to not actually send email and let someone else deal with the problem. I'd look at postmark or Amazon's simple email service.
We had problems that mails sent with local server often get trapped in spam filters until we implemented SPF on our mail server.
http://en.wikipedia.org/wiki/Sender_Policy_Framework
But I am not admin, that's just what our admin said, and after that we have no problems anymore.
btw. maybe would be better to ask on serverfault.com
I need to forward emails for a several domains to other email addresses. Previously I have used hMailServer on my Windows server to perform this forwarding function, but I am looking for something simpler that I can interface with from a .NET application.
Is there a simple email forwarding server I can easily manage from .NET? Spam filtering or email storage is not required.
I've never used hMailServer but according to the documentation there's a COM API that looks like it would be automation compatible (since they've got VBScript samples) so you should be able to access this from .Net.
I'd suggest looking at the Rule object or the forum