-
Notifications
You must be signed in to change notification settings - Fork 935
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mail attempts to decode a mail message twice when using exim #814
Labels
Comments
Thanks for this. Are you able to write a test that demonstrates this behavior? |
Hi Ben Regards Mark On 15 January 2015 at 14:14, Benjamin Fleischer notifications@github.com
|
same question /root/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/mail-2.6.4/lib/mail/network/delivery_methods/exim.rb:47:in `block in call': undefined method `encoded' for #<String:0x007f8fd34eec28> (NoMethodError)
from /root/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/mail-2.6.4/lib/mail/network/delivery_methods/sendmail.rb:73:in `popen'
from /root/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/mail-2.6.4/lib/mail/network/delivery_methods/sendmail.rb:73:in `popen'
from /root/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/mail-2.6.4/lib/mail/network/delivery_methods/exim.rb:46:in `call'
from /root/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/mail-2.6.4/lib/mail/network/delivery_methods/sendmail.rb:57:in `deliver!'
from /root/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/mail-2.6.4/lib/mail/message.rb:253:in `deliver!'
from email.rb:17:in `<main>' |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When trying the basic example in the readme with exim, I only received and error:
The mail message should have been an instance of the Mail class which respond to 'encoded', not a string.
It turns out the encoded is being called twice, once in the super class(Mail::Sendmail) and once in the subclass Mail::Exim.
My fix was to remove encoded from the Mail:Exim
This research was done in 2.5.4, however it looks like it is still in the master on github.
The text was updated successfully, but these errors were encountered: