GroupWise's SMTP server currently acts as a standard SMTP server. Messages sent via this message, even when authenticated to a GroupWise user, are not retained by GroupWise.
It would be a great advantage when using GroupWise for information tracking if authenticated messages sent via SMTP were to be stored in the authenticated user's Sent folder and treated as standard GroupWise messages in the data store.
by: Johnnie O. | over a year ago | Agents
Comments
Apart from this being technically very difficult to implement as it would require a major design change in GWIA, it is actually industry standard that mail clients sending mail directly via SMTP are resonsible themself for putting copies of those mails into some mailbox or folder, usually via IMAP. So I suggest looking at it from that angle, as while such a function might be useful, I consider it very unlikely to ever be implemented.
There are many small solutions that want to send mails not only full ERP or CMS - like Health insurances, Social insurances, IRS, scanners, HR, etc. for that you like to have a central location for the success information of the sent mails. MAPI is a very old solution today.
Wouldn't it be possible to have a new "relay-gateway" for this task. SOAP or the GWIA API could possibly been used for generating internal sent messages for known accounts, so you don't have to change the GWIA design.
Responding to Massimo R: I accept the difficulty of changing the GWIA, so that's a knock against this. I am much less invested in the "industry standard" argument though for several reasons:
1. The industry standards for e-mail are generally an insecure mess (I am not going to quote chapter and verse on that, as it would be a long comment). It is important that GroupWise support them, but I would argue that the importance of that lies in making those standards a common baseline with the "value add" for GroupWise largely being proprietary functionality that exceeds those standards. This request falls in line with that view.
2. If we only want to support standards, then the Google Apps suite becomes more compelling because their literal target is to meet and not exceed the standards for most functionality. And in some industries like education they are a "no cost" solution with low admin and excellent uptime. In order to compete against such products GroupWise does need to have a "value add' (#1 and #2 are also reasons for a true Mac client instead of CalDAV, CardDav, IMAP)
3. The standard that mail clients save copies using a non-SMTP format is a user-facing client behavior. This functionality is an enhancement for automated or server "clients". Since GroupWise only has a real client on Windows, and Windows market share is declining, I see the need for non-user-client advantages as increasing in the future.
I add my vote for this. After recently upgrading my Windows desktop accounting software, the new version no longer uses the old create email api. Instead, it has direct integration with Outlook, Gmail or fallback to smtp.
I now have no GroupWise sent item for tracking the status of invoices sent to customers.
Similarly to RodneyW we have also migrated to a different 'cloudy' finance system and use SMTP for sending remittance advice notes, which we now haven't an independent record of...