RE: Aaron Bartell Email Utility

["Briggs, Trevor (TBriggs2)" <TBriggs2@xxxxxxxxxxx>]

Sorry, I probably didn't explain myself very well. All I'm trying to say
is that you sound like you're setting yourself up to use email for this
process, knowing in advance that there's a high probability that this
isn't going to work for all your customers and yet aren't preparing an
alternative. Many people have suggested FTP or 3rd-party sites that have
no size restrictions and would work for ALL your customers. I'm assuming
that you're going to know who your customers are in advance and won't be
getting files from random strangers, so when you establish your
relationship with that customer you just tell them that email has
restrictions, but to avoid this you have created X functionality for
their benefit.

Trevor Briggs
Analyst/Programmer
Lincare, Inc.
(727) 431-1246
TBriggs2@xxxxxxxxxxx

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, November 14, 2012 11:26 AM
To: RPG programming on the IBM i / System i
Subject: RE: Aaron Bartell Email Utility

What potential problems - that their ISP may invalidate it?  Should we 
also warn them that their email system may not work if they trench the 
cable out?  We could warn them - if it was something we were causing. 
We're not.  We're allowing them to send the attachment.  If we were 
blocking them then we'd send them a message like the one I get when I
try 
to send too large attachments to IBM.  Comes from their email system. 
Since I am not blocking it, any problems caused would be by forces
beyond 
my control.  What are you suggesting?  If I receive any email from any 
person and if there's an attachment over xMB I return them a message
"Dude, we have no trouble with your attachment, and since it got
through, 
evidently your system doesn't either.  This is not to say that your
system 
(or some intermediary) may not have trouble with it in the future.  You 
may wish to reduce your attachment size to something smaller than xMB."

Seems rather odd to me.


Rob Berendt