Bug#557804: vm: does not conform to RFC 822 skipping
Brian Denheyer
Version: 8.0.12-7
Severity: normal
Using 'R' to reply to many e-mails results in a
"does not conform to RFC 822 skipping" message.
Some e-mails cause several of these messages.
The cite-er cannot retrieve the correct reply-to name when this happens.
The errors seem to be associated with the _body_ of the message, not the
_body_ of the message and not the header, as the error message is
referring to lines in the body.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: powerpc (ppc64)
Kernel: Linux 2.6.26-2-powerpc64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages vm depends on:
ii dpkg 1.15.4.1 Debian package management system
ii emacs23 [emacsen] 23.1+1-5 The GNU Emacs editor (with GTK+ us
ii install-info 4.13a.dfsg.1-5 Manage installed documentation in
ii make 3.81-7 An utility for Directing compilati
ii ucf 3.0024 Update Configuration File: preserv
vm recommends no packages.
Versions of packages vm suggests:
ii exim4 4.69-11 metapackage to ease Exim MTA (v4)
ii exim4-daemon-light [mail-tran 4.69-11+b1 lightweight Exim MTA (v4) daemon
pn stunnel <none> (no description available)
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Manoj Srivastava
thanks
Hi,
I have never seen that behaviour. There is little to go on in
the bug report -- could you please provide the messages that trigger
this condition, and the actual log, or otherwise steps how to reproduce
this error?
manoj
--
If you explain so clearly that nobody can misunderstand, somebody will.
Manoj Srivastava <sriv...@acm.org> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
sriv...@ieee.org
I opened up the error.txt in VM (after adding a From line at
top), to simulate a new mbox folder, and hit F. You can see the
results below (I do not use supercite).
So, this seems more like a problem in your setup, or possibly
with supercite, and not VM proper. I think this bug should be
reassigned to supercite.
manoj
Manoj Srivastava writes:
> tags 557804 + unreproducible moreinfo
> thanks
>
> Hi,
>
> I have never seen that behaviour. There is little to go on in
> the bug report -- could you please provide the messages that trigger
> this condition, and the actual log, or otherwise steps how to reproduce
> this error?
>
> manoj
> --
> If you explain so clearly that nobody can misunderstand, somebody will.
> Manoj Srivastava <sriv...@acm.org> <http://www.golden-gryphon.com/>
> 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
Manoj Srivastava <sriv...@acm.org>
Manoj Srivastava
thanks
On Tue, Nov 24 2009, Brian Denheyer wrote:
> I forgot that I was explicitly enabling supercite.
> I disabled it, and now I have no problem.
> So, definitely an sc bug.
> How do I re-assign the bug report ?
Done above.
> I do have another bug report :-)
>
> If you kill a message it will ask you if you want to save the file to
> postponed.
> If postponed does not already exist then it throws an error.
> It probably needs to create the file if it does not exist (?)
Kill a message? You mean a message you are composing? VM does
not itself do anything to write/compose email, it just defers to what
Emacs has. If this is happening during outgoing message composition,
you need to figure out where emacs23 is going wrong.
manoj
--
Be a better psychiatrist and the world will beat a psychopath to your
door.
Manoj Srivastava <sriv...@debian.org> <http://www.debian.org/~srivasta/>
era eriksson
The request in the bug report to supply a sample with which this can be
reproduced is still topical. Apparently a file "error.txt" was
communicated in private (?) but it is not attached to the bug report.
Manoj or Brian, could you please attach it there? Also, minimal repro
steps would be appreciated. Thanks in advance!
/* era */
--
If this were a real .signature, it would suck less. Well, maybe not.