If you like to play around in the IFS I think all mail coming into the IBM SMTP server creates a file in a folder in the IFS. Look around in QTCPTMM. You could look in the IFS on a regular basis and read the file, decode the message and process it.
I just sent an test email to nondeliver@xxxxxxxxxxxxxxxxxxxx and found a file named JW375776.NOTS in NONDELIVER folder under MAIL under QTCPTMM
Contents below. Scanning these messages for relevant data is lots of fun :)
Received: from spamfilter.pct.edu(barracuda.pct.edu[10.133.2.113])
by AS400ADM.PCT.EDU (IBM i5/OS SMTP V05R04M00) with TCP;
Tue, 9 Sep 2008 13:37:57 -0400
Received: from exch-hub2.pct.edu (localhost [127.0.0.1])
by spamfilter.pct.edu (Spam Firewall) with ESMTP id 0A3A1FBBF7E
for <nondeliver@xxxxxxxxxxxxxxxx>; Tue, 9 Sep 2008 13:37:56 -0400 (EDT)
Received: from exch-hub2.pct.edu (exch-hub2.pct.edu [10.133.2.26]) by spamfilter.pct.edu with ESMTP id Gu6ZyKNgCWsnhPgd (version=TLSv1 cipher=RC4-MD5 bits=128 verify=NO) for <nondeliver@xxxxxxxxxxxxxxxx>; Tue, 09 Sep 2008 13:37:56 -0400 (EDT)
Received: from exch-mbx1.pct.edu ([10.133.2.21]) by exch-hub2.pct.edu
([10.133.2.26]) with mapi; Tue, 9 Sep 2008 13:37:56 -0400
From: Mike Cunningham <mcunning@xxxxxxx>
To: "'nondeliver@xxxxxxxxxxxxxxxx'" <nondeliver@xxxxxxxxxxxxxxxx>
Date: Tue, 9 Sep 2008 13:37:55 -0400
X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at pct.edu
Content-Type: text/plain; charset="us-ascii"
Content-Type: text/html; charset="us-ascii"
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
/* Font Definitions */
panose-1:2 4 5 3 5 4 6 3 2 4;}
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
margin:1.0in 1.0in 1.0in 1.0in;}
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:idmap v:ext=3D"edit" data=3D"1" />
<body lang=3DEN-US link=3Dblue vlink=3Dpurple>
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Emily Smith
Sent: Tuesday, September 09, 2008 12:01 PM
Subject: Receiving Emails on the I
We have a system in place that sends emails and/or text messages to our clients. These emails contain critical alerts (e.g. an ATM being out of service). We use javamail to accomplish this, and we route the emails thru our email server. Currently only critical alerts are emailed out. In order to see non critical alerts clients must sign on to the I, or they can call in and get the alerts over the phone. The option to get the alerts over the phone is going away in the next few months due to high cost.
Now I'm tasked with finding a way for users to send an email to request an email of non critical alerts. Basically the flow would be something like...
1. Client sends email to 'Alertretriever@xxxxxxxxxxx' Subject Line = 'Alerts Request' Body = 'Clientemailorcell@xxxxxxxxxxxx' Client Number 1234.
2. Our email server receives the email and then forwards it (somehow?) to the I.
3. A never ending program receives the email, and based on the subject line and information in the body of the email formats and sends out an email with the alerts requested by the client.
If anybody has done anything like this, and could give me any pointers I'd really appreciate this. Also, if this is something that can't be done, I guess this is a good time for me to find that out also.
Vendors are welcome to reply also, but I would definitely prefer to do something home grown.
Thanks in advance.
CONFIDENTIALITY NOTICE: This email message is private,
confidential property of the sender, and the materials
may be privileged communications intended solely for
the receipt, use, benefit, and information of the intended
recipient indicated above. If you are not the intended
recipient, you are hereby notified that any review,
disclosure,distribution, copying or taking of any
other action in reference to the contents of this message
is strictly prohibited, and may result in legal liability
on your part. If you have received this message in error,
please notify the sender immediately and delete this
message from your system. We believe that this email
and any attachments are free of any virus or other defect
that might affect any computer system that it is received
and opened in, however, it is the responsibility of the
recipient to ensure that it is virus free and the sender
accepts no responsibility for any loss or damage.
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives