MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » January 2014

RE: Domain Name on Email sent from iseries



fixed

Hi

Thanks Rob for testing that on your machine. It confirms what we suspected. Looks like we'll simply bite the bullet and set up users in the system directory. It works, it's simple and we understand the process.

I do wonder about the "tricks" that your system uses to build the 'from' address. How does it get information from their Notes account? But there's no point for us to wonder too much because we don't use Notes. (I assume you mean Lotus Notes.)

The "nice guy" part is a given.

Thank you

To: midrange-l@xxxxxxxxxxxx
Subject: RE: Domain Name on Email sent from iseries
From: rob@xxxxxxxxx
Date: Mon, 13 Jan 2014 13:52:24 -0500

We don't use SNDSMTPEMM. And a command exit program changes any usage of
SNDDST to a different email package (SNDEMAIL). We have tricks for
determining the 'from' address. We make no use of the system distribution
directory. It's all custom code trying to tie some information from their
user profile into their Notes account (if any). Failing that, our most
common default is postmaster at dekko dot com. But, because I'm a nice
guy, I'll try some tests...

CRTUSRPRF DUMMY
Sign on as that person
SNDSMTPEMM RCP((ROB@xxxxxxxxx)) SUBJECT('test from dummy') NOTE(TEST)
User DUMMY not enrolled in System Distribution Directory.
Send E-mail Failed.

ADDDIRE USRID(DUMMY GDISYS) USRD('delete me') USER(DUMMY)

SNDSMTPEMM RCP((ROB@xxxxxxxxx)) SUBJECT('test from dummy') NOTE(TEST)
Send E-mail Successful.
This one came from dummy@xxxxxxxxxxxxxxxxxxxxx

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: w 4038 <window4038@xxxxxxxx>
To: Midrange Use this to send questions <midrange-l@xxxxxxxxxxxx>
Date: 01/13/2014 01:32 PM
Subject: RE: Domain Name on Email sent from iseries
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Hi

Yes, we know that. We used the command:
CHGTCPDMN HOSTNAME('iseries') DMNNAME('company.com')

And our emails have a from address of: userprofile@xxxxxxxxxxxxxxxxxxx

So we don't understand Rob's suggestion. What are we not understanding?

Rob... do emails sent out by your iseries have a from address of:
userprofile@xxxxxxxxxxxxxxxxxxxxx
or userprofile@xxxxxxxxxxxxxx

Thank you

To: midrange-l@xxxxxxxxxxxx
Subject: Re: Domain Name on Email sent from iseries
From: rob@xxxxxxxxx
Date: Mon, 13 Jan 2014 08:37:20 -0500

cfgtcp
12
or CHGTCPDMN
Host name . . . . . . . . . . . 'GDISYS'
Domain name . . . . . . . . . . 'corp.dekko.com'

Now that you know that, what do you do about that?

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: w 4038 <window4038@xxxxxxxx>
To: Midrange Use this to send questions <midrange-l@xxxxxxxxxxxx>
Date: 01/13/2014 08:30 AM
Subject: Domain Name on Email sent from iseries
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Hi
When the iSeries sends email, using SDNSMTPEMM command, how does it
determine the domain part of the sender's email?
Our email is being sent out with a from address like this:
userprofile@xxxxxxxxxxxxxxxxxxx

It should look like this:
userprofile@xxxxxxxxxxx

Why is the "iseries" part being added to the domain?

If we add the user profile to the directory (WRKDIRE) and specify the
SMTP
address (F19=Change name for SMTP) for the user, the email from address
comes comes from there and appears as we want it to appear.

If we don't add the user profile to the directory, email can still be
sent, but the from address is, "userprofile.iseries.company.com"

Do we have to add each user to the directory? Then specify the SMTP
user
id and SMTP domain for each user?

We're trying to avoid having to add directory entries and SMTP user ids
for hundreds of users.

Here are the 4 commands we used to configure email on the the iSeries:
CHGTCPDMN HOSTNAME('iseries') DMNNAME('company.com')
CHGTCPHTE INTNETADR('10.555.55.55') HOSTNAME((company.com) (iseries))
CHGSMTPA RTYDAY(0 0) RTYHOUR(0 0) MAILROUTER('EXCHANGE.COM')
FIREWALL(*YES) DIALSCD(*NO)
ADDDIRE USRID(INTERNET SMTPRTE) USRD('SMTP email') SYSNAME(INTERNET)
PREFADR(*NETUSRID *IBM ATCONTXT)


Thank you

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact