I am trying to set up an SMTP server on a virtual private server. I have typically hosted applications with hosting companies in the past.
I am using SMPT on a website to send mail but need to configure IIS's SMTP Server to allow me to send the mail. I have a couple of questions around this:
1.What settings do I need to set to enable me to hit mail.myDomain.com and provide a user name and password for the mail to send?
2.What security issues do I need to be aware of and how do I lock down the SMTP server?
If you have an externally acessible SMTP server avalaible, just target it directly from your .NET code?
The <system.net> section in your config has some mail server settings you can use.
Related
I'm currently building a system where users can list Word and Excel files in an ASP.net webapp and click on files to edit which will open them up in Office from an IIS WebDAV server and allow the users to edit the files.
I have all of this working with Windows Authentication enabled and using the server's hostname to address the file on the WebDAV server:
ms-word:ofe|u|http://hostname/webdav/myfile.docx
However the client has a subdomain (resolved by internal dns on their network) and ssl cert they want to use for the site. When I address the file with this domain name:
ms-word:ofe|u|https://portal.domainname.com/webdav/myfile.docx
I get a windows authentication prompt when opening it in Word that will not accept my domain credentials.
If I switch the WebDAV server to Basic Authentication and set the domain Word will prompt for authentication and will accept my domain credentials, but it will prompt on every file I open.
Is there a way to address the file using this internal subdomain name that will open the files without prompting the user for authentication?
This will only be accessible on their internal network so I'm open to considering any authentication scheme that would achieve this goal.
Because of security reasons the client will not send credentials to hosts that are not recognized as local intranet.
When using a (sub)domain instead of a hostname every client has to add the (sub)domain to it's intranet zone:
Internet options > security > Local intranet > Websites > Advanced > Add.
This can also be done by using a Group Policy or setting a registry key.
HKEY_CURRENT_USER\software\microsoft\windows\current version\internet settings\zonemap\domains\[domain]\[subdomain (optional)]
DWORD name: http of https value: 1
I have a website; let's call it abc.com. It's e-mail is handled by Office365. I recently migrated it from a Sharepoint environment to a different webhost (GoDaddy). I have tried using the WP Mail SMTP plugin option to send e-mails, but it fails to send.
My settings are:
smtp: smtp.office365.com
port: 587
encryption: use TLS
authentication: use smtp
Sending fails with the error:
SMTP ERROR: Failed to connect to server: Connection refused (111)
Using the default wp mail with the settings below works to send to e-mail addresses outside the domain, but messages get flagged as spam on addresses within the domain.
header = 'From: '.get_option('blogname').' <wordpress#abc.com>'
I have e-mail routing set to Remote Mail Exchanger. I've tried adding the address wordpress#abc.com to Exchange's allowed list/whitelist, and I even tried adding the host IP to trusted IPs on the server - but it still doesn't work.
As far as I'm aware, GoDaddy do not let you send mail to external SMTP providers. If you're not able to choose another host (which I'd recommend if you can!), you'll need to use wp mail and send all mail to a local address at the same domain, hosted with GoDaddy.
If you wanted to, you could then set up an alias to send it elsewhere.
There's some more background on this over at wordpress.org, such as this thread and this thread.
EDIT
Just realised that the Postman SMTP plugin claims it can get around GoDaddy's filtering using HTTPS:
"Even hosts that block the standard SMTP ports, like GoDaddy or Bluehost, can't stop your email as Postman can deliver via HTTPS if it can't use SMTP."
So maybe give that plugin a go instead. :)
I ended up using the default wp mail.On the client o365 admin I added the email address to the whitelist. Made the mail rule priority over the default spam filter rule.I even went a step further to whitelist the IP but that's overkill I think.
What could be possible reasons why my app cannot send emails once it's moved to the production environment?
I'm using my private e-mail address to send these emails and I learned via admin that the server is not blocking this. What would be other issues to look for?
We are migrating from a dedicated server with a local virtual SMTP server to Windows Azure. As far as I can tell Windows Azure does not allow a local SMTP server to be setup in IIS. The SMTP Server option in the management console is missing. How would I setup an email relay so that I can have a .net web application send emails from a Windows Server 2012 virtual machine in Azure?
This is more like corollary to what #mcollier has stated. Given that you are already on Azure and you get 25,000 free emails (there are higher plans as well) with your subscription as well.
You can configure a Virtual SMTP server which relays to the sendgrid services. For the development perspective you will have the view of using your own SMTP server / service. Setting up a sendgrid based service is explained in this link.
I have used sendgrid earlier and my experience with this was amazing. As #mcollier has pointed out, using services like Sendgrid will give good chance of staying away from spam problem, if you try to setup and use the SMTP service of your own because of the reverse lookup etc.
PS: The above Virtual SMTP Server can be replaced with Amazon SES, which is equivalently a good service. Check out more info here.
First, assuming you're using a Windows Azure IaaS VM. Correct? If so, I think you need to enable that role/feature in Windows Server.
Second, why the need to send emails from that specific server? Would a service like SendGrid work? One problem people sometimes have with email servers in Windows Azure is the domain of your service (something.cloudapp.net) does not match your vanity domain when a reverse DNS lookup is performed. This could cause the email to be flagged as spam (since you don't technically own the sending domain, something.cloudapp.net).
I developed an direct relay application using the normal RFC email commands and lock that on my application, but strange that some test emails get delivered using the relay on windows AZURE VM, and all other mails are not getting any bounce response, and making a sense that every email is being delivering,
This is strange behaviour on azure vm.
so it means you can't send email using azure vm as a smtp mail server, if like to test then simply download promailer marketing manager from jsmtp.com
I am creating a banking application in asp.net v 2.0.I need to send confirmation email when a user creates the new account.
I am running the application in localhost.DO I need any special rights to send SMTP email?
provide me a proper way to send email from my application.
Regards
Jeyaganesh
Do you have a SMTP server set up on localhost? Test by using telnet on the server:
telnet 127.0.0.1 25
If the server responds, try sending raw SMTP commands to send an email and trouble-shoot from there.
I find the easiest way with the Microsoft SMTP server is to disable any checks for authentication and rely on relay restrictions, then restrict relaying to 127.0.0.1.
The fact that you're running on localhost shouldn't make any difference.
As long as you have valid email server settings, and it's allowed on the system you are running on, this works just fine.
Did you try it? Did you have a problem?
I think you can sent by gmail smtp server. check this out
http://csharpdotnetfreak.blogspot.com/2009/08/send-email-using-gmail-in-aspnet.html