You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by cheshirrrrre on 23 Aug 2013 09:27 UTC as Trac ticket #1489291
Hello!
After upgrade from 0.9.2 to 0.9.3 strange thing occured:
on 0.4.2 and 0.9.1/0.9.2 (versions i've tested) corresponding profile was used automatically when one was trying to reply on emails in defferent distribution groups.
F.e.: i've got an reply email to admin@some_domain in my some_domain.admin distributed imap folder. As i hit reply, i've got a new_mail window with admin@some_domain in the "From:" field (i have matching profile in rcube so i can send emails from that address). The default profile is another one, which is used mainly for local in-office emails, so corresponding profile was choosed based on "To:" or "Received:..... for...." header or whatever else.
Such thing worked till 0.9.3. Now one have to change "From:" when replying on emails every time. And i can't say that it's a very handy thing.
Reported by cheshirrrrre on 23 Aug 2013 09:27 UTC as Trac ticket #1489291
Hello!
After upgrade from 0.9.2 to 0.9.3 strange thing occured:
on 0.4.2 and 0.9.1/0.9.2 (versions i've tested) corresponding profile was used automatically when one was trying to reply on emails in defferent distribution groups.
F.e.: i've got an reply email to admin@some_domain in my some_domain.admin distributed imap folder. As i hit reply, i've got a new_mail window with admin@some_domain in the "From:" field (i have matching profile in rcube so i can send emails from that address). The default profile is another one, which is used mainly for local in-office emails, so corresponding profile was choosed based on "To:" or "Received:..... for...." header or whatever else.
Such thing worked till 0.9.3. Now one have to change "From:" when replying on emails every time. And i can't say that it's a very handy thing.
Migrated-From: http://trac.roundcube.net/ticket/1489291
The text was updated successfully, but these errors were encountered: