|
Hi Filippo,
Your configuration should work (notifications too), but there are a
couple of considerations:
- MRMEMO is rapidly reaching "end of life", and the support situation
may be less than satisfactory for you and your customer.
- MRMEMO still doesn't support binary documents, and you can safely
assume that it never will.
- same as above regarding large messages (effectively >~ 100Kb)
If you want to install MRMEMO as a short-term solution while the
customer is migrating from MEMO, and if the MEMO users *only* handle
text messages (ie no MS-Word, Word-perfect or even RFT etc), then you
could be on the right track. Otherwise I suggest you look into X.400
connections (MRX <-> MEMO X.400 gwy).
hope this helps,
Stefan
|
|
Hi again,
> Will in this case the Delivery or Read notifications be supported?
It's difficult to give a definitive answer, since there are a lot of
factors to consider;
Notifications will be supported some way or other, but you may be in
for a few surprises. As far as I know MS-mail issues notification
messages that look quite ugly when they arrive at "the other side" (ie
MEMO). If I remember correctly MS-mail issues text-messages (not
structured notification messages) that basically says "message
selected", and the rest is up to the original sender to guess (like
what was the original message, and who received it).
Since I have never seen Mailbus Postmaster with MS-Mail, I could not
comment on Postmaster's ability to map MS-Mail notification messages to
Message Router Notification messages.
The mis-match between proprietary schemes of handling notification
messages in in my humble opinion one of the strongest reasons for
implementing X.400 P2 compliant messaging User Agents. That's why I
think you should stick with your original idea (Mailworks, which
provides P2 compliance for its clients)
cheers,
Stefan
|