"Casey Provance" <ca***@tpasoft.com> wrote in message
news:OWsd93lYFHA.3364@TK2MSFTNGP12.phx.gbl...
> Karl -
>
> Well, you being the VB guru here, I'm not sure how much I could offer....but
> I can share with you what I've done in the past.
>
> My apps come with a "system information" tool which when opened shows the
> user their system specs (kind of like MS's System Information viewer, only
> much simpler and to the point) with additioanl space for input from the user
> (standard text box).  The user could 1) Open this tool at any time via the
> program group or from the app's About box or 2) opt to open the tool when my
> error handler trapped an error.
>
> When ready to send, the user would click a "send report" button and the
> program would email me the results, all via the winsock API and smpt, as Jim
> has suggested.  It's all very neat and simple for the user (as I believe it
> should be) while my program did all the work in the background.  This way I
> never had to bother with email programs (considering the vast amount
> available, it would be impossible to support them all) and the information
> was delivered to me as a support email, at which time I could make a
> diagnosis based on what was sent.  FWIW, my error handler also logs errors
> with as much information as I can gather from the program at the time the
> error occured.
>
> I don't know how much this would be useful to you.  I'd be happy to share
> with you what I have (especially considering all I have learned from your
> MVP site) if you so desire.
>
> Cheers
>
> - Kev
>
>

"Jim Carlock" <anonymous@localhost> wrote in message
news:eNsp2klYFHA.252@TK2MSFTNGP12.phx.gbl...
> Winsock?
>
> The URL you are connecting to is an IP address over a SMTP port
> number? Grab the UID (email id) from the default mail client, provide
> a small dialog for the password, connect to their SMTP server as the
> email client does, then send via SMTP?
>
> Based upon the KBID it looks like you've got a webpage using, so
> that doesn't quite identify that you're using a mail server to send the
> information. I'd be thinking along the lines of using the mail server if
> that's possible.
>
> If you're thinking a client-side app, that's where I'd be leaning, is to
> use a winsock to connect to their mail server, send the message via
> their mail server. Either that or leave a port open on your web-
> server awaiting a certain connections, that way you wouldn't have to
> use email.
>
> Hope that helps.
>
> --
> Jim Carlock
> Please post replies to newsgroup.
>
> "Karl E. Peterson" <k***@mvps.org> wrote:
> Hi --
>
> I have an odd set of requirements that got flummoxed by the maximum URL length
> limitation.  In short:
>
>   * VB5 app with no dependencies other than runtime,
>   * Create an email, ready to send, using default mail client,
>   * Stuff the body text with 100K or more of diagnostics info,
>   * Maintain absolute trust/transparency!
>
> I know I could send the email directly from code, but that's not the goal.  The
> *user* is the one who must press Send, on an email they have full access to edit,
in
> order to preserve every shred of trust that only information they're willing to
> divulge will be sent.
>
> The old standby, ShellExecute a mailto: link, fails because URLs are limited to
2083
> characters (ref: Q208427).  Other ideas?
>
> Thanks...   Karl
> --
> Working Without a .NET?
> http://classicvb.org/petition
>
>
>

>If it's an update, you could provide a text file indicating the
>file used for the update, and it could document exactly what
>is being updated, in an XML format that could be viewed
>through a web-browser:
>
><?xml version="1.0"?>
><Update20050601>
><0001><name="mscomctl.ocx" action="replaced" backup="%systemroot%/system32/oldnnnn/" /></0001>
><0002><name="rrrr.dll" action="replaced" location"xxx" backup="xxx" /></0002>
></Update20050601>
>
>The configuration above needs a little work and is provided as an
>simple example but I see it as doable if you have your own installer
>and it's easy to understand and do.
>
>The numbering provides some organization, easy to read. XML
>provides a neat clean way to view the details inside of IE or
>better browser (like FireFox or Mozilla). Just don't include any
>code inside of the XML document, to keep IE and Explorer from
>crashing.
>
>Document it well enough, and they trust you enough to run your
>update, you'll end up with documentation of the update that you
>and the end-user can use. No trust is lost and if the email is
>documented in such a manner you can keep a copy logged on
>their machine as well as the copy sent to yourself.
>
>Just my two cents.

>"Stefan Berglund" <keepit@in.thegroups> wrote:
>> The trust issue is more moot although I will admit that I'm careful
>> not to betray that trust.
>
>Karl Peterson posted:
>> Yep, looked at this as an option, but don't like the "powerlessness"
>> it leaves the user feeling. Myself, I *hate* it when an application asks
>> to send information back to the Mother Ship, even when it offers me
>> a chance to preview what it says it will send. Without having the
>> ability to hit the Send button personally, I'm just never sure what's
>> going out.
>
>I was just thinking about my own distrusts...
>
>1) I hate software that does not provide a detailed list of actions that
>were imposed,
>2) I hate software that does not provide a way to restore the previous
>state,
>3) I hate software that does not provide individual downloads for
>updates, with detailed explanations of what the update fixes.
>4) Most of all, I keep thinking of this Axialis software that I bought as
>an icon editor, where they provide none of the above, and I have no
>way to roll back updates and it's all done via an update button inside
>the application. I hate that. I really do. <g> And while the software
>works for the most part, I've run into some bugs and I've reported
>the bugs to Axialis, and they've responded, but there is that lack of
>trust that Karl mentions, because the company does not provide
>downloads, does not provide a way to roll back an update, does
>not provide any information about what problems an update fixed,
>does not provide any way of seeing what's being sent to Axialis,
>and all of that stuff just unseats me. It's got a couple really annoying
>things built into it as well that I have issues with, like a built in web
>browser, which I NEVER use and definitely do NOT want, simply
>because it appears to be Internet Explorer running inside of Axialis.
>Absolutely no need for it. <g>
>
>So when Karl posted his response, I kinda looked at his response
>pretty lightly. Upon a second reading, the icon editing software I
>purchased popped into mind and I have to agree with Karl.

"Karl E. Peterson" <k***@mvps.org> wrote in message
news:%23TusMuiYFHA.980@TK2MSFTNGP12.phx.gbl...
> Hi --
>
> I have an odd set of requirements that got flummoxed by the maximum URL
length
> limitation.  In short:
>
>   * VB5 app with no dependencies other than runtime,
>   * Create an email, ready to send, using default mail client,
>   * Stuff the body text with 100K or more of diagnostics info,
>   * Maintain absolute trust/transparency!
>
> I know I could send the email directly from code, but that's not the goal.
The
> *user* is the one who must press Send, on an email they have full access

> characters (ref: Q208427).  Other ideas?
>
> Thanks...   Karl
> --
> Working Without a .NET?
> http://classicvb.org/petition
>
>

"Veign" <NOSPAMinveign@veign.com> wrote in message
news:OCf4ZAmYFHA.2124@TK2MSFTNGP14.phx.gbl...
: Sending Large Emails via ShellExecute
: http://vbnet.mvps.org/index.html?code/internet/shellexecutelargeemail.htm
:
:
: Wonder where this code came from<g> .  Any ideas Randy?
: Sending Large Emails via ShellExecute
: http://emsindia.com/Hindi/H2/C896.html
:
: --
: Chris Hanscom - Microsoft MVP (VB)
: Veign's Resource Center
: http://www.veign.com/vrc_main.asp
: --
: Read. Decide. Sign the petition to Microsoft.
: http://classicvb.org/petition/
:
:
: "Karl E. Peterson" <k***@mvps.org> wrote in message
: news:%23TusMuiYFHA.980@TK2MSFTNGP12.phx.gbl...
: > Hi --
: >
: > I have an odd set of requirements that got flummoxed by the maximum URL
: length
: > limitation.  In short:
: >
: >   * VB5 app with no dependencies other than runtime,
: >   * Create an email, ready to send, using default mail client,
: >   * Stuff the body text with 100K or more of diagnostics info,
: >   * Maintain absolute trust/transparency!
: >
: > I know I could send the email directly from code, but that's not the
goal.
: The
: > *user* is the one who must press Send, on an email they have full access
: to edit, in
: > order to preserve every shred of trust that only information they're
: willing to
: > divulge will be sent.
: >
: > The old standby, ShellExecute a mailto: link, fails because URLs are
: limited to 2083
: > characters (ref: Q208427).  Other ideas?
: >
: > Thanks...   Karl
: > --
: > Working Without a .NET?
: > http://classicvb.org/petition
: >
: >
:
:

"YYZ" <n***@none.com> wrote in message
news:uSZOa%23lYFHA.3320@TK2MSFTNGP12.phx.gbl...
> "Karl E. Peterson" <k***@mvps.org> wrote in message
> news:%23TusMuiYFHA.980@TK2MSFTNGP12.phx.gbl...
> > Hi --
> >
> > I have an odd set of requirements that got flummoxed by the maximum URL
> > length
> > limitation.  In short:
> >
> >  * VB5 app with no dependencies other than runtime,
> >  * Create an email, ready to send, using default mail client,
> >  * Stuff the body text with 100K or more of diagnostics info,
> >  * Maintain absolute trust/transparency!
>
> I'm assuming that your clients are far and wide, so you can't count on any
> certain mail client being used or even present.
>
> Maybe an alternate solution would work?  ie, create a submission form on
> your website, navigate there, pop the fields that you want, and give them
> the opportunity to review before clicking submit, or even the ability to
> cancel.
>
> It sounds like you are trying to be (continue to be) extremely mindful of
> your users' privacy -- good for you.  Is this step really necessary to keep
> the trust you've built?  I'm not judging, merely asking.
>
> I know I didn't solve your problem, but I don't think you CAN do what you
> want to do just via email.  So I thought I'd offer up some alternatives.
>
> Matt
>
>

"Karl E. Peterson" <k***@mvps.org> wrote in message
news:%23TusMuiYFHA.980@TK2MSFTNGP12.phx.gbl...
: Hi --
:
: I have an odd set of requirements that got flummoxed by the maximum URL
length
: limitation.  In short:
:
:  * VB5 app with no dependencies other than runtime,
:  * Create an email, ready to send, using default mail client,
:  * Stuff the body text with 100K or more of diagnostics info,
:  * Maintain absolute trust/transparency!
:
: I know I could send the email directly from code, but that's not the goal.
The
: *user* is the one who must press Send, on an email they have full access

: characters (ref: Q208427).  Other ideas?
:
: Thanks...   Karl
: --
: Working Without a .NET?
: http://classicvb.org/petition
:
:

"Karl E. Peterson" <k***@mvps.org> wrote in message
news:eixsKlgZFHA.1148@tk2msftngp13.phx.gbl...
: Hi Randy --
:
: > MAPI APIs?
:
: Wouldn't that be entirely behind-the-scenes?  (I haven't played with MAPI
for years,
: now.)  Does email client affect this approach?
:
: Thanks...   Karl
: --
: Working Without a .NET?
: http://classicvb.org/petition
:
:

"Karl E. Peterson" <k***@mvps.org> wrote in message
news:%23TusMuiYFHA.980@TK2MSFTNGP12.phx.gbl...
> Hi --
>
> I have an odd set of requirements that got flummoxed by the maximum URL length
> limitation.  In short:
>
>   * VB5 app with no dependencies other than runtime,
>   * Create an email, ready to send, using default mail client,
>   * Stuff the body text with 100K or more of diagnostics info,
>   * Maintain absolute trust/transparency!
>
> I know I could send the email directly from code, but that's not the goal.  The
> *user* is the one who must press Send, on an email they have full access to edit,
in
> order to preserve every shred of trust that only information they're willing to
> divulge will be sent.
>
> The old standby, ShellExecute a mailto: link, fails because URLs are limited to
2083
> characters (ref: Q208427).  Other ideas?
>
> Thanks...   Karl
> --
> Working Without a .NET?
> http://classicvb.org/petition
>
>