🚀 go-pugleaf

> I have received version 2.08 of the Mailer but haven't installed it yet.
> Since I heard on this list that version 2.09 might be available soon, I
> was wondering what the differences would be? We will be migrating over
> to ESA 1.1 soon, currently we are VM/HPO5.
>
> -Rich

Rich, This is a list of the current fixes/new function:

R208001    Documentation corrections

R208002    Correct DISTSUB ASSEMBLE to properly handle long MAIL FROM:
*          lines

R208003    Fix FORWARD MAILER to always use the diskmode passed by
*          Mailer

R208004    Handle RECFM=V mailer profile correctly

R208005    Update R207044 improperly coded in MAILER AUXEXCR2 file.
*          No update ever existed.

R208006    Always produce a valid To: in BSMTP error mail

R208007    Never return more than 2M to CMS.
*          Never allocate a trace table larger than ????

R208008    Correction to R207007.  RSCS options should have been enclose
*          in parenthesis.

R208009    Make waiting for work message controllable from profile
*              Waiting-For-Work-Msg = True | False

R208010    Fix for looping processing messages (and producing lots of
*          'Mailer waiting for work messages'

R208011    Correction to *DEFAULT* search in ORIGINS table

R208012    Fix problem with Local-Hostn addresses unable to return
*          mail sent message.

R208013    Fix problem with forwarding scavenger

           If mail was sent from a user using using the MAIL/MAILBOOK
           command's DIRECT option and there are multiple recipients
           the process of transferring the mail to the Mailer generates
           multiple copies at the forwarding addresses (all the original
           copies had the same set of userids in the To: header).  To
           correct this problem, the mail will be wrapped with a BSMTP
           header specifying the correct final destination.  This will
           require the scavenger to be listed as a trusted mailer in
           the INCOMING table.

           This change requires the CMS PIPE command.  If PIPE is not
           available forwarding will be done as it was in the past.

R208014    Support for quiet mail FORWARDing
*          The forwarding support will now create a new BSMTP file and
*          set the FORM field to QUMAILER so that messages will not be
*          sent to the sender.
*
*          To allow user control of this facility the keyword (NO)QUIET
*          will be added to the FWD cmd.  This will allow changing of
*          value without requiring any address changes.
*

R208015    Support for file forwarding without mail forwarding
*          This change allows a file forward to be specified without
*          having to have a mail forwarding also specified.


R208015 is not operational at the moment.

   John