Incoming mail and on-the-fly compression

Incoming mail and on-the-fly compression

[Richard Pieri]

-----BEGIN PGP SIGNED MESSAGE-----

I just stumbled into a nasty gotcha, a conflict between Gnus (probably
any version) and any on-the-fly file compression hooks.  This morning,
the code that pulls the system mailbox into a local Incoming file
created a file called 'Incominga003.Z'.  The problem should be apparant:
the '.Z' "extension" gets the file flagged as compressed, so the
compression code tries to decompress it; since it is not compressed,
this fails.

The solution: do not allow periods in the pseudo-random Incoming file
names.

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3
Charset: noconv

iQCVAwUBMZiITZ6VRH7BJMxHAQGwpwQAoWYSLNBsVaCTxQaVl/2xT17nwvseSPgS
Iqpk/C8QXevS5IFnGI92nT1kgBo/T+M9uNy5PGQwcubz8k0ve11VJbtX16OWDC5K
7k7SeNwywQvzXVU42UTqpv/3aYr+20MB7uBGO/TdhmLhwiiRFQ705MEQxhBKQBeN
B1Q8GKxfJso=
=H/kV
-----END PGP SIGNATURE-----
-- 
Richard Pieri/Information Services \ Variety is the spice of life: one day
<ratinox@unilab.dfci.harvard.edu>   \ ignore people, the next day annoy
http://www.dfci.harvard.edu/         \ them. -A cat's guide to life

Re: Incoming mail and on-the-fly compression

[Lars Magne Ingebrigtsen]

Richard Pieri <ratinox@unilab.dfci.harvard.edu> writes:

> I just stumbled into a nasty gotcha, a conflict between Gnus (probably
> any version) and any on-the-fly file compression hooks.  This morning,
> the code that pulls the system mailbox into a local Incoming file
> created a file called 'Incominga003.Z'.  The problem should be apparant:
> the '.Z' "extension" gets the file flagged as compressed, so the
> compression code tries to decompress it; since it is not compressed,
> this fails.

I didn't know that `make-temp-name' creates names like that.  What
system is this on?

-- 
  "Yes.  The journey through the human heart 
     would have to wait until some other time."

Re: Incoming mail and on-the-fly compression

[Richard Pieri]

-----BEGIN PGP SIGNED MESSAGE-----

>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:

LMI> I didn't know that `make-temp-name' creates names like that.  What
LMI> system is this on?

Sparc Sun Solaris 2.5, XEmacs 19.13, Gnus 5.0.15.

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3
Charset: noconv

iQCVAwUBMZ/H/56VRH7BJMxHAQGIyQQAnIxWCbXKsYbgAzN6QKnPOF/P/5DPmzXQ
5M3QKEFDo06X2/HVwWLfpV6TwjnUHhYTTDlbJ0DPoAE/Us208lT0MQCWCGYrPLrH
WLpL9neo+yb12gBAfYatiYMQWNWo4EUYYte8gWKhF3nMrO3JvO+PRj/nbkjkCw9t
lHV33GUo2ac=
=Tr+k
-----END PGP SIGNATURE-----
-- 
Richard Pieri/Information Services \ Make your mark in the world, or at least
<ratinox@unilab.dfci.harvard.edu>   \ spray in each corner. -A cat's guide to
http://www.dfci.harvard.edu/         \ life

Re: Incoming mail and on-the-fly compression

[Mark Borges]

Just as a datapoint,

>> On 19 May 1996 21:16:45 -0400,
>> Richard Pieri(rp) wrote:
>>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:

LMI> I didn't know that `make-temp-name' creates names like that.  What
LMI> system is this on?

rp> Sparc Sun Solaris 2.5, XEmacs 19.13, Gnus 5.0.15.

Sparc Sun Solaris 2.5, XEmacs 19.14, sgnus-0.89

doesn't:

  (make-temp-name "foo") ==> "fooa005QB"

-- 
  -mb-

Re: Incoming mail and on-the-fly compression

[Stephen Peters]

Mark Borges <mdb@cdc.noaa.gov> writes:

> >> On 19 May 1996 21:16:45 -0400,
> >> Richard Pieri(rp) wrote:
> >>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
> 
> LMI> I didn't know that `make-temp-name' creates names like that.  What
> LMI> system is this on?
> 
> rp> Sparc Sun Solaris 2.5, XEmacs 19.13, Gnus 5.0.15.
> 
> Sparc Sun Solaris 2.5, XEmacs 19.14, sgnus-0.89
> 
> doesn't:
> 
>   (make-temp-name "foo") ==> "fooa005QB"

Actually, it probably does.

Because make-temp-name uses the mktemp() function (in Emacs 19, and I
would assume in XEmacs as well), this is kind of system-specific.  On
Solaris 2.5, it appears that the set of characters used for those last
6 positions can include both the period (.) and the underscore (_)
characters as well as the alphanumeric characters (bringing the number
of characters used to 64 -- probably for efficiency considerations).
On the other hand, the GNU C library only uses letters and digits in
its implementation.  I will leave the behavior of other systems as an
exercise for the reader.

In short, on some machines it's quite possible to see temp files
ending in ".Z" or ".gz", or even any other special one- or
two-character extension.

-- 
Stephen L. Peters                         speters%samsun@us.oracle.com
 For PGP key, use keyservers or send email with subject: SEND PGP KEY
      PGP fingerprint: BFA4 D0CF 8925 08AE  0CA5 CCDD 343D 6AC6
	Oracle won't speak for me, so I won't speak for them.

Re: Incoming mail and on-the-fly compression

[Lars Magne Ingebrigtsen]

Stephen Peters <speters%samsun@us.oracle.com> writes:

> In short, on some machines it's quite possible to see temp files
> ending in ".Z" or ".gz", or even any other special one- or
> two-character extension.

How annoying.  Perhaps nnmail should use raw insertion of the Incoming
files?  Probably.  I'll have it do that instead.

Hm.  Gremlins:

(fset 'nnheader-insert-raw-file-contents 'insert-file-contents)

I certainly didn't do that.  That should be
`insert-file-contents-literally'.  Fix in September Gnus v0.90.

-- 
  "Yes.  The journey through the human heart 
     would have to wait until some other time."