Moved Content-Transfer-Encoding generation back into

Moved Content-Transfer-Encoding generation back into
MimeifyPageRevision().  (Note that moving it to MailifyPage() broke
the zip-dumps.  (In multipart MIME message, each part needs to specify
its transfer-encoding --- furthermore the top (multipart) part must
not be encoded.

Urlencode all mime-type parameters (since only US-ASCII is allowed in
the mail headers.)

Eleminated the global $pagedump_format in favor of new define
STRICT_MAILABLE_PAGEDUMPS.

Cleaned up the generated mail headers a bit.  Don't include From:
<foo@bar> unless STRICT_MAILABLE_PAGEDUMPS is set.

Don't put RCS id tags in headers.  There should only be RCS tags in
files which actually come from RCS(/CVS).  For now, I think we should
manually insert headers like:

  X-Rcs-Id: $Id$

in the pgsrc files.

Note that this is legal.  'Unstructured' header values can contain any
US-ASCII characters other than carriage-return and new-line.  (see RFC
2822.)

(Also note that Content-Id:'s must be valid 'msg-id's (see RFC 2822)
--- they look roughly like bracketed e-mail addresses: "<.*@.*>".)

Are MTA's really allowed to strip X-* headers?  (It's not an issue, in
any case, since, as noted above, only the files which are in CVS
should have X-Rcs-Id anyhow.)

git-svn-id: svn://svn.code.sf.net/p/phpwiki/code/trunk@1569 96ab9672-09ca-45d6-a79d-3d69d39ca109