To troubleshoot the issue I have set up an XSLT file that uses the umbraco.library:SendMail() extension method and I have created a Contour form using the Contact Us template.
Also, I created an ASP.Net web control that creates a MailMessage and sends an email. It's very barebones but uses the SMTP settings from the Umbraco web.config file.
Our SMTP server belongs to our client and we do not have direct access to it so I can't check the logs.
Our client wants the "from" address of emails from the site to be "[email protected]" (I'm obscuring their actual domain for privacy reasons).
- Contour forms with email sending workflows: no email received
- Default Contour contact us form: no email received
- XSLT using umbraco.library:SendMail(): no email received
- My test asp.net web control: email is received
With the site configured to send "from" my personal work email address we get:
- Umbraco notifications: no email received
- Contour forms with email sending workflows: email is received
- Default Contour contact us form: email is received
- XSLT using umbraco.library:SendMail(): email is received
- My test asp.net web control: email is received
I can also run the same tests with a bogus email address: [email protected] and we get:
- Umbraco notifications: no email received
- Contour forms with email sending workflows: email is received
- Default Contour contact us form: email is received
- XSLT using umbraco.library:SendMail(): email is received
- My test asp.net web control: email is received
There are no messages in the Umbraco log database table to help us track down the problem. It's almost as if Umbraco has an issue with the email address [email protected].
So what I know at this point is:
- The SMTP server does relay emails and will relay emails "from" [email protected].
- Umbraco Contour form workflows will send emails "from" any email address BUT [email protected].
- The XSLT extension method umbraco.library:SendMail() will send emails "from" any email address BUT [email protected].
- My test ASP.Net web control will always send emails "from" any address.
Does anyone have any ideas on why Umbraco would have an issue with this one email address? And why do we get some emails but no Umbraco Notifications?
Our client had a configuration problem with the email address they gave us to use. We changed it for another (a known valid mailbox) and now email sending works properly (including Notifications).
Hello, we cannot get Contour forms to send emails, though the recipients are setup and the mail settings below are correct. We tested these mail setting in code outside of Umbraco and it worked. However, we cannot get it to work in Umbraco. We have tried several configurations of this as well and no success. Any ideas?
Yes, here's the code from the umbracosettings.config. This is odd that it wont send as we've tested the email connection outside of Umbrao and can send email.
<notifications>
<!-- the email that should be used as from mail when umbraco sends a notification -->
I tried the send email workflows in Contrib. Tried: Send Email, Send Email Extended, Send XSLT Transformed Email and none worked. Thanks for your help!
Any luck finding a solution Greg? I'm experiencing a problem just like this. Contour is not sending e-mail with the normal send e-mail workflow type. Tea Commerce can send e-mails from the same website, so it's NOT the smtp.
Like you the the smtp needs both a username and a password. Might have something to do with that, Tim?
Contour not sending emails problem
sigh ... sorry for the formatting. When I try to edit the post I get an XSLT error.
Comment author was deleted
Hi Chester, I think this is more a smtp server issue, just use a valid sender email address.
Regards,
Tim
Hi Tim,
Our client had a configuration problem with the email address they gave us to use. We changed it for another (a known valid mailbox) and now email sending works properly (including Notifications).
Thanks!
chester
Hello, we cannot get Contour forms to send emails, though the recipients are setup and the mail settings below are correct. We tested these mail setting in code outside of Umbraco and it worked. However, we cannot get it to work in Umbraco. We have tried several configurations of this as well and no success. Any ideas?
<system.net>
<mailSettings>
<smtp from="[email protected]">
<network enableSsl="true" host="smtp.gmail.com" userName="[email protected]" password="xxxxxxx" port="587" defaultCredentials="false"/>
</smtp>
</mailSettings>
</system.net>
Can anybody help?
Comment author was deleted
@Greg, did you update the sender email in the /config/umbracosettings.config ?
Yes, here's the code from the umbracosettings.config. This is odd that it wont send as we've tested the email connection outside of Umbrao and can send email.
<notifications>
<!-- the email that should be used as from mail when umbraco sends a notification -->
<email>[email protected]</email>
</notifications>
Comment author was deleted
Could you try the workflow that's part of contour contrib: http://our.umbraco.org/projects/developer-tools/contour-contrib,might be the ssl that is causing the issue
I tried the send email workflows in Contrib. Tried: Send Email, Send Email Extended, Send XSLT Transformed Email and none worked. Thanks for your help!
Comment author was deleted
Hmm doubt that its a Contour issue the, have you tried of the umbraco notifications get emailed (so as a user subscribe to a notification like create)
Any luck finding a solution Greg? I'm experiencing a problem just like this. Contour is not sending e-mail with the normal send e-mail workflow type. Tea Commerce can send e-mails from the same website, so it's NOT the smtp.
Like you the the smtp needs both a username and a password. Might have something to do with that, Tim?
/Rune
i am having this issue as well. I have the correct email address setup in the umbraco config, as well as in the SMTP have the ip of the mail server,
Comment author was deleted
@Ryan does the smtp also need a username and password?
Comment author was deleted
@Ryan any update on this?
We got it corrected late last night. It was the ports on the firewall to allow port 25.
Comment author was deleted
Ok thanks for the update :)
is working on a reply...