> > On Sat, 15 Feb 2003, Newsmirror wrote: > > > > > > > > > You should't care about the XMail spool header. You should read up to > > > reading a line with "<<MAIL-DATA>>". The real RFC822 message will follow. > > > > > > > actually I do care alot, the Scope parsing routine does indeed, > > if MAIL_FROM or RCPT_TO are undefined by argument it'll drag info > > from the 2nd and 3rd fields accordingly. anyways, tell me what one > > line 1 holds please so I can adapt. > > No, that's the wrong approach. You MUST get such data from @@* macros > since the spool internal format might change any time. What will never > change is that the real RFC822 message will start after the "<<MAIL-DATA>>" > line.
wrong approach, yeah I know, but I am in stuck smack dab in the middle of undefined data or picking this from the XMail header, due to filter/mailproc mishaps. looking at things I am normally a programmer, but in the smtp world I am mainly a admin kind of guy. if X or Y changes over versions I would like to know exactly why/how. I'd like to think we are working in the same lane, an explanation of "info data" would still help... /thomas. > > > > - Davide > > - > To unsubscribe from this list: send the line "unsubscribe xmail" in > the body of a message to [EMAIL PROTECTED] > For general help: send the line "help" in the body of a message to > [EMAIL PROTECTED] > > > > -- > ---------------------------------------------------------------------------- > XMail::Scope::nntpfwd v1.00 | 2003-02-15 05:01:32Z > <nntp://news.saltstorm.net/saltstorm.xmail/3576> - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
