1 / 68

> 1) I notice that when someone sends an HTML message (via Netscape, for

> 1) I notice that when someone sends an HTML message (via Netscape, for. > instance) that the resulting message contains the list header, followed. > by the MIME attachment, and the list footer. Under Netscape, at least,.

ivie
Download Presentation

> 1) I notice that when someone sends an HTML message (via Netscape, for

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. > 1) I notice that when someone sends an HTML message (via Netscape, for

  2. > instance) that the resulting message contains the list header, followed

  3. > by the MIME attachment, and the list footer. Under Netscape, at least,

  4. > it only displays the MIME attachment. Is that a Netscape problem or a

  5. > problem in Mailman with handling HTML messages?

  6. It's kind of a combination of both. Chances are that your document

  7. has a header like this:

  8. Content-type: multipart/mixed; boundary=my-boundary

  9. Then your message body looks like this:

  10. Hi there! here's a message

  11. --my-boundary

  12. Content-type: image/gif

  13. Content-disposition: attachment; filename="image.gif"

  14. Content-description: image.gif

  15. Content-Transfer-Encoding: base64

  16. garbagesquiggleunreadabletextandnumbersthatmagicallybecomeanimage

  17. garbagesquiggleunreadabletextandnumbersthatmagicallybecomeanimage

  18. garbagesquiggleunreadabletextandnumbersthatmagicallybecomeanimage

  19. garbagesquiggleunreadabletextandnumbersthatmagicallybecomeanimage

  20. --my-boundary--

  21. Hi there! here's a message

  22. This tells your reader that anything encapsulated within the

  23. "my-boundary" tokens is a MIME attachment. Anything outside of

  24. that is ignored (unless you have a non-MIME-aware reader.

  25. A "solution" is to wrap the header and footer with boundaries

  26. as well:

  27. --my-boundary

  28. Content-type: text/plain; charset=US-ASCII

  29. Hi there! here's a message

  30. The termination string "--my-boundary--" should also be pulled out of

  31. its current location and added to the end of the message.

  32. But I don't know if it's right for mailman to do this... It's kind

  33. of icky. At any rate, I doubt that anyone will do it until 1.0 is

  34. taken out of beta.

  35. > 2) Is there a way where I can automatically restrict subscribers to a

  36. > subnet or domain name? I want to use the list internally to my company,

  37. > but there's nothing to keep an outside person from subscribing, unless

  38. > someone moderates every subscribe request.

  39. Not currently, unless you wrap the list aliases with something like

  40. procmail and to some pre-mailman filtering.

  41. See

  42. http://www.python.org/pipermail/mailman-users/1999-March/000912.html

  43. > 3) Is there a way to restrict attachments? I did see something about

  44. > this on the archives, but there wasn't any answer given. I guess not,

  45. > then, eh?

  46. The above URL can be used to catch attachments, or you can also add

  47. certain headers or header regexes to bounce_matching_headers (under

  48. the privacy menu). Just restrict

More Related