GNOME Bugzilla – Bug 609341
responds with standart-adress
Last modified: 2010-03-01 03:47:11 UTC
when i click respond it doesnt respond with the adress i gottet the mail. its responding with my standart-adress. in 2.26 it was still working..
Could you please example of both the contacts, one which works and other one which doesn't work and what do you mean by respond ?
oh sorry my english is so bad.. now i changed my system to english and now i saw that its reply.. so, i have 2 accounts in evolution (one imap with smtp and one just smtp) and i get all my mails forwarded to the imap-account. when i click reply it has automaticaly the standart-adress as my responding-adress doesn't matter if the mail was sended to account a or account b. maybe its because all the mails are forwarded to account a?! a third account (imap and smtp) no has this problems.. when i am responding one of these mails it knows to reply with the adress c. i know it was working in the version which was part of ubuntu 9.04.
I have the same problem with Evolution 2.28.1 I am using IMAP on my server. This server loads all my emails via POP3 to the IMAP storage. My default account (default@mail.com) in Evolution had configured this IMAP server in the "Receiving Email" tab. My server isn't an SMTP server so I have configure another SMTP server in the "Sending Email" tab. Then I have another account (another@mail.com) in Evolution with a Server Type "None" in the "Receiving Email" tab and the same SMTP server as my default account but with the other email. (I am using a few aliases for my email account) If I receiving an email to another@mail.com and reply to this mail the FROM in the Evolution composing window is always default@mail.com instead of another@mail.com But I would like to reply with the same address the email was sent to. Hope the problem is clear now and I think this behaviour is easy reproducible on every system!
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of bug 588833 ***