|
I don't see any reason why you would need to maintain the directory and SMTP information then, but someone wiser than me might know otherwise. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Cunningham Sent: Monday, March 26, 2007 3:37 PM To: Midrange Systems Technical Discussion Subject: RE: Directory Entries and SMTP names We have a database that we maintain of all users which is also part of our dynamic menu system. In that database we have their e-mail address. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Grizzly Malchow Sent: Monday, March 26, 2007 4:28 PM To: Midrange Systems Technical Discussion Subject: RE: Directory Entries and SMTP names Do you have another way to link the user profile to an email address? I always add a directory entry and SMTP information because I can then use the file QUSRSYS/QATMSMTPA to get the user's email address based on their user profile. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Cunningham Sent: Monday, March 26, 2007 3:21 PM To: midrange-l@xxxxxxxxxxxx Subject: Directory Entries and SMTP names We currently create a directory entry (WRKDIRE) and an SMTP name entry (WRKNAMSMTP) for all of our users. We started doing this because the SNDDST command was the only way to send an e-mail and these two tables needed an entry to route that Distribution to the correct external e-mail account. We have now converted all our e-mail sending applications to use the java mail API and no longer use SNDDST. Is anyone aware of any reason why we could not stop creating the Directory entry and SMTP name entry? Thanks
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.