This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon (
) is public.
Every repository with this icon (
commit 732c724df61bc8b780dc42817625b25a321908e4
tree c444d2594fc1bc6f3888d9eeb61b6b8417959d58
parent 6406a87eedb74a41f19f5ad21ea1b8f97dd45755
tree c444d2594fc1bc6f3888d9eeb61b6b8417959d58
parent 6406a87eedb74a41f19f5ad21ea1b8f97dd45755
... |
... |
|
... |
... |
|
... |
... |
|
... |
... |
|












NICE
I don’t think this should be turned on if the server doesn’t have a certificate. Not all servers do, and it broke my ExceptionNotification, so I realized it two days late.
This is causing problems for me as well:
OpenSSL::SSL::SSLError (hostname was not match with the server certificate)
Sounds reasonable that we should have an option or at least a fallback for this. Anyone wants to give it a stab?
While the issue remains – perhaps it’s helpful to point out a quick workaround if you’re using postfix.
Disable tls by setting smtpd_use_tls=no
if you are determined to use tls then really you should set up your certs/keys and enforce it with smtpd_tls_auth_only=yes
more details here: http://postfix.state-of-mind.de/patrick.koetter/smtpauth/postfix_tls_support.html alternatively -
This is likely a architecture oversight. I upgraded my system and it died cause the hosts were mismatched. This is common on hosting environments and there should be at the least, a option in the settings that either ignores it or at least gives the option not to use ssl.
This is causing a lot of problems for my Capistrano Mailer plugin when used with Rails 2.2.2. So essentially at this point, it’s either dig into postfix, or you’re SOL?
@pboling: We’re happy to take a patch to make this optional, roll it into 2-2-stable and have it fixed in 2.2.3.
Want to take a crack at it?
I took a crack at it. :)
Lighthouse ticket and patch here: http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/1731-make-enable_starttls_auto-opt-in-in-actionmailer
Thanks, darragh.
I am able to make it working by smtpd_use_tls=no
This is killing a lot of rails apps that need to talk to broken SMTP servers. josevalim is on the right track with the patch at http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/1731-make-enable_starttls_auto-opt-in-in-actionmailer
Yeah, and I really think it should be false by default! As soon people moves to Rails 2.3 and see that their mailers are not working properly, IRC and mailing lists will be very busy. :)
This won’t work with 1.8.6 correct? Is this causing woes to anyone else using non-ssl AuthSMTP?