× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: tracking down MSF problems
  • From: Joel Fritz <JFritz@xxxxxxxxxxxxxxxx>
  • Date: Fri, 9 Feb 2001 13:00:04 -0800

I've been playing with Dave Leland's wrapper for qtmmsendmail and trying to
pervert uh modify it to send messages based on boilerplate HTML in an IFS
file.  I'm mostly sending messages to my address on our M$ Exchange server.
They mostly get through.  Every now and then a message will fail.  I can see
in the MSF instance job logs entries for messages that the MSF couldn't
process.  The errors seem to be written by the mail forwarding exit program.
I've also looked in the journal QZMF.  Are there any other places I could
look?  I may be thick, but the information I've been able to find so far
seems to tell me that the MSF was unable to forward a message that I sent
without offering much detail.  

I have two versions of the code running, the original from the News 400
article, and my modified version.  Both have the forwarding problem.  Snddst
seems to work every time. 

TIA 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.