Grabbing Emails

  • Thread starter Thread starter sck10
  • Start date Start date
S

sck10

Hello,

I am working on a new project where I need to:
1. open an email and then create an xml file from the email
2. open the xml file and parse the information.

I would like to be able to do the second step using a web page and then
duplicate it with a Windows Service. Does anybody know of some good links
on how to get started on something like this. I haven't created a Windows
Service before, so this will be new to me.

Thanks, sck10
 
I would like to be able to do the second step using a web page and then
duplicate it with a Windows Service. Does anybody know of some good links
on how to get started on something like this.
Click to expand...

1) Launch your Internet brower (e.g. IE, FireFox, Netscape, Opera, Mozilla
etc)

2) Navigate to http://www.google.com

3) Enter the text below in the box:

"C#" "windows service" tutorial

4) Hit the button
 
sck10,

Reading emails can be challenging. There are 3rd party tools for talking to
email servers to download emails, and there are 3rd part tools for parsing
emails.

Searching for "pop3 mime c#" should give a few reasonable hits.

One important feature is a decent debug mode. Diagnosis why a connection to
an email server isn't working can be challenging... having a debug mode that
shows the underlying protocol conversation is huge help.

There are some "gotcha's" with reading emails... it is not as simple as
Outlook makes it appear. The MIME standard is very very very very flexible.

Typically an email is sent either plain text or MIME. Plain text emails are
easy. MIME emails typically include one, two or more parts. It is not
unusual to see a plain text part and an html part. EMails with attachments
are always mime, and typical contain the plaintext/html portions in sort of
a sub message.

Outlook RTF format is not so bad anymore... there is generally a plain text
version of the message sent along as well. Outlook RTF format with embeded
attachments (eg. screen shots) are difficult to parse.

Good luck,

Rob MacFadyen
 
Thanks Rob. Appreciate the help...


Rob MacFadyen said:
sck10,

Reading emails can be challenging. There are 3rd party tools for talking
to email servers to download emails, and there are 3rd part tools for
parsing emails.

Searching for "pop3 mime c#" should give a few reasonable hits.

One important feature is a decent debug mode. Diagnosis why a connection
to an email server isn't working can be challenging... having a debug mode
that shows the underlying protocol conversation is huge help.

There are some "gotcha's" with reading emails... it is not as simple as
Outlook makes it appear. The MIME standard is very very very very
flexible.

Typically an email is sent either plain text or MIME. Plain text emails
are easy. MIME emails typically include one, two or more parts. It is not
unusual to see a plain text part and an html part. EMails with attachments
are always mime, and typical contain the plaintext/html portions in sort
of a sub message.

Outlook RTF format is not so bad anymore... there is generally a plain
text version of the message sent along as well. Outlook RTF format with
embeded attachments (eg. screen shots) are difficult to parse.

Good luck,

Rob MacFadyen
Click to expand...
 
Hi sck10,

For windows service information and tutorial, you may refer to following
MSDN library and the linked documents in it:

#Introduction to Windows Service Applications
http://msdn2.microsoft.com/en-us/library/d56de412.aspx

I hope this helps. Please feel free to post here if anything is unclear.

Sincerely,
Walter Wang ([email protected], remove 'online.')
Microsoft Online Community Support

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications. If you are using Outlook Express, please make sure you clear the
check box "Tools/Options/Read: Get 300 headers at a time" to see your reply
promptly.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top