Thanks to all the folks who posted stuff about Blat. With this abundance of reference material, I was able to sort it out in only 4 hours <g>.
I had been putting off converting from using Outlook for sending mail to Blat, but recently discovered the last straw with Outlook: code that was working fine just stopped filling in the message body. Probably some change MS made to improve Outlook security, and I probably could have sorted it out with Redemption (?), but I had been wanting to convert to Blat anyway. Now that I've got it working, I really like it and highly recommend it. It does everything Outlook does (that I need, anyway). And repeating what's been said by others, it runs just fine with blat.dll installed in the product's folder (no system folders involved). One mention, the gotcha that wasted most of my time: I'm using Frontiernet DSL here for outgoing mail, but incoming mail from a different POP server. As such, my Outlook setup has userid/pw that is used for the POP server, but (evidentially) there is no userid/pw for the SMTP server. The net of this is that the SMTP (outgoing) server accepts and sends mail sent to -server smtp.frontiernet.net:25 without a userid/password (-u and -pw parms) specified (that is, BLAT only works when these parms are omitted; all that's needed is the SMTP server address and the port). Probably an unusual email setup, but thought to mention it because it had me going for a while. Bill _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
