I am using Windows Server 2012. I followed following URL for configuring IIS smtp
http://blogs.technet.com/b/yashgoel-msft/archive/2012/10/26/configuring-outgoing-email-settings-in-sharepoint-with-gmail-smtp.aspx
Now my problem is my email are stuck in queued folder, I feel like as I have 2-step verification in gmail account is getting reject. So I change password in my smtp to application specific password. But still same problem.
So now I wanted to know what can be the problem. Is there any tool from which we can say that smtp of gmail is rejecting email.
Hope somebody can help me over here
I found the issue, actually my network team had block 25 port on our network.
Related
i have many application servers (cyber-ark, SIEM solution, forti gate etc') installed on azure as a IaaS.
all of them connect to an smtp server in order to send notifications via mail.
on my on Prem deployments, this was not an issue, but on azure, all smtp communication seems to be blocked.
i created a send-grid account and tried playing with it, but the send grid smtp server is getting blocked too.
what is the right way to work in this scenario ?
i need a smtp server to integrate with my applications...
what should i do ?
thanks,
david
Depends on your type of subscription, pay-as-you-go if you want the ability to send email from Azure VMs directly to external email providers (not using an authenticated SMTP relay), you can make a request to remove the restriction. Requests will be reviewed and approved at Microsoft's discretion, and they'll be granted only after additional anti-fraud checks are made. To make a request, open a support case by using the following issue type: Technical > Virtual Network > Connectivity > Cannot send email (SMTP/Port 25). Make sure that you add details about why your deployment has to send mail directly to mail providers instead of using an authenticated relay. More details
When I have been trying to access gmail through browser and when proxy been enabled, I have been getting "sec_error_untrusted_issuer" and can't able to proceed further. I feel this is some security implementation by gmail to not to sniff it's requests & responses. am I right? or is there something that I have to configure in proxy (fiddler/open source tools).
Also, could you please let us know the details/background on this. and how to implement this type of security feature in applications.
The error message in question simply means that the client has not been configured to trust the root certificate authority that issued the certificate it received.
One way this would happen, for instance, is if you enabled HTTPS decryption in Fiddler, but when prompted to configure Windows to trust the Fiddler Root Certificate, you chose No.
I simply added the following SMTP details:
What's wrong with my configuration then?
Why is that I can't receive any new emails on my gmail account.
Please help me with these. Thank you.
I recently came across this issue. Specifically for Gmail I had go to my Google Account Settings and first enable 2-Step Verification. Once that was enabled I could create 'App Passwords'.
This creates a custom password for login and bypasses the 2-step verification. Copy and paste that in your password for login.
The reason this did not work for me even without 2-Step verification enabled is because it was presenting the application originally with a Captcha to solve.
We are having issues with Connect notifications from our DocuSign demo account.We are not able to receive any updates from our Connect configuration. Though, when I republished the XML from Connect logs, I did receive a Connect update to a specified URL.
When I created new envelopes using API as well as from DocuSign account itself, I never got any notifications to the same URL.I do not even see a Connect log.
We do not have any issues with Connect notifications for our DocuSign live account.
We have never experienced this issue before with Connect updates from our DocuSign demo account.
Please advise.
Just a hunch - do you use http or https? connect can only work over port 443 with a valid SSL certificate. If you're on localhost - you may need to get a temp certificate or something like that but also using azure websites is good way to avoid this issue since they're pretty much just as good as working on your localhost
In control panel there is a option to turn on certain features that are not installed by default. When you turn on IIS feature it has an option called smtp email. Does it refer to smtp service or smtp server? I have looked for the answer. But there is no concrete answer. Some say it's a service others say it refers to server. Can anyone please help me with the confusion??
The SMTP service under IIS is a simple relay agent. You really cannot use it as a mail server, as there is no real interface for retrieving (reading) emails from that service.
You typically use the SMTP service as a sending buffer for outgoing emails generated by your server (e.g. website). You configure the SMTP service as a relay for outgoing emails (e.g. to a smarthost) and then you can have your website generate emails to the local SMTP service. This way your website is not affected if network or other server problems would affect mail sending, as the SMTP service queues the emails you generate and can automatically retry deliveries etc.