in the project we'are working on, an unexpected requirement has come to light: it seems that some outbound email can be tergeted toward an email account fetched by a different OTRS instance (not managed by us). So, in a general situation, the 2nd instance shall be able to create a ticket of its own, reply and so on. This, obviously, can potentially be a problem: the logic of mail-ticket association based on ticket# in the subject can be troublesome if the two numerations overlap. An instance put its #, and the other can alternatively, add its # if the numerations don't overlap, or associate the email to an existing ticket with the same number (and all becomes a mess!).
According to some tests the problem doesn't seem to exist in our scenario, but I would like to know if someone has experience about it. Maybe there are limits and/or suggestions that is better to take in mind.
The following are two example of ticket number from the two different OTRSs:
- Ticket#2014031810001111 <--- our instance
Ticket#2014031888007694 <--- the 'other'
- 8 digits: date yyyymmdd
- 3 digits: a code specific of the system (based on what?)
- 5 digits: a incremental counter (with jumps)
Is this interpretation correct?
Can we feel safe if the two instances starts sending email to each other?
As always, thanks
Luca