Hi to all
when I receive new mail, and I have read it,after using the action forward the mail become unreaded again.
I am using
Server Release 5.0.10 over windows 2000 server,
and the client and mail file version are Release 6.0
Thanks in advance.
Hi to all
when I receive new mail, and I have read it,after using the action forward the mail become unreaded again.
I am using
Server Release 5.0.10 over windows 2000 server,
and the client and mail file version are Release 6.0
Thanks in advance.
Subject: readed mails are become marked as unread after forward
Hi
On Design tab of the database property dialog there is a setting which says
“Do Not Mark Modified Documents as Unread”
Check this and forwarded mail will not be marked unread.
HTH
Richard
Subject: RE: readed mails are become marked as unread after forward
Can this be set as the default somehow. All my users have this issue…a real pain and nobody likes this as a “default” setting.
Subject: It can be set as the default through the template.
Subject: RE: It can be set as the default through the template.
My template has this option selected already. But the mail files didn’t inherit the setting. I saw your later posting regarding the issue with the setting not replicating to the local mail replica. That’s not good…I hope this is going to be fixed in 6.51 or possibly in a possible 6.5 CF1 if they deem it important enough. I’d be happy if they could just reissue the mail template or an agent to fix it.
Subject: that property fixes the problem but there are problems for replicated mail users
that property fixes the problem but there are problems for replicated mail users. The property “Do Not Mark Modified Documents as Unread” doesn’t seem to replicate down to the client when enabled on the server.
Anyone have a trick up their sleeve to make this work?
Subject: RE: that property fixes the problem but there are problems for replicated mail users
One option would be to check the setting in the template and do a Design Replace (as opposed to a Design Refresh) which tends to force these settings to be updated, though I’m not sure if this would fix the replication problem.
Subject: it doesn’t help unless you do a nconvert on the client