> Hi,
>
> I'm trying to help a user who is subscribed to a list here at the
> University at Albany.  She wants to send a WordPerfect file through her
> list, and I'm trying to find an Attachments= keyword to allow this.
>
> Her list is currently configured as this:
>
> Attachments= application/*msword,application/*excel,application/pdf,
> Attachments= image/gif,image/jpeg
>
> And it's not allowing the .WPD attachment through.  I've tried testing with
> a test list, and various email clients, and am having trouble finding the
> entry that will allow all WordPerfect attachments through, in the way that
> application/*msword allows all Word documents.
>
> When sending this .WPD file from OE6, it seems to be tagged as
> multipart/alternative.  From NS4.8, it shows it as
> application/x-unknown-content-typeWP9DOC.  So the .WPD file is not being
> consistently recognized as a certain content-type.

From the manual...
The ability of LISTSERV to filter or reject messages that contain MIME attachments
is completely dependent on the ability of the poster's mail client to properly identify
the MIME attachment when the mail is originally sent.  Filtering/rejection is done
based on the Content-Type headers found in the message--NOT by evaluation
of the actual contents of the attachment.

The excepted media types can be found here:
http://www.isi.edu/in-notes/iana/assignments/media-types/

The only one I see pertaining to WP is  application/wordperfect5.1
So I'm sure you'll never see all mail clients uniformly use a particular
subtype for all WP files. I believe RFC 1341 states that unknown
applications should be  application/octet-stream,  which basically means
they are executable binaries. I think some mail clients use that as a
default for all binary attachments also.

So I think your only safe alternative is to have the various users send
WP files to you, check the raw message and add those subtypes to your list
of allowed ones.

> When I put Attachments= application/x-unknown-content-typeWP9DOC, and send
> the attachment from NS4.8, it passes through this list ok.  However, if I
> send from OE6, it gets rejected as multipart/alternative.

Good ol' MS :-)  Any message with an attachment should be:
Content-type: Multipart/Mixed  Then other types and subtypes
are nested below that. Including the attachment itself and
mutipart/alternatives, if the message body wasn't plain text :-)

> A related question:  Does Listserv recognize the * in
> application/*msword as a wildcard?  If not, what is the purpose of the
> asterisk?

Yes, but I don't know why one is used/needed.