email notifications from SQL Server job - sql-server-2008-r2

We want to set a profile in Database Mail on SQL Server 2008 R2 for all the developers in our team to receive notifications once an overnight job has completed.
Unfortunately, in the Notifications properties in the job it only allows us to select one of the Operators (Data Management Developers) and the problem with using the Operator is that there is a 100 nvarchar limit on how many characters (and therefore how many email addresses) can be added.
How can we select the new profile for notifications? Do we have to delete the Operator?

If you have access to administering your email subsystem you can create dedicated email account for Operator and configure email forwarding from it to all recipients you need. This simplifies database mail administering as well as email subsystem administering.

Related

Allowing mail delivery against a SQL db

My questions is regarding with MIMEDefang and I tried to reach their public mail list but after 1 week nobody accepted my join request. Also, I've already asked similar question to their mail list and i got no answer yet.
I'm trying to change the behavior of our Postfix mail server which is used for e-mail delivery to the customers. It doesn't accept any e-mails from the internet. A couple of weeks ago, the government decided to change mail delivery options for all banking industries. Basically the government add some some basic rules regarding with "gdpr" which should be applied for all outgoing mails to the banking customers. There is an options list to state customers desires about what kind of e-mails allowed to deliver their personal mail accounts. The mails could be 3 or 4 different types. For example, bills for payments, campaign mails, sending and receiving money receipts and so on. The policy says, if a customer specifically states that any of these mail types could send him, we can process it according his/her preferences. On the contrary, if a customer receives any mail other than its preferences the bank will face penalties for that behavior. I decided to use MIMEDefang to achieve this policy. The requirements listed above, drive me to use sql or redis service along with MIMEDefang because this list could change in time. I guess right on the "filter_recipient" time, I have to connect sql db to check whether the user allowed this mail to deliver its personal mail account. Is it possible to use sql (postgresql, mariadb,) with MIMEDefang ? I'm not certain about which callback is the right choice here to query that. May be "filter_end" is better than "filter_recipient" callback for this particular check because there is another condition which needs to check/determine the type of e-mail.
The second condition is the type of e-mail. I have to look at the contents in the DATA portion of e-mail and find out the type of e-mail. I'm going to tie these two conditions and decide to allow or drop e-mails individually. Also, there are 90K customers and we were delivered 30K mails per day at most.
I would like to ask some questions about SQL and MIMEDefang.
Is that possible to use SQL queries with MIMEDefang to validate recipients and its preferences ?
Is there any drawbacks while using SQL services with MIMEDefang ?
Where can i tie these conditions with each other ? Which callback is eligible to process these two conditions together ?

Writing a job that can access office 365 email and migrate them elsewhere

I need a little help understanding a task I have been given.
I started work on a 'SharePoint focused' team and we are trying to create a SharePoint portal that would house/manage all incoming mail to a specific company email address.
We have had a couple of issues setting up SharePoint to accept incoming mail, so have begun looking at other possible options.
1 option that was suggested was to 'write a job' that would read our mailbox server (on Office 365), and then find, pull and migrate/copy selected emails onto the sharepoint site.
(something else we are also interested in doing is seeing what info we can grab from these emails at this stage which we can use to create various mail objects in sharepoint with the mail metadata. Not sure what limitations there are to what can be accessed, if anything)
Is somebody able to explain a little more the type of process or work that is required to do this (access Office 365 mail via some API which we can create a timed job for), and any experience or advice around it? Where would I start looking or how would I start implementing it, etc.
Thanks!
You combine couple of things together. SP can read incoming emails through locally installed and configured SMTP server. You can then setup document library or list to store them or create event listener to handle incoming emails completely by your own.
But both cases (OOTB functionality or event receiver) rely on local SMTP. If you want process emails from other server like Exchange Online you must either forward these emails to local SMTP server installed beside SP or you must create your own code. It can be SP job or any other type like windows service or console application executed by windows schedule, ... calling Exchange online API (designed specially for Exchange online) or MAPI or POP3 (generic using libraries) to get emails and calling SP API (CSOM, REST API) to store emails.

What email server or online email service allows for creating unlimited email alias for an inbox (via API)

Here is the reason for my peculiar question:
I am working on a mortgage application for a mortgage broker where each mortgage application is a record. Now this broker will take each of the applications he has received and enter this application (in an up line lender's system) and during the life of this mortgage application, he receives notification emails about updates from the up line lender.
It is required that in this application, all emails pertaining to a particular mortgage application are visible under that record.
My plan is to have all emails collect in a single inbox, and give that inbox an alias corresponding to the record id of the mortgage record. The alias remains active as long as the mortgage application is active and the broker cares for receiving these updates. Once the mortgage application record is dead, that alias is removed.
When displaying the particular mortgage record, I can query the mail server for the emails where the to address is the alias of that particular record.
My key requirements are:
The email server or email service should allow for about 400-500 aliases at a time.
Should have an API interface for creating and deleting an alias.
As far as the creating/deleting API is concerned, Google Apps (https://developers.google.com/admin-sdk/directory/v1/guides/manage-user-aliases) really fits the requirement, but has a 30 alias limit.
Does Microsoft Outlook online mail support this kind of API and ability to create mailbox alias?
If we went in the direction of having a Microsoft Exchange Server 2010/2013, would it allow programmatic access to create aliases? What would be the license cost?
Thanks in advance for looking this up.
With update from #mti2935, I am considering a catch-all solution rather then deal with creating aliases.
So, now I think all I need is to be able to process the emails. What's the best means of processing emails (in my case, I will simply have to look at the "to" field and put the emails in different buckets).
I have found a third party service that can help me parse emails. Definitely going to try that out and provide an update here.
Service: https://postmarkapp.com/inbound
Referenced by a post on: How to setup a mail server?
One option to consider is to setup a mail server using qmail, configured as a catch-all for your domain, such that all mail to *#yourdomain.tld forwards to a script which parses each incoming message, scrapes the to, from, subject, etc. logs the messages in your database, etc. It's easier than it sounds to setup. See How to setup a mail server?. This can be done fairly inexpensively on a Rackspace or AWS cloud server.

Mail Client in Cloud used for Backups

I'm new to cloud storage and I'm wondering how a mail-client that is running on, say a rackspace server running RedHat, stores emails locally on it's machine so we can back emails up. I am trying to find the best mail client that can fit these requirements:
Backup of these email accounts is as follows:
1) Each email account must be backed up individually on a daily basis
2) We must be able to reconstruct our mail account as it looked on some past date.
3) Emails among these email accounts cannot be mingled. In other words, if we are asked to restore our "support" mail account, we should not be including emails from our "reports" mail account.
This client will:
1) Sit on a secured server accessible by us
2) Connect to each target email account over IMAP, securely
3) Synch down all emails for each account and retain emails on the file system. Each mail account must be stored in a location that is distinct from the locations of other accounts we are backing up (per regulatory requirement above). Thunderbird, for example, supports the notion of Profiles.
4) Each Profile maintains its own distinct folder structure on the fs. Each Profile is then responsible for pulling data for only of the mail accounts.
5) Mail stored within these profiles should be encrypted with the security key in our possession. This requirement will most likely be satisfied by the server infrastructure we select, ie the cloud servers at amazon will run on an encrypted file system.
If anyone has any ideas for an ideal replacement to thunderbird that would be of huge help.
Thanks,
Connor

How to receive emails of the same inbox from multiple server instances

I have an application running on WebLogic Server with 6 instances. Many requests for the application come from Email. We already set up an email account that will be used by all clients to send email to. But the problem is that the email account inbox can only be opened for reading by a single connection, unlike a typical database.
Currently I can only deploy the email reading service on a single server instance, this will effectively create a single point of failure and unbalanced load. What's the best way to read from the same inbox from multiple servers? I am thinking developing something using a database table, sort of leasing, whoever locked the table own the lease and can connect to the email server, but this is pretty hard to implement correctly in all circumstances.
I am not sure why you say that only one client can access the inbox as POP certainly can handle multiple connections to the same inbox and this can be configured in the mail server. You might need to talk to your mail server admin.
I haven't worked with Weblogic to give you a specific answer, but you should also be able to have a service written that checks the incoming mail and process incoming mails into a database as you wanted. Once the information is in a database, you can use it via multiple hosts. This is a better approach as this can be setup to prevent multiple clients responding to the same email.