Difference between revisions of "Talk:GroupWise"

From MicroFocusInternationalWiki
Jump to: navigation, search
m
(GroupWise improvements)
Line 7: Line 7:
  
 
Did you try to deselct the Message option on the content tab?
 
Did you try to deselct the Message option on the content tab?
 +
 +
== GroupWise improvements ==
 +
 +
I've had a number of ideas on significant improvements to GroupWise that I think could be made with a relative minimum of effort.
 +
 +
1) Auditor ID
 +
 +
GroupWise has some great internal security. Sometimes, tho, its just a little too good.
 +
 +
If one is in an environment subject to regulatory requirements (e.g. Sarbox, HIIPA, 1157, et. al. ad. nauseum), one may have a need, from time to time, to access a user mailbox for auditing or investigatory purposes. Generally, this is done without the user's knowledge.
 +
 +
But it can be difficult to gain access to a user's GroupWise mailbox on the live system, especially if the user has set a GroupWise password (which they have to do to use IMAP, POP or SMTP relay). Often, the "solution" is to lower the POA Security setting to "Low" and, if necessary, clear the user's password (which may tip them off to an investigation). Other methods involve laboriously copying to relevant files of the POA to another location and using GroupWise in "Direct Connect" mode; or defining a Proxy, which the user can see if they look.
 +
 +
GroupWise needs to be able to define certain accounts as "Auditors". An "Auditor" can then be granted access to a user mailbox, allowing the "Auditor" to Proxy into the specific user mailbox without having to establish a Proxy in the user's Security settings. This would allow investigatory examinations of user mailboxes without having to lower security for the entire POA, or copy files, or take other actions that may reveal the investigation.
 +
 +
2) iManager integration
 +
 +
We all know and love ConsoleOne, but iManager is Novell's stated direction. Its time for GroupWise to move along with the rest and become manageable under iManager.
 +
 +
Legitimate concerns regarding access to the WPDOMAIN.DB file exist, but they can be addressed. For example, much like GWADA.NLM was folded into the MTA and POA, the functionality needed to manipulate WPDOMAIN.DB can be folded into MTA, and the iManager plug-ins can be a front-end. The iManager server would communicate over TCP/IP with a listening port in GWMTA.NLM, and the GWMTA.NLM would execute the same changes now being made with ConsoleOne snap-ins.
 +
 +
3) sendmail integration
 +
 +
Everyone things Exchange is the "900-pound gorilla of E-Mail", but its not. sendmail has been around a lot longer and is much more widely deployed. Estimates range as high as 80% for the percentage all Internet E-Mail that is handled by a sendmail installation.
 +
 +
sendmail is also deceptively powerful. Out-of-the-box it supports not just SMTP and ESMTP, but UUCP, Decnet and faxing capabilities. It is not a mail "gateway", but a mail "router", with the ability to handle multiple protocols.
 +
 +
It also offers a standardized interface to add a new protocol - the MAILER definitions. An example is ProcMail, which plugs into sendmail as a MAILER and can accept E-Mail directly from sendmail.
 +
 +
The same could be done for GroupWise - in place of a GWIA (specifically, the GWIA component that translates to/from SMTP-MIME) a MAILER module could be written for sendmail. This would allow sendmail to deliver E-Mail directly into the GroupWise system.
 +
 +
On the flip side, it would also allow GroupWise to take direct advantage of all the software out there that plugs into sendmail's MILTER interface. SpamAssassin, Clam and MIMEDefang are just a few examples.
 +
 +
By doing this, every sendmail server on the 'Net could become a front-end for GroupWise, and mail system admins will have less-complex infrastructure to maintain.
 +
 +
4) UNIX socket alternative to GWIA "Third Party" directory
 +
 +
Now that NetWare is POSIX-compliant and OES has been introduced, its time to stop limiting the "third party directory" function of GWIA to a directory. Allow the option of using a UNIX socket interface, and open up all sorts of software from the *NIX world to GWIA.

Revision as of 18:38, 8 September 2005

Hi, In gwclient 6.5SP4 during printing Notes List GW insert blank line above and under every notes items. Its take many paper for long notes list. How can we remove blank line? Novell Support forum and editing gwca3007.frm dont help.


I'm having the same problem. This is a fairly major deal for me as well.


Did you try to deselct the Message option on the content tab?

GroupWise improvements

I've had a number of ideas on significant improvements to GroupWise that I think could be made with a relative minimum of effort.

1) Auditor ID

GroupWise has some great internal security. Sometimes, tho, its just a little too good.

If one is in an environment subject to regulatory requirements (e.g. Sarbox, HIIPA, 1157, et. al. ad. nauseum), one may have a need, from time to time, to access a user mailbox for auditing or investigatory purposes. Generally, this is done without the user's knowledge.

But it can be difficult to gain access to a user's GroupWise mailbox on the live system, especially if the user has set a GroupWise password (which they have to do to use IMAP, POP or SMTP relay). Often, the "solution" is to lower the POA Security setting to "Low" and, if necessary, clear the user's password (which may tip them off to an investigation). Other methods involve laboriously copying to relevant files of the POA to another location and using GroupWise in "Direct Connect" mode; or defining a Proxy, which the user can see if they look.

GroupWise needs to be able to define certain accounts as "Auditors". An "Auditor" can then be granted access to a user mailbox, allowing the "Auditor" to Proxy into the specific user mailbox without having to establish a Proxy in the user's Security settings. This would allow investigatory examinations of user mailboxes without having to lower security for the entire POA, or copy files, or take other actions that may reveal the investigation.

2) iManager integration

We all know and love ConsoleOne, but iManager is Novell's stated direction. Its time for GroupWise to move along with the rest and become manageable under iManager.

Legitimate concerns regarding access to the WPDOMAIN.DB file exist, but they can be addressed. For example, much like GWADA.NLM was folded into the MTA and POA, the functionality needed to manipulate WPDOMAIN.DB can be folded into MTA, and the iManager plug-ins can be a front-end. The iManager server would communicate over TCP/IP with a listening port in GWMTA.NLM, and the GWMTA.NLM would execute the same changes now being made with ConsoleOne snap-ins.

3) sendmail integration

Everyone things Exchange is the "900-pound gorilla of E-Mail", but its not. sendmail has been around a lot longer and is much more widely deployed. Estimates range as high as 80% for the percentage all Internet E-Mail that is handled by a sendmail installation.

sendmail is also deceptively powerful. Out-of-the-box it supports not just SMTP and ESMTP, but UUCP, Decnet and faxing capabilities. It is not a mail "gateway", but a mail "router", with the ability to handle multiple protocols.

It also offers a standardized interface to add a new protocol - the MAILER definitions. An example is ProcMail, which plugs into sendmail as a MAILER and can accept E-Mail directly from sendmail.

The same could be done for GroupWise - in place of a GWIA (specifically, the GWIA component that translates to/from SMTP-MIME) a MAILER module could be written for sendmail. This would allow sendmail to deliver E-Mail directly into the GroupWise system.

On the flip side, it would also allow GroupWise to take direct advantage of all the software out there that plugs into sendmail's MILTER interface. SpamAssassin, Clam and MIMEDefang are just a few examples.

By doing this, every sendmail server on the 'Net could become a front-end for GroupWise, and mail system admins will have less-complex infrastructure to maintain.

4) UNIX socket alternative to GWIA "Third Party" directory

Now that NetWare is POSIX-compliant and OES has been introduced, its time to stop limiting the "third party directory" function of GWIA to a directory. Allow the option of using a UNIX socket interface, and open up all sorts of software from the *NIX world to GWIA.