The re-writing of the email addresses was unintentional, done by the list's software, and I had no idea it was there to trigger.
But it is my fault. My normal sending of email isn't from my home boxen, but through a web form. I pop email down to read. Unfortunately, the web form also attaches a reply-to [EMAIL PROTECTED], which is the "account" I logged into for getting the webmail form, regardless of my putting [EMAIL PROTECTED] in the From: HTML form entry box. This web form behaviour interfered with my subscribing to the list a couple months ago, and it also causes my messages to be blocked for some reason. So I sent the message in question by a direct telnet to port SMTP and some X-Windows scooping. I entered the envelope info, but apparently it would be good to repeat it again in the inside headers, so as not to trigger that TROLL. In reply to Jarno, thanks, I'll try the 'months' solution next waking spell. Jarno wrote: # I would imagine that this error message has # nothing to do with the example in Mike's book, # but rather with the fact that your stylesheet # is not generating valid FO. I said the line was erroneous, and that that one line triggered all the error msgs. Without it, no error msgs. I take it you agree, but wish to state it in different terms. However, could you or someone else tell me in a clearer fashion how I can run my FOP and have the ESXLT functions available as "native", i.e. no "import" needed. Thank youz. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
