Yes, there is a lot of classic ASP still out there..... *sigh*... My boss ran into an issue with a client of ours where we were redirecting to a link with a comma in it in a classic ASP page. The classic ASP Response.Redirect escapes commas before performing the redirect therefore invalidating the link (BTW, ASP.NET does not do this). Unfortunately you cannot change this behavior so the only workaround we could find is manually setting the HTTP status and location header.

Response.Status = "302 Object moved"
Response.AddHeader "Location", "http://www.somesite.com/yada,yada,yada/default.html"
Response.End

If you happen to be using the Persits mail component and you get the 'Access is denied' exception:

Persits.MailSender.4 error '800a0011'

Access is denied.

/pages/somepage.asp, line 208

You'll probably find, from the Persits support site or elsewhere, that the queue folder needs to have increased permissions. It doesn't however tell you where this is. So here is the default install path for version 4:

C:\Program Files\Persits Software\AspEmail\Queue

As far as the permissions go I have found that granting Read and Write permissions to the accessing account on that folder is sufficient. In IIS 6 the accessing account for .NET will be the identity of the App Pool assigned to the site (if you are not doing impersonation) which is the NetworkService account by default. For Classic ASP it will be the anon account (Which by default is the IUSR_xxx) for anon access or the user/group if you are doing other types of auth.