We want to hear from you! What features or improvements would you like to see in PoliteMail? Send us your ideas and we’ll consider them for future releases.
Our company ran into an email with PM5.0 where we had an older cached distro that was being expanded (to remove a couple leadership members), causing a user with a disabled mailbox to be placed directly in the TO: field. Since emails are being processed with GraphAPI, the email would not send since one recipient's mailbox is disabled.
My suggestion is: In this scenario, can you add in a response message saying "X User Mailbox is not active. Please remove this recipient and try again." Manually sorting through hundreds of users to verify all recipients have an active mailbox is cumbersome and inefficient, and this simple feature would save loads of time and frustration
Alexander Silva
Hi Alexander,
We've updated the latest release and this was included. When expanding a distribution group with a disabled mailbox, you will now be able to send the message without issue.
Attachments Open full size
Hi Alexander,
I was able to work with internal resources and resolve the disconnect. Paul will be able to keep you updated as we work on this, and I will update here as well.
Attachments Open full size
Hi Alexander,
I've spoken with Paul about this and it seems we've had a disconnect. What you have described is not expected behavior, so we want to make sure that we can get this resolved for you. If you could submit a Request Support, we will get this straightened out.
Attachments Open full size
Hi Marlena,
I had support from Paul Stewart and he agreed to make this suggestion, since emails are being sent through GraphAPI, having a disabled mailbox in the TO: field will cause emails not to be processed. This behavior seems like a bug in PM to cause the entire email not to send, rather than skipping that one recipient.
Paul confirmed by checking recipient count with a disabled mailbox user in the TO: field.
Attachments Open full size
Hi, Alexander. Having a disabled mailbox in the TO: field should not prevent sending. If this is still happening for you, would you please submit a 'Request Support' so we can look into this for you?
Attachments Open full size