I'm currently testing multiple user profiles for a new system.
These users will all be using outlook.com, and an outlook plugin.
I need to test about 5 different profiles/addresses for outlook.com. I've been barred from creating more accounts.
What is your solution when testing multiple email profiles/accounts, where a few developers would need access.
Thank you
I'm going to create Microsoft aliases and use mailbox filtering for my testing.
https://support.microsoft.com/en-au/help/12407/microsoft-account-manage-aliases
Related
I have a web application that utilizes several CRM types of emails for notifications, appointment reminders, attachments for digital sales and such. My clients can use my own admin domain email account to send these emails (no-reply email), or they can provide credentials for using their own SMTP server or relay service so that any emails that are replied to are sent to them (vs a no-reply admin email).
However, I'd like to try for a 3rd option where I can create an email mailbox on my a domain like so:
client1#mydomain.com
client2#mydomain.com
...
And then I would apply a forwarding rule on each one to send any replies to their personal email accounts so they wouldn't have to have their own SMTP service.
Now I can do this using providers' interfaces, but I'd rather do it with an API so I'm not having to manually create mailboxes and setting forwarding rules.
Currently I'm using AWS SES for my domain emailing, but I've searched for hours and the "solution" to create mailboxes and create rules to forward are ridiculous.
Are there any other email providers out there that make this easier? I don't need anything fancy except the ability to create a bunch of email mailboxes via API (preferably with a high limit of mailboxes) and the ability to create the forwarding rules via API.
Or can anyone recommend a good email provider that allows for a lot of mailboxes and makes forwarding really easy (and of course cheap).
Like "cringe" GoDaddy Email or something similar??
After a lot of research, this procedure doesn't really make sense these days. There are a lot of relay email providers that make it easy to set up "Senders" so that emails can appear to come from any kind of email account (personal or domain based) for ease of use with applications
I'm writing a program that should send emails to multiple users with content extracted from an excel spreadsheet. I know how to do this using the net/smtp package in Go, but I would like to know if it's possible to send an email with the sender being a google group (i.e googlegroup#gmail.com) instead of my email without resorting to using the gmail API? Currently I have a working program that can log in through an email and password, which is then used for auth credentials, but seeing as that google groups don't have the same kind of interface I'm not quite sure how to change it so emails are sent from a group instead of an individual user.
Each google group should have an email address associated with it. golang-nuts is golang-nuts#googlegroups.com for example. Any mail sent to that should be posted to the group, assuming it is from a member of the group.
In order to send from your own gmail account, you can use gmail's outgoing smtp feature with the net/smtp package. Configuration is explained better on this digital ocean post
I'm looking for a way to allow Yahoo application to read user's emails over IMAP. It works well for old applications (that were created before Yahoo Mail API has deprecated), but trying to access IMAP for new applications gives me an error
[AUTHENTICATIONFAILED] (#AUTH007) Bad scope.
Unfortunately, I have no idea how to add a correct scope for accessing IMAP for new applications. During creation of the app, I was not given a choice to add scope with name even looking like 'mail'.
Is Yahoo API just broken or there is some tricky way to work around?
Contact imap-service#yahoo-inc.com
With your Yahoo.com email address and
Brief description of your product.
How will your product use Yahoo user's email content?
How will your product help Yahoo mail users?
What market do you serve?
What is your product's userbase?
A client insists on moving from Notes/Domino to Office365 (no further comments on that please). There are some mail agents that provide automated functionality. In one case, it is an agent in a mail database that, when it receives a mail, it responds with a mail that contains a unique reference for the mail just received. It's their way to generate unique mail references.
How to create an alternative solution, in Office 365? Can one develop an agent in Office365?
If it must be an equivalent solution, does it have to be an Outlook client that's always on?
Or are there other ways to generate reply mails from a special mail account?
Can one send a mail to an SQL server, for instance?
I'm open to all your suggestions! Thanks.
I'd do some research into what's currently available for Office365 users via Exchange Web Services - or better yet, the Exchange Web Services Managed API.
Assuming that you Office365 gives you full access through Exchange Web Services, you can write code to use the subscription/notification services for the mailboxes that you want to monitor, and then have your code send the emails.
There may also be better ways.
So we are planning to use AWS SES for sending emails. But how do we set up the email receivers? And how do we create an email accounts? When activating AWS SES, it asks to verify an email account (eg. help#example.org)...
I tried to create a mail server on one of the instances using postfix following this article: http://flurdy.com/docs/postfix/, but it's not easy at all... Does anybody know any better alternatives?
Thanks.
SES is for sending email only. As you note, you must have some other way set up to receive email at least at the "From" address you intend to use, because Amazon will verify it before letting you send.
While you certainly could set up an email server and domain on an EC2 instance, it's very complicated. I recommend that you get an email service for just that purpose. If you only need a single address for all your messages, just get a free address from Google, Microsoft, Yahoo, etc.
If you need multiple addresses, consider getting Google Apps for Business, either for an existing or new domain name (it's easiest to set up if you have it register a new domain name for you). It's no longer free, but it's still quite cheap. A single user account can receive emails for every address in the domain, it's flexible, and it's reliable. It's a good companion to using SES for sending automated emails.
Use Amazon WorkMail if you prefer AWS. Gmail for work, Office 365, Hostgator, are some other examples. FYI, none of these providers simply provide domain emails. They come bundled with many other things such as chat clients, calenders, etc. Pricing of these services depends on what other things they are bundled with.
$4/user/month for AWS
$5/user/month for Google
$5/user/month for Microsoft
Since you are in AWS cloud, I will tell you a few things about Amazon WorkMail.
You get your own domain and 50GB of storage per user.
You get calendars for free.
You cannot use just any desktop mail client. You have to either use Outlook, or Mac's mail client, or the web interface. This is their weakest point. However, including other IMAP clients is in their roadmap (I guess atleast a year).
Integrates nicely with SES.
Important links:
FAQ page.
Features page.
There are many more features such as remotely removing emails from a device, managing your users, and so on.
What I can recommend you is to use Amazon WorkMail because they almost provide all the features supported by others, and you are tied with AWS anyway. AWS also recently launched Workspace and Workdocs (both separately billed) that will allow you to create a complete work solution. These services also combine nicely with IAM.