SCO Unix»How to install mvmail for Unix»email installation for Unix
  • RSS Feed

Last modified on 1/7/2015 9:04 AM by User.

Tags:

email installation for Unix

Install the email executable file.

install /u/mvs/sco/bin/email  by just transmitting the email file from MVS to the customer's machine.  Also send the email.conf file which is also on this folder.  They both should go in /u/mvs/sco/bin.

They will need a S/M module update done after 01/06/05 to support tokens that come from .ini parameters.

Here's a website for email that has the man pages.

The project home page is at:  email.cleancode.org

 

Edit email.conf

Edit the $MVS_ROOT/$MVS_PLATFORM/bin/email.conf file and assign the correct value to the entry for the SMTP_SERVER parameter.  This is an example of the entry.

SMTP_SERVER = 'mail.mvsoftware.com'

MY_NAME  = 'company name'

Comment out the following parameters in the file:

MY_EMAIL
REPLY_TO
SIGNATURE_FILE
SIGNATURE_DIVIDER
ADDRESS_BOOK
SAVE_SENT_MAIL
TEMP_DIR
GPG_BIN
GPG_PASS
SMTP_AUTH
SMTP_AUTH_USER
SMTP_AUTH_PASS
 

Set SMTP mail server to allow relaying.

Ask the customer for a valid username and password for SMTP authentication. Then uncomment and modify the following fields in the sco\bin\email.conf file.

SMTP_AUTH = 'LOGIN'

SMTP_AUTH_USER = 'username'

SMTP_AUTH_PASS = 'password'

Not all email servers have the same requirements for authentication.  See this link for instructions on how to set up Profits Plus  for different scenarios.

 

You might have to set the sticky bit.

We have seen SMTP servers that accept a connection from root but not allow a connection from any other login.  Test sending an email when logged in as someone other than root.   If non-root logins are timing out trying to connect to the SMTP server you can set the sticky bit on the email executable that will make program masquarade as root while it is connecting to the SMTP server.  Here's how to set the sticky bit.

cd /u/mvs/sco/bin
chmod a+s email

This will make the permissions on the email file look like this:  rwsrwxrwx.  The blue s means the sticky bit is set.

 

Edit parms in SITE.INI?

You probably will never have to do this, but you can add tokens to the printer spool command to specify a different SMTP server than is already defined in the email configuration file in $MVS_ROOT/$MVS_PLATFORM/bin/email.conf.  

The values for the tokens are kept in the site.ini file for every company.  If you never use these tokens, then you don't have to do this step.  

Edit the /u/mvs/dsk0/100???/site.ini file in every company and add/change the following parameters.

INI'SMTP'SERVER=          ; Don't use this anymore.  use email.conf  instead

INI'SMTP'PORT=            ; Don't use this anymore. use email.conf instead

INI'SMTP'RULES=           ; see this link for how to use this parameter.

This is an  example of a printer spool command that uses the above token to override the default SMTP server.  Notice the -r option at the end of the example below.. 

If they use a non-standard smtp port (something other than 25) then you'll also have to add -p %(INI'SMTP'PORT)% as well.

 

mvmail -s"%(SUBJECT)% -t%(EMAIL.TO)%  -f%(EMAIL.FROM)% -p %(PRINTFILE.HTM)%

 -c"%(COMPANY.NAME)%  -r %(INI'SMTP'SERVER)%

 

Verify Network setup

Verify their default gateway is setup according to our email networking startup scripts.