Reply All Bug
Problem reported by Erick Baum - October 7, 2015 at 2:14 PM
Resolved
We discovered what appears to be a new bug in build 14.3.5752.  Whenever we Reply All in the webmail, it replies to ourself as well anyone else the message was sent to.  This even happens if I am the only recipient and I reply all, it will send it to the original sender and myself.  In the past, my e-mail was always excluded from the reply... as I think it should be.

9 Replies

Reply to Thread
0
Andrea Rogers Replied
Employee Post
Hey Erick! I'm on this same version, and I'm not able to replicate this. When you hit Reply All, do you see your email address added in the To, CC or BCC fields?

Andrea Rogers
Customer Operations Manager
SmarterTools Inc.
877-357-6278

www.smartertools.com

0
Erick Baum Replied
It gets added to the To field after the original sender.
0
Erick Baum Replied
I confirmed this ONLY happens when you have multiple From addresses configured on your account.
1
kevind Replied
We're seeing this also.  Probably introduced by this change in 5752:
  • Fixed: A user replying to a message that was sent to the user's domain alias address no longer includes that address as a recipient.
2
Andrea Rogers Replied
Employee Post
Thanks for the update Erick. I'll get this over to the SmarterMail team. 

Andrea Rogers
Customer Operations Manager
SmarterTools Inc.
877-357-6278

www.smartertools.com

0
kevind Replied
Andrea, can we switch the status to Known? Thanks.
1
Andrea Rogers Replied
Employee Post

Hi Kevin,

This has been resolved and will be included in the next minor release (tentatively scheduled for next month). This fix is also included in our latest custom build. If you'd like that, just get it touch with our sales team at sales@smartertools.com and they'll get it over to you.

Andrea Rogers
Customer Operations Manager
SmarterTools Inc.
877-357-6278

www.smartertools.com

0
Dan Dickson Replied
This is still happening if the user that is reply all was in the CC on the original email
0
User Replied
Hi Dan,

The release we put out yesterday should fix that. Let me know if you see any more issues with it.

Reply to Thread