inFORM Decisions Information Portal

User Tools

Site Tools

Trace: • mainmenuoverview • workwithmergeengine • conditionalmap
pub:imail

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
pub:imail [2021/09/30 10:06] – [Work with Log] kkramerpub:imail [2025/03/21 20:47] (current) – [User Profile Considerations] kkramer
Line 184: Line 184:
 The first portion of this display shows only the System i information useful for licensing and compatibility purposes. The lower half, Maintenance Information, enables the configurable settings to be changed. By in large, these settings will retain the default shipped values. However, to be as configurable, these values are exposed and may be changed.  The first portion of this display shows only the System i information useful for licensing and compatibility purposes. The lower half, Maintenance Information, enables the configurable settings to be changed. By in large, these settings will retain the default shipped values. However, to be as configurable, these values are exposed and may be changed. 
  
-  * Target IFS Directory - The target IFS directory contains the path off the root directory that will retain iMail attachements. +  * Target IFS Directory - The target IFS directory contains the path off the root directory that will retain iMail attachments. 
   * Default Library - The default library contains the library that iMail will refer to as a current library. In this way, iMail may be relocatable to another library defined by this value.   * Default Library - The default library contains the library that iMail will refer to as a current library. In this way, iMail may be relocatable to another library defined by this value.
-  * Default Code Page - This is useful for globalization purposes. Should you be running this software on a non United States system, and another code page needs to be used to accomodate your language, the code page can be set here. +  * Default Code Page - This is useful for globalization purposes. Should you be running this software on a non United States system, and another code page needs to be used to accommodate your language, the code page can be set here. 
-  * DIF File Code Page - The DIF file code page is essentially the same setting as above, but for a specifice file conversion of datatabase to DIF (Data interchange Format).+  * DIF File Code Page - The DIF file code page is essentially the same setting as above, but for a specific file conversion of database to DIF (Data interchange Format).
   * JAR Files directory - If the path is blank, then the Java ARchive files are saved in the default directory: /QIBM/USERDATA/JAVA400/EXT. If specified here, they are save in the specified directory.    * JAR Files directory - If the path is blank, then the Java ARchive files are saved in the default directory: /QIBM/USERDATA/JAVA400/EXT. If specified here, they are save in the specified directory. 
  <html> <pre>  <html> <pre>
-Note:You can check the existence of ifdjava.jar in /QIBM/UserData/Java400/ext with the command: <br> WRKLNK ‘/QIBM/UserData/Java400/ext/ifdjava.jar’. <br> +Note: You can check the existence of ifdjava.jar in /QIBM/UserData/Java400/ext with the command: <br> WRKLNK ‘/QIBM/UserData/Java400/ext/ifdjava.jar’. <br> 
-If the JAR file is missing from your system, you can reatore it with the following command: +If the JAR file is missing from your system, you can restore it with the following command: 
  RST DEV('/qsys.lib/<i>currentiMaillibrary</i>.lib/jarfiles.file') OBJ(('/qibm/userdata/java400/ext/ifdjava.jar'))       RST DEV('/qsys.lib/<i>currentiMaillibrary</i>.lib/jarfiles.file') OBJ(('/qibm/userdata/java400/ext/ifdjava.jar'))     
 </pre></html> </pre></html>
  
 +If a path is not specified in the iMail configuration, you can use CLASSPATH to specify the ifdjava.jar at the system level and when any java job is started, ifdjava.jar is loaded accordingly.
 +**Note:** If not using the JAVA iMail option to send emails you can ignore CLASSPATH, but some RPG options still require JAVA.  i.e. if using iMail to send a Data Base file to XML a JAVA method is utilized.  If the ifdjava.jar file resides in QIBM you do not need CLASSPATH.  
 ==== Configure Secondary SMTP Settings ==== ==== Configure Secondary SMTP Settings ====
  
Line 254: Line 256:
 ==== Work with Log ==== ==== Work with Log ====
  
-Option 2 from the iMail menu allows an administrator to view the status of out going emails from the System i. No preliminary configuration for this option is necessary. Illustrated in the screen shot, a log of previously sent email displays in descending chronological order.+Option 2 from the iMail menu allows an administrator to view the status of out going emails from the System i. No preliminary configuration for this option is necessary. Illustrated in the screen shot, a log of previously sent email displays in descending chronological order.\\ 
 +**Note:** What is displayed on the log is controlled by the Data area DSMLOGAUT.   
 +  * When the data area is set to 'N' then the iMail log will display without restriction. 
 +  * When the data area is set to 'Y' then the iMail log will restrict access to users so they only see their own emails and the '4=Delete', '7=Resend' and '9=Forward Mail' aren't displayed as options.  Only User Profiles with *SECOFR and *SECADM will be able to see all mail logs and be able to use the "4=Delete" and '7=Resend' and '9=Forward Mail' options.
  
 <html><pre> <html><pre>
-  9/30/21                            iMail                            IMEMLOGC1  +  3/23/24                            iMail                            IMEMLOGC1  
  13:35:38                        iMail Send Log                       QSECOFR     13:35:38                        iMail Send Log                       QSECOFR   
                                                                                                                                                                    
-  4=Delete   5=Display   7=Resend   8=Mail log +  4=Delete  5=Display   7=Resend   8=Mail log   9=Forward Mail 
  
                                                                                                                                                                  
Line 281: Line 286:
                                                                                                                                                                                                        
 </pre></html> </pre></html>
 +
 +  * Option 4 Deletes the eMail (CONFIRM by answering Y/N)
 +  * Option 5 Displays the eMail message details
 +  * Option 7 Resend the eMail
 +  * Option 8 Mail job log is only available for error transactions 
 +  * Option 9 Forwards the eMail by displaying the EFWDLOG screen shown below. (Enhancement to iDocs 8.00; 03/27/24)
 +<html><pre>
 +                       Forward iMail Transaction (EFWDLOG)                      
 +                                                                                
 + Type choices, press Enter.                                                     
 +                                                                                
 + iMail Log ID (ELMAILID)  . . . . > 202404011025400830000000                    
 + To Address . . . . . . . . . . .   ken@informdecisions.com                                            
 +                                                                                
 +                                                                                
 + Subject  . . . . . . . . . . . .   *SAME                                       
 +                                                                                
 +                                                                                
 +                                                                                
 +                                                                                
 +                                                                                
 +                                                                                
 +                                                                                
 +                                                                                
 +                                                                                
 +                                                                                
 +                                                                                
 +                                                                         Bottom 
 + F3=Exit   F4=Prompt   F5=Refresh   F12=Cancel   F13=How to use this display    
 + F24=More keys                                                                  
 +                                                                                
 +</pre></html>
 +**Paramaters:**
 +  * MSGID (26A): user inputs 26 characters which retrieves record from file FRMEMLLOG by field ELMAILID; 
 +  * TOADDR (128A): user inputs new destination addresses, seperated by blank or colon; 
 +  * SUBJECT (128A): *SAME if user wants to use same subject in field ELEMSUBJ of FRMEMLLOG or enter new subject 
 +
 The **F8** function runs the [[pub:miscadmincmd|PRGMAILLOG]] command to purge the email log file. The **F8** function runs the [[pub:miscadmincmd|PRGMAILLOG]] command to purge the email log file.
  
Line 340: Line 382:
 </pre></html> </pre></html>
  
-The screen below illustrates the forth view of email messages.+The screen below illustrates the fourth view of email messages.
  
 <html><pre> <html><pre>
Line 365: Line 407:
   PAGE:        1 /      790                                                        PAGE:        1 /      790                                                     
   F3=Exit   F5=Reload   F7=Find   F8=Purge   F11=Next view   F12=Previous          F3=Exit   F5=Reload   F7=Find   F8=Purge   F11=Next view   F12=Previous       
-                                                                                                                     +                                                                                                                 
 </pre></html> </pre></html>
  
Line 403: Line 445:
 In most PC based email systems this type of distribution list would be limited to a table confined to potential recipients. This is not true of iMail. Although recipient email addresses can be created here, sender email addresses are created and maintained in this program as well.  Moreover, once a sender’s email address is created that address can be associated with an AS/400 User profile. In this way, when sending an email a user’s originating email address can automatically be generated. In most PC based email systems this type of distribution list would be limited to a table confined to potential recipients. This is not true of iMail. Although recipient email addresses can be created here, sender email addresses are created and maintained in this program as well.  Moreover, once a sender’s email address is created that address can be associated with an AS/400 User profile. In this way, when sending an email a user’s originating email address can automatically be generated.
  
 +====== User Profile Considerations ======
 +With IBM i, user profiles can be created with names up to 10 characters. However, when adding a user to the SNA (Systems Network Architecture) directory entry system using the ADDDIRE command, the User ID (USRID) field is restricted to 8 characters maximum. This limitation stems from legacy SNA and OfficeVision compatibility requirements.
 +
 +When a user profile name exceeds 8 characters (e.g., MWTRAIN10), only the first 8 characters (MWTRAIN1) are used in the directory USRID. This leads to conflicts when:
 +
 +  * Multiple user profiles share the same first 8 characters.
 +  * Directory entries become ambiguous or overwrite each other.
 +  * Messaging and routing via SNADS or other directory-dependent functions fail or misroute messages.
 +
 +**Conflict example:**
 +
 +^ User Profile: ^ Intended Directory ID: ^ USRID truncation:                                                            ^
 +|MWTRAIN1  |MWTRAIN1 |MWTRAIN1 | 
 +|MWTRAIN10 |MWTRAIN10 |MWTRAIN1 (conflict) | 
 +
 +In the example above, both users map to MWTRAIN1 in the SNA directory, causing a conflict.
 +
 +**Resolution: Use Alias IDs (≤8 Characters) for Directory Entries**
 +
 +To avoid conflicts while preserving your actual user profile names, you can assign a unique 8-character alias for the directory entry's USRID and link it to the full user profile using the USER() parameter. This allows the directory to uniquely identify each user while complying with the 8-character limit. 
 +
 +**Example Alias Directory Entries:**
 +
 +MWTRAIN10 → Alias: MWTRN010
 +
 +ADDDIRE USRID(MWTRN010 LCLSYSTM) USRD('Alias for MWTRAIN10') USER(MWTRAIN10)
 +
 +
 +==== Work with distribution list ====
 Work with public distribution list, shows the initial public table of email addresses. The maintenance program uses the standard editing options and functions keys to maintain the list. Using an option 1 next to the email address enables that entry to be edited, whereas pressing the F6 key adds a new record to the email table. Work with public distribution list, shows the initial public table of email addresses. The maintenance program uses the standard editing options and functions keys to maintain the list. Using an option 1 next to the email address enables that entry to be edited, whereas pressing the F6 key adds a new record to the email table.
  
pub/imail.1633021574.txt.gz · Last modified: 2022/06/25 17:02 (external edit)