Jim,
I  kinda lost the original post, so I hope this is what you meant...
Seems like you have the user create an html file using one of the many HTML
editiors out there then save that file to a specific area on the IFS.
Then the green screen tool can be used to read in the stream file change
any Template text that needs to be changed then the stream file could be
dumped in to the body of a message using the JavaMail  and sent out as
text/HTML

If you are not familiar with sending mail Via Java and RPG let me know we
have a couple of programs that send e-mail.  You will probably need someone
else to help with reading the stream file and putting the customer address
into the html...


J. Scott Carter
Programmer/Analyst
e-mail: Mailto:scarter@xxxxxxxxxxx
Phone: 214.583.0348

"When I die, I want to die like my grandmother who died peacefully  in her
sleep.
Not screaming like all the passengers in her car."

    - Author Unknown



|---------+------------------------------->
|         |           "Jim Franz"         |
|         |           <franz400@xxxxxxxxxx|
|         |           om>                 |
|         |           Sent by:            |
|         |           midrange-l-bounces@m|
|         |           idrange.com         |
|         |                               |
|         |                               |
|         |           12/17/2003 10:10 AM |
|         |           Please respond to   |
|         |           Midrange Systems    |
|         |           Technical Discussion|
|         |                               |
|---------+------------------------------->
  
>------------------------------------------------------------------------------------------------------------------------------|
  |                                                                             
                                                 |
  |       To:       "Midrange Systems Technical Discussion" 
<midrange-l@xxxxxxxxxxxx>                                            |
  |       cc:                                                                   
                                                 |
  |       Subject:  Re: email design                                            
                                                 |
  
>------------------------------------------------------------------------------------------------------------------------------|




(since i was the original poster of this email question...)
I do appreciate David keeping the lists separate. In many areas,
there may be a blurring of which list is appropriate.
I usually try to be very clear in my posts, but I can see this is not one.

What I was looking for was a pc tool the user can use to generate
the email newsletter, and then drive the sending of the newsletter
from a greenscreen (most likely rpg) process, with selections from
the customer list, and the email addresses currently only exist in
the 400 cust file. The 400 at v4r5 (stuck with Officevision app)
does not yet have the email server going, and would forward to an
Exchange Server. No technicians or operations staff on-site. No
VB programming (yet). Since I was looking for a solution driven
from the 400, midrange-l seemed appropriate. I do appreciate
the answering posts - they have been most helpful.
jim


----- Original Message -----
From: "Michael Naughton" <mnaughton@xxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, December 17, 2003 10:00 AM
Subject: Re: email design


> FWIW, I'm with David on this one. I like having a variety of lists to
> choose from, and the ability to pick only the ones I'm interested in.
Even
> so, I get dozens of messages a day; if there were no filtering, I'd
> probably get hundreds.
>
> While in theory I'm interested in everything, in reality I don't have
time
> to wade through a lot of stuff that has zero relevance to my daily life.
A
> lot of people  have Java questions and tips, but I don't (yet) use Java,
> so I'm not interested. For all I know, the BPCS and C/400 lists are very
> popular, but I really don't know what I would gain from or contribute to
> either of them.
>
> In the end, though, I don't think it really matters what I like or don't
> like. Bottom line: these are David's lists, and in return for all the
time
> and effort he puts into them I think it's only fair for  us to let him
run
> them the way he wants. . . .
>
> Just my $.02 (but I think he's doing a great job)
>
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> writes:
> >IMO -
> >
> >Does it REALLY matter where this subject gets discussed?
> . . .
> >
> >
> >In the end, it really doesn't matter whether we use 15 lists or 1 list
to
> >discuss a computing subject...
>
>
> Mike Naughton
> Senior Programmer/Analyst
> Judd Wire, Inc.
> 124 Turnpike Road
> Turners Falls, MA  01376
> 413-863-4357 x444
> mnaughton@xxxxxxxxxxxx
>
> _______________________________________________
> 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.







As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.