On 23-Sep-2001 Digitalpeer wrote: > It is my understanding that there are ASP engines for Linux and Solaris > also. There are > two software packages that I know of, but neither are free. > > http://www.chilisoft.com/chiliasp/linux.asp is one of them. > > I have some specific questions. I think I am going about interfacing to > xmail completely wrong. I am trying to use the pop protocol (possibly to be > portable across mail servers originally), and I am running into major > problems with speed. My com object is obviously too fast for xmail to > respond (or the vb Winsock control sucks ass more than I thought). It > produces an unstable response when retrieving all messages to a collection > at one time unless I stick a nice pause in there. So I got to thinking, and > thumbing through the xmail code, how much trouble do you think it would be > to write a com object that could straight up read the mailboxes. Of course, > this means that the web interface will have to be run on the same server, or > on a local area network, but that's reasonable. I know this is a huge > thing, but has this been done before? How hard do you think it would be and > how many conflicts where will there be with the com object updating and > xmail server updating mailboxes at the same time? Right now I am just > trying to slap something together, hence VB and the awful Winsock control. > I like to do this with major projects to ease initial troubleshooting.
Do not _absolutely_ get messages from the mailbox. If you want to do things in the right way interface XMail entirely through the network. That means 1) administration using CTRL protocol 2) mail recv using POP3 and 3) mail send using SMTP. Simply consider XMail as a black box that exposes SMTP, POP3 and CTRL interfaces. XMail's POP3 is definitely not slow, check your code. - Davide
