We are running Traveler R8.5.2 along with iPhones.
Traveler is on it’s own servers, in it’s own Domino Domain. This one server is hosted in a DMZ.
This domain been cross-certified with our ‘live’ domain, and Directory Assistance setup to enable lookup into our users.
Whilst email functions correctly, we are having some issues when calendar events occur in conjunction with a Traveler device (eg iPhone).
When replying to a calendar event the routing domain name of the Traveler Server is appended to the users email address.
For the purpose of examples, lets call the Traveler domain ‘TravelerDomain’ and our actual domain ‘RealDomain’.
For example, you could have a meeting that was created in a Notes Client, the attendee can then accept the meeting on his iPhone. If the Chairperson then clicks ‘Reply’ on the acceptance notice then the reply address would be:
Username/Organisation@TravelerDomain rather than Username/Organisation@MailDomain
Or, trying to make use of the new functionality in Traveler R8.5.2 which allows the iPhone to create meetings the attendees, a similar issue is generated.
The iPhone user can create a meeting on the iPhone and select their attendees. The attendees will accept/decline etc the meeting request but the acceptance notice will then generate a delivery failure as again the routing domain will be the Traveler Server rather than our actual mail server.
We’ve had this problem since we deployed Traveler - which was originally Traveler R8.5.1. A PMR is open with IBM regarding this since June, but I thought maybe someone here may have some ideas.
Subject: RE: Similar Issue - Meeting Acceptance Not Sent to Chairperson
No, that is not normal. The first thing to do is make sure you have mail routing setup on your Traveler server. After that, it could be the same issue as the original post in this thread or it could be something else. If mail routing works on the Traveler server, then you probably need to open a PMR for further analysis.
We have one traveler server (8.5.2) which hosts several customers. Server is placed in DMZ with a replica of Names.nsf from each customer on it.We are having the same issuses as earlier described on this issue.
Did you make sure mail routing (the most common issue with this) is setup correctly? If mail routing from the Traveler server works correctly, then you might be hitting the PMR that some others have hit. We are still working on the PMR, so there is not really an update on that. But make sure you have gone through the mail routing post and documentation first as you are much more likely to hit mail routing problems.