Project

General

Profile

Bug #60784

Outlook has problems because of a not correct formatted email address in TO field

Added by Robert Schardl over 3 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
AllDevsGroup
Category:
Outlook
Target version:
Start date:
11/11/2016
Due date:
% Done:

0%

Estimated time:
Operation System:
Rhel 5

Description

When you have a look at the redmine notification emails, than you can see within the _TO field a not correct formatted email address -> "undisclosed-recipients:;".
After discussing with Danny we think it's because of receiver is originally within _BCC field and maybe _TO field is filled out with "undisclosed-recipients:;".

It is important to check correct formatted email adresses on the server first to avoid Outlook problems.

We have to discuss this issue.


Related issues

Related to Scalix - Bug #60645: Outlook Export To .pst fails to re-import same itemsResolved08/17/2016

Actions

History

#1

Updated by Danny T over 3 years ago

I think this happens when all the recipients are BCC (redmine does not probably to send one email to lots of watchers and use BCC to ensure that nobody sees who is in the list).

This display is not new so I don't know why OL starts to fail now, and if this must be changed on server side then we need to figure out how this can be done (what to display in order to not compromise the meaning of BCC).

It is not clear in the RM but I am guessing that this RM is causing problem in sxmigrate?

#2

Updated by Andrea Lanfranchi over 3 years ago

  • Related to Bug #60645: Outlook Export To .pst fails to re-import same items added
#3

Updated by Andrea Lanfranchi over 3 years ago

It is also related to #60645

#4

Updated by Robert Schardl over 3 years ago

Same issue.

#5

Updated by Alexey Bobyr about 2 years ago

undisclosed-recipients

depends on locale

at BRHC server

2017-12-15 00:05:10.613 [WARN ] [ajp-nio2-8009-exec-15] [Message.parseRecipientHeader:453] Message (url: null , dref:004d38dd71bf8bf1) - Failed to parse provided address <destinatarios-nao-revelados:;>Local address contains illegal character

'destinatarios-nao-revelados' it's 'undisclosed-recipients'.
So '<some-text:;>' must be treated as 'undisclosed-recipients'

#6

Updated by Alexey Bobyr about 2 years ago

for history.

here is rfc https://tools.ietf.org/html/rfc2822#appendix-A.1.3 .

field with an empty group recipient named Undisclosed recipients.

Alexey Bobyr wrote:

undisclosed-recipients

depends on locale

at BRHC server

2017-12-15 00:05:10.613 [WARN ] [ajp-nio2-8009-exec-15] [Message.parseRecipientHeader:453] Message (url: null , dref:004d38dd71bf8bf1) - Failed to parse provided address <destinatarios-nao-revelados:;>Local address contains illegal character

'destinatarios-nao-revelados' it's 'undisclosed-recipients'.
So '<some-text:;>' must be treated as 'undisclosed-recipients'

#7

Updated by Alexey Bobyr over 1 year ago

  • Status changed from New to Resolved

it seems it works normally in Setup12.7.1.9178.
closing it.

Also available in: Atom PDF