I am looking for the component that interacts with the email client and passes credential for further authentication within Dovecot.
I am also looking for the component that passes from the mail process to the email client.
Related
Our application currently supports sending emails via SMTP. We have some customers who have enabled MFA and managed to get it working by setting an App Password which we use when sending the email via SMTP.
We have another customer who has MFA enabled and has also disabled the use of App Passwords. Given that we cannot use app passwords and MFA is enabled, is it possible to send via SMTP or is there another way of potentially sending using the API that works with MFA?
I'm attempting to understand how spring boot uses http sessions to manage the oauth authorization code flow.
I understand that after the user submits their credentials via the /login form spring will persist the authentication object so it can be retrieved when the browser is redirected to retrieve the authorization code.
What I dont understand is if the browser needs to sends jsession cookie to the server or http basic authentication header when invoking this flow.
For example if I wanted to initiate the flow manually via curl do I need to specify any special headers ?
It doesn't use HTTP sessions to persist it, the client ID and authorisation code (the code that's passed back to the client app after the user authenticates) is used to identify the authentication object. The authorisation code is then used to obtain the access token.
So:
The client app redirects to the auth server, passing in their client ID.
The user authenticates with their username and password on the auth server , which stores the authentication against the code and client ID and passed the authorisation code back to the calling app as a request param on the redirect URL.
The client app calls back to the auth server, authenticating with it's client ID and secret and passing in the authorisation code. This is then swapped for the access (and possible refresh) token.
If the app needs the user details, the client app calls the user details endpoint authenticating with the access token it now has.
I am using " Mailkit " to send emails from a dot net core console application (using smtp). It works when i run the application in my local machine and I receive emails.
However, when i deployed as an azure webjob, It does not send emails. I could see the job completes successfully and no errors logged. BUT i do not receive emails
I am just wondering how it works in local machine and it does not while run in azure.
Update:
Based on comments below, trying to be specific. can someone confirm if you were able to use Mailkit and an organizational smtp server(no public domains) & email account to send emails from an azure webjob ? or else please suggest what should be a working setup. thanks!
can someone confirm if you were able to use Mailkit and an organizational smtp server(no public domains) & email account to send emails from an azure webjob ? or else please suggest what should be a working setup. thanks!
No public domain means that we can't access the smtp server through the internet. As a workaround, you could save the mail information to a Azure Queue Storage from the WebJob and writing a new application and publish it to your internal network. In your new application, you could get the information from Azure queue storage and send the mail from your internal network.
my job contains a simple tSendMailCompenent
the configuration are as follow:
smtp host = smtp.gmail.com
smtp port = 465
beside the user name, email to, ...
also, I have allowed a less secure app for the Gmail account sending
the problem is after I run the job, the Talend hang up the job is running forever
I've never seen this component hang. It usually returns quickly if there is an issue.
Have you tried creating a simple Job with just the component so that you can establish that it is this component, on it's own, at fault?
Can some one explain me how to configure the send mail task is ssis 2012?
I don't where we need to assign our Mail password while configuring.
You specify the password when you set up the SMTP Connection Manager.
The MSDN page on SMTP Connection Manager has all the details.
https://msdn.microsoft.com/en-us/library/ms137684(v=sql.110).aspx
AFAIK, The out of the box Send Mail Task in SSIS only supports an SMTP Connection Manager.
Right click in the Connection Managers area and choose SMTP as the Type.
You will now be prompted to Enter the SMTP Mail Server connection details. The minimum required are the SMTP Server's address. The rest default to their default values. Ex: If you don't enter timeout, it defaults to 60000 = 60 seconds.
Once you enter the details and press OK, the ConnectionString property of the SMTP Connection Manager will be set (see example below)
It is a good idea / best practice to parameterize this ConnectionString property so you don't have to change code if the SMTP server info or connection details change at a later date.
I keep the SMTPConnectionString at the Project Level (not Package Level) so that it can be re-used across various packages that send emails.
If you need advanced control over this component, there is a 3rd party SSIS component provider that has something called Send Mail Task Plus. That lets you configure an email provider password and such, although I rarely see this need in the enterprise SSIS world.