Added UUEncoding to System.Web.Mail for attachment encoding. So now both of
the encoding techniques work for attachments UUEncode, Base64. Soon the mail
api is totally complete since there is only some minor parts left to fix.
Great news!!!
----------------------------------------------------------------------- Here are some issues in MS.NET System.Web.Mail. i would like to have some comments here on how the mono System.Web.Mail should handled these issues:
* SmtpMail.Send throws HttpExceptions (why?)
In Win2000, IIS 5.0 (the web server) can be configured to provide 'Virtual SMTP', as a forwarder to Exchange or other true smtp server. In that case, probably it will probably generate HTTPExceptions.
* Bcc is completely ignored
In this issue I think we should do it the rightway. Forget what MS' implementation does here.
* As soon as you add an attachment with UUEncode explicitly, all the other attachments will be encoded with UUEncode regardless of what you have specified :)
Could it be that some RFC mandates it? If not, doesn't follow MS either.
* Text file attachments are allways encoded using Quoted printable regardless
of what you have specified explicitly.
Ditto...
* Filename for attachments must be absolute. if they are not you get:
HttpException( "Unknown protocol" );
If they aren't absolute how can you find them, relative to the application directory, or the current directory, or relative to the first non-relative attachment?
I think, here, you must follow what MS has done, because you don't have the concept of a Base URL as you have in the HTML/XML world.
Best regards
Per Arneng
Keep the good work, and happy hackings,
Rafael Teixeira Brazilian Polymath Mono, MonoQLE Hacker
_________________________________________________________________
The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail
_______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
