I have the same problem as above, where the web server and mail server are seperate. I toyed with the idea of setting up a mail server on the web server so that I could forward messages and pipe the data in, but since they were both windows servers I wasnt sure it could be done. The cygwin/exim option should work, but if you want an alternative you can try event based pop3 fetching (as opposed to timing based pop3 fetching).
Basically, if your mail server lets you do custom processing for individual accounts, you set it up so that whenever an email comes in it initiates a wget.exe request to start the pop3 fetching. I'm using xmail, so all I had to do was add a mailproc.tab to the users mailbox with the following:
Code:
"mailbox"
"external" "0" "300" "C:\install\wget.exe" "-q" "-O nul" "http://DOMAINNAME/helpdesk/cron/index.php?_t=parser"
This basically says that all emails for this user should be sent to the users mailbox first and then run an external script with normal priority, 300ms timeout, calling wget.exe to initiate the parser cron job. Kayako will then pull the email from the mail server using POP3 and parse it immediately after it arrives. As an added benifit, if no emails come in, the cron job doesn run. Works great so far, and much easier than setting up a second mail server and messing with piping the data.