Re: report-xemacs-bug?
Simon Josefsson wrote:
> I thought it did - there was no error message after I
> installed mail-lib & invoked report-xemacs-bug, and the test
> e-mail got into my outgoing queue. Then I've removed the test
> message and sent a real bug report (with the subject "Syntax
> highlighting turned off on startup") - but it looks like it
> didn't leave my computer at all... :-(
Can you reproduce it?
Well, I'm not very eager to keep trying to reproduce
e-mail bugs
on public lists... Upon reflection, I think the bug report does
leave my computer, but it's refused by xemacs-beta filters because
it has invalid return path (somebody can check that if they want -
hint, hint... :-) ). The behavior on my machine is 100%
reproducible.
> P.S: One difference in (correctly handled) messages netscape
> puts through my mail system to the outgoing queue (like this
> one) vs. (apparently incorrectly handled) messages xemacs puts
> there is the Return-Path mail header: using netscape, I get
> Return-Path: <vbar(a)comp.cz>
> while xemacs insists on
> Return-Path: <>
> which isn't valid anywhere outside my computer. Perhaps it is
> an xemacs bug after all...
Return-Path is not added by XEmacs.
I know, but why does qmail use different return
addresses
depending on the e-mail client? Perhaps I should subscribe to
qmail group, too...
Do you really use local delivery with QMail using netscape? I
doubt Netscape supports that. Maybe you are using QMail as a
SMTP server on your local machine, and if so Adrian's hints
Right, that's
what I have.
should work.
We'll see... :-)
Bye
Vasek