Evolution: MAIL FROM response error: command unrecognized
LinuxQuestions.org Member Success StoriesJust spent four hours configuring your favorite program? Just figured out a Linux problem that has been stumping you for months?
Post your Linux Success Stories here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Evolution: MAIL FROM response error: command unrecognized
This is more of a tip and trick but still a success in order to help others.
But when using Evolution, if you ever come across this error when attempting to send/reply mail:
MAIL FROM response error: command unrecognized
This is due to a problem or bug in glibc which seems to just give us random string chunks from the /etc/hosts file.
To fix the problem, just remove all the lines and even empty lines in your /etc/hosts file.
Cheers.
PS. I only found one other site/mailing list that explained this problem when using Evolution mail, so hopefully this will help anyone in the future looking for solutions when they encounter this problem. And I just can't help myself, when in a GUI I just prefer Evolution over most other mail clients but pine is still the best for console based email..
Originally posted by Rastralcaz I have to admit, I didn't think this would work, but I tried it anyway. Much to my surprise, it worked! Bizarre.
Interestingly, I'm using Slackware, and am connecting to Austin, TX's Road-Runner servers too. I wonder if there's something peculiar about that mix?
Thanks for the tip! Saved me a heck of a lot of trouble.
Yes, very strange error indeed and glad its helped others out as it took me forever to find the solution myself when setting up Evolution in Slackware on one of my machines.
holy cow, i just had that error, and thank god for LQ or i never would have figured out how to fix it. what a weird error, is there a bug report filed with the evolution people? (road runner here, too, btw.) thanks trickykid.
update: just wanted to document what i did: moved /etc/hosts to /etc/hosts.sus, launched evolution and sent out a test email, closed evolution, moved /etc/hosts.sus back to /etc/hosts, and evolution has continued working properly since then. cheers.
Last edited by synaptical; 02-07-2004 at 02:46 PM.
I just commented out the 127.0 line and it worked. One question though, don't you need that line? Won't you get a error on restart that your localhost couldn't be found, blah blah
Originally posted by FXRS I just commented out the 127.0 line and it worked. One question though, don't you need that line? Won't you get a error on restart that your localhost couldn't be found, blah blah
FX
Its for loopback only. Why not just remove the crud that isn't even used and taking up space. If you know what the hosts file does.. really no reason to keep the explanation and description of the file in there that is taking up space..
hmmm....That does allow Evolution to work, but now it generates an error after a reboot. Does anyone know exactly why this allows us to send mail? I would hope somebody sent a bug report to Ximian but I don't see anything on there website.
Originally posted by mi6 hmmm....That does allow Evolution to work, but now it generates an error after a reboot. Does anyone know exactly why this allows us to send mail? I would hope somebody sent a bug report to Ximian but I don't see anything on there website.
Its got to do with something in which glibc I think is in correspondence with Evolution is trying to read the whole hosts file, ignoring the commented # marks in it.
What kind of errors are you getting at boot specifically? The only reason you should get errors at boot by only removing # commented lines in the files is if you accidently removed something you should not have.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.