|
Jim,
I will have to send you some attachments off-line. They will get stripped
off if I try to send them to the list.
Albert
-----Original Message-----
From: Rubino, Jim [SMTP:Jim.Rubino@Fike.com]
Sent: Friday, December 20, 2002 8:32 AM
To: 'midrange-l@midrange.com'
Subject: RE: Using email on iseries
Albert,
Would it be possible to maybe get a sample of the code to do this?
I have
never done that and I would like to see how it works and see if we
might be
able to use it here.
TIA
Jim
-----Original Message-----
From: York, Albert [mailto:albert.york@nissan-usa.com]
Sent: Friday, December 20, 2002 10:24 AM
To: 'midrange-l@midrange.com'
Subject: RE: Using email on iseries
Tom,
If you just need text messages then you could write your own sockets
programs to send and receive mail. It's not hard to do and it gives
you the
most control. That is what I ended up doing.
Albert York
-----Original Message-----
From: Law, Tom [SMTP:ACTLaw@nmhg.com]
Sent: Thursday, December 19, 2002 9:02 PM
To: Midrange-L (E-mail)
Subject: Using email on iseries
This message is in MIME format. Since your mail reader does
not
understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
We are looking to send email from our iseries boxes to
anyone.
These are
simple text messages and no attachments. I have the process
working
but it
seems that there is a lot of "lack of control" using the
SNDDST
command.
Right now the only users are on our exchange server which
is
working, but
the future needs are to send outside the company.
We are currently writing Global s and procedures to manage
and
control
iseries email. We find the control or "lack there of"on
iseries
email
frustrating.
What Vendor software do you use instead of the IBM SNDDST?
We
aren't
looking for an expensive alternative.
BTW The iseries will only SEND mail and not receive any
back. We
use an
exchange server list ID as the originating address and this
works
well.
Thanks for any information you can provide.
Thomas Law
_______________________________________________
This is the Midrange Systems Technical Discussion
(MIDRANGE-L)
mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
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@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
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@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.