\201 problem (only in news headers) introduced in p0.45 or p0.46

\201 problem (only in news headers) introduced in p0.45 or p0.46

[Peter von der Ahé]

Content-Transfer-Encoding: 8bit


Hi!

When I post to a newsgroup I have problems with latin1 characters in
the headers.  Characters like æøåé in headers are still "mule"
encoded, this means that the From: field, as an example, is:

   From: Peter von der Ah\201\351 ...

not

   From: Peter von der Ah\351 ...

The body is OK.

The strange thing is that, whenever I send a mail, the headers are OK.

As stated in the subject line, the problem was introduced in p0.45 or
p0.46.  I have tried p0.50 and the problem is still present.

I'm using Emacs-20.3 (no MBSK, no --unibyte), and I have this Mule
setup:

       (set-language-environment "Latin-1")
       (modify-coding-system-alist 'file "" 'latin-1)


M-x describe-coding-system gives this output:

Coding system for saving this buffer:
  Not set locally, use the default.
Default coding system (for new files):
  1 -- iso-latin-1 (alias: iso-8859-1 latin-1)
Coding system for keyboard input:
  nil
Coding system for terminal output:
  nil
Defaults for subprocess I/O:
  decoding: 1 -- iso-latin-1 (alias: iso-8859-1 latin-1)
  encoding: 1 -- iso-latin-1 (alias: iso-8859-1 latin-1)

Priority order for recognizing coding systems when reading files:
  1. iso-latin-1 (alias: iso-8859-1 latin-1)
  2. iso-2022-jp (alias: junet)
  3. iso-2022-7bit 
  4. iso-2022-7bit-lock (alias: iso-2022-int-1)
  5. iso-2022-8bit-ss2 
  6. emacs-mule 
  7. raw-text 
  8. japanese-shift-jis (alias: shift_jis sjis)
  9. chinese-big5 (alias: big5 cn-big5)
  10. no-conversion (alias: binary)

  Other coding systems cannot be distinguished automatically
  from these, and therefore cannot be recognized automatically
  with the present coding system priorities.

  The followings are decoded correctly but recognized as iso-2022-7bit-lock:
    iso-2022-7bit-ss2 iso-2022-7bit-lock-ss2 iso-2022-cn iso-2022-cn-ext iso-2022-kr

Particular coding systems specified for certain file names:

  OPERATION	TARGET PATTERN		CODING SYSTEM(s)
  ---------	--------------		----------------
  File I/O	"\\.gz\\(~\\|\\.~[0-9]+~\\)?\\'"
					(no-conversion . no-conversion)
		"\\.tgz\\'"		(no-conversion . no-conversion)
		"\\.bz2\\'"		(no-conversion . no-conversion)
		"\\.Z\\(~\\|\\.~[0-9]+~\\)?\\'"
					(no-conversion . no-conversion)
		"\\.elc$"		(emacs-mule . emacs-mule)
		"\\(\\`\\|/\\)loaddefs.el$"
					(no-conversion . no-conversion)
		"\\.tar$"		(no-conversion . no-conversion)
		""			(latin-1 . latin-1)
  Process I/O	nothing specified
  Network I/O	nothing specified


Kind regards
Peter

-- 
Peter von der Ahé · Systems programmer · <URL:http://www.daimi.aau.dk/~pahe/> 
| Phone: office (540.030): +45 89 42 31 41, home: +45 86 13 26 34        ---+
|              "Feltet havde bestilt en Hamburger, men fik den ikke spist." |
+---                                         -- Claus Elgaard (TV2 Sporten) |
.

Re: \201 problem (only in news headers) introduced in p0.45 or p0.46

[Lars Magne Ingebrigtsen]

nospam2159@daimi.au.dk (Peter von der Ahé) writes:

> When I post to a newsgroup I have problems with latin1 characters in
> the headers.  Characters like æøåé in headers are still "mule"
> encoded, this means that the From: field, as an example, is:
> 
>    From: Peter von der Ah\201\351 ...

This sounds like a problem in the nntp code.  Has anyone else seen
this? 

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: \201 problem (only in news headers) introduced in p0.45 or p0.46

[Peter von der Ahé]

>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

 LMI> nospam2159@daimi.au.dk (Peter von der Ahé) writes:
 >> When I post to a newsgroup I have problems with latin1 characters
 >> in the headers.  Characters like æøåé in headers are still "mule"
 >> encoded, this means that the From: field, as an example, is:
 >> 
 >> From: Peter von der Ah\201\351 ...

 LMI> This sounds like a problem in the nntp code.  Has anyone else
 LMI> seen this?

It is funny that problem is not present when I post to the ding list
(I post via the news gateway at sunsite.auc.dk).

The problem is still present in p0.51.

I have posted some tests to news.daimi.au.dk+daimi.test, but messages
do not live long there.

If anyone wants to test posting to news.daimi.au.dk, I can talk to our
newsadmin to open up for postings.

Kind Regards
Peter
.

Re: \201 problem (only in news headers) introduced in p0.45 or p0.46

[Peter von der Ahé]

>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

 LMI> nospam2159@daimi.au.dk (Peter von der Ahé) writes:
 >> When I post to a newsgroup I have problems with latin1 characters
 >> in the headers.  Characters like æøåé in headers are still "mule"
 >> encoded, this means that the From: field, as an example, is:
 >> 
 >> From: Peter von der Ah\201\351 ...

 LMI> This sounds like a problem in the nntp code.  Has anyone else
 LMI> seen this?

I think it could be a problem in message-send-news or
message-generate-headers.  I observed that the "Subject:" field has no
problems if the message has first gone through the draft folder.

I have started using this hook:

(defun my-pgnus-201-hack ()
  (mm-encode-coding-region (point-min) (point-max) 'latin-1))

(add-hook 'message-header-hook (function my-pgnus-201-hack))

And now the problem can no longer be observed.

Kind Regards
Peter Ahé

-- 
period
.

Re: \201 problem (only in news headers) introduced in p0.45 or p0.46

[Lars Magne Ingebrigtsen]

pahe@daimi.au.dk (Peter von der Ahé) writes:

> I think it could be a problem in message-send-news or
> message-generate-headers.  

Yup.  Fix in Pterodactyl Gnus v0.52.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: \201 problem (only in news headers) introduced in p0.45 or p0.46

[Jason L Tibbitts III]

>>>>> "KS" == Kurt Swanson <ksw@dna.lth.se> writes:

KS> I noticed this as well.  There must be some sort of bad characters
KS> filter in the majordomo thang.

I've been away and am just catching up, but I just wanted to note that
Majordomo does no filtering whatsoever.  It will pass headers and bodies
through exactly as it receives them.

 - J<