Hey, I agree with ya'll - whole heartedly. I've already
been taken to task for stating my opinion "no matter
how grounded in fact it might be". So hey - I've given
my estimates and they can decide from there. 
Keith Barrows
Senior Developer | Engineering Services | (303) 531-4489
| kbarrows hartic.com
ASPInsider - http://aspinsiders.com
Sites - http://sol3.net
________________________________
Confidentiality Notice: This email message, including all
the attachments, is for the sole use of the intended
recipient(s) and contains confidential information.
Unauthorized use or disclosure is prohibited. If you are not
the intended recipient, you may not use, disclose, copy or
disseminate this information. If you are not the intended
recipient, please contact the sender immediately by reply
email and destroy all copies of the original message,
including attachments.
________________________________
-----Original Message-----
From: Kevin Fricovsky [mailto:kfricovskybroadway.com]
Sent: Friday, May 11, 2007 7:34 AM
To: aspnet-architectureaspadvice.com
Subject: [aspnet-architecture] RE: ASP.NET 2.0/3.0 and
SMTP/POP3
Aspnetpop3 is the way to go.
No reason to do bake this cake from scratch.
Dave (and his team?) built an excellent collection of tools
for .net developers and aspnetpop3 is one of them. He's also
an expert in the inner working of email communication
components.
The ROI by using aspnetpop3 is exponentially greater than
building this from the ground up on your own.
My suggestion is to convince your employer that not only
will your product be delivered faster, but the overall
solution will cost less to build and employ the very well
tested and industry approved aspnetpop3 component (that even
comes with support if needed).
Keep your "proprietary" business logic in a
façade(or anywhere) and use the component to do you dirty
work.
And just keep it simple.
(ps. If this is a licensing issue here's some info: http://ww
w.advancedintellect.com/licen.aspx)
-----Original Message-----
From: dave wanta [mailto:dave.wanta123aspx.com]
Sent: Thursday, May 10, 2007 10:41 PM
To: aspnet-architectureaspadvice.com
Subject: [aspnet-architecture] RE: ASP.NET 2.0/3.0 and
SMTP/POP3
If you need something quick and dirty, check code project
for some pop3 tutorials. But, be warned. Although the
protocol is simple, there are nuances you will run into,
that can kill days of programming. Like most things, the
devil is in the details.
Cheers!
Dave
----- Original Message -----
From: "Christopher Frazier" <chris.fraziergmail.com>
To: <aspnet-architectureaspadvice.com>
Sent: Thursday, May 10, 2007 5:25 PM
Subject: [aspnet-architecture] RE: ASP.NET 2.0/3.0 and
SMTP/POP3
> It sucks that your client feels that way, because
aspNetPop3 rawks.
>
> --
> -Christopher
> | AspInsider
> http://chrisfrazier.net/
blog
>
> (__/)
> (='.'=) This is Bunny. Copy and paste bunny into your
> (")_(") signature to help him gain world
domination.
>
>
> -----Original Message-----
> From: Barrows, Keith [mailto:kbarrowshartic.com]
> Sent: Wednesday, May 09, 2007 5:26 PM
> To: aspnet-architectureaspadvice.com
> Subject: [aspnet-architecture] ASP.NET 2.0/3.0 and
SMTP/POP3
>
> I've been tasked with researching a possible solution
for a client. I
> am not an email wiz. I can send via SMTP just fine
using the built in
> tools in .NET and IIS with SMTP activated. I've never
dealt with
> programming against POP3.
>
> Where are some good tutorials on how to program for
POP3?
> * Raise event on incoming mail
> * Open message and do some task based on contents
> * Move to a public POP3 if it is for an existing
account
>
> Does WCF have hooks into POP3?
>
> I'm not looking for canned solutions (though that makes
the most sense).
> The client feels it is best to write this solution from
the ground up.
>
> TIA
>
> Keith Barrows
> Senior Developer | Engineering Services | (303)
531-4489 |
> kbarrowshartic.com
> ASPInsider - http://aspinsiders.com
> Sites - http://sol3.net
> ________________________________
>
> Confidentiality Notice: This email message, including
all the
> attachments, is for the sole use of the intended
recipient(s) and
> contains confidential information. Unauthorized use or
disclosure is
> prohibited. If you are not the intended recipient, you
may not use,
> disclose, copy or disseminate this information. If you
are not the
> intended recipient, please contact the sender
immediately by reply
> email and destroy all copies of the original message,
including attachments.
> ________________________________
>
>
> Need SQL Advice? http://sqladvice.com
> Need RegEx Advice? http://regexadvice.com
Need XML Advice?
> http://xmladvice.com
>
>
>
> Need SQL Advice? http://sqladvice.com
> Need RegEx Advice? http://regexadvice.com
Need XML Advice?
> http://xmladvice.com
>
Need SQL Advice? http://sqladvice.com
Need RegEx Advice? http://regexadvice.com
Need XML Advice? http://xmladvice.com
Need SQL Advice? http://sqladvice.com
Need RegEx Advice? http://regexadvice.com
Need XML Advice? http://xmladvice.com
Need SQL Advice? http://sqladvice.com
Need RegEx Advice? http://regexadvice.com
Need XML Advice? http://xmladvice.com
|