Mark, I'm going to answer your question in a rather oblique fashion; basically, I think there's a better way to do what you're doing, though I can't tell you offhand why your way broke between 6.06 and 7.06.
You can use a on-the-fly mailing list for this purpose: use a blocking SMB connection to write out a new USERS.LST to the Imail server, then just send to the list from ASPMail. This saves the bandwidth of the call-and-response Bcc: list (the file dump should be much faster). Even if you're not into it for the long term, you can at least try the mailing list solution as a testing mechanism, as it removes a few possible trouble spots. As far as troubleshooting the current situation, your best bet would be to sniff the packets on the wire as the ASPQmail component communicates with the Imail server and see if there's any evidence of a buffer overflow when submitting the data or the recipients. The Imail logs would show you a outright broken connection, but probably won't give you enough detail if Imail "thinks" the SMTP conversation was generally acceptable and still queues up the messages. You also should try to get your hands on the source of a broken message to see if the attachment MIME encoding is messed up (due to an aborted or overflowed connection) or if it's correct MIME-wise, (meaning ASPQmail just doesn't attach the file at all under certain circumstances). Sandy Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Please visit the Knowledge Base for answers to frequently asked questions: http://www.ipswitch.com/support/IMail/
