Krause, Uwe wrote:
Not only Outlook ... try to get a EUR through the list ...
I assume you mean you have your list configured for German (ISO-8859-1)
but then send an email with a Euro sign character (ISO-8859-11) to the list.
This is one special case where I think Mailman should not assume t
e interested in starting an Icelandic translation!
Thanks for your efforts.
Ben Gertzfield
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-m
Mark Koek wrote:
Hello list,
After I added some lines to the footer of my list run by Mailman 2.1,
it has started converting the list messages (plain old text only) into
multipart/mixed MIME messages, with the footer in a separate
text/plain attachment.
Subscribers are complaining because not
Kevin McCann wrote:
Thanks, Ben. I had initially been thinking this was strictly an Outlook
problem, too. But I became skeptical as I realised that there are still two
big questions:
1) Why do these same Outlook clients not have problems receiving
attachment-less messages with footers from other M
Kevin McCann wrote:
Isn't the solution to just insert the footer as a plain text message
part before sending? Something like:
--_=_NextPart_000_0149566.27838596
Content-Type: text/plain;
charset="iso-8859-1"
Here's my groovy footer
The HTML content is in it's own message section,
Kevin McCann wrote:
FWIW,I experience the same problem as jsmith and my preferred language
setting is US English. I'm at mm 2.1.2, sendmail, RH 8.0). I have had to
configure my lists to have no footers in outgoing mail. Otherwise,
incoming messages with HTML cause the footer to be appended as an
a
jsmith wrote:
I have sent a post similar to this previously but it has been a while.
At home I am using outlook.
Content-Type: text/plain; charset="UTF-8"
Content-Language: en
jsmith,
Here's your problem. This email is flagged as using the UTF-8 character
set (Unicode).
I'll guess your list
On Saturday, August 23, 2003, at 10:19 AM, Ares Liu wrote:
When I use chinese subject, mailman 2.1 will get an error as follow:
LookupError: unknown encoding: gb2312
How to solve this error?
Make sure you have the Chinese codecs for Python installed. You can
get them from:
http://sourceforge.ne
chris weisiger wrote:
i didnt know if there was a way to test mailman to detect the nimda
virus...since there was a tests folder...
ive been trying to google for information but i havent come across
anything really about testing...
Mailman cannot detect email viruses. You can use an external
chris weisiger wrote:
i noticed the nimda test virus in the Mailman tar.gz file
how do i test Mailman using the nimda test file?
That file is actually only in the Mailman source code as a way to
exercise the email parser package's MIME handling code; Nimda virus
emails have particularly bad MI
Bausch, Jean wrote:
I have now found who swallows the Umlauts in message bodies:
I had inserted a 'fmt -s -w 80' in the mail aliases. Unfortunately on Solaris 7 this command erases the Umlauts.
Interesting. You can try changing that to
LANG=de_DE fmt -s -w 80
to make sure Solaris can handle
CodyG wrote:
You're right! It is something in the mail client that isn't showing the
footers! Cause for sure they are there in the message source. (I should have
checked.)
So, what is the use of footers if someone using OE defaults doesn't see
them? But how could it be a mailer issue, when the fo
Matthias Juchem wrote:
When sending an absolute normal e-mail (simply one word in the subject and
one word in the body) to both servers, the older one distributes it fine. The
newer one generates a MIME attachment that includes the body content.
Sounds like the list is set for one language,
Sebastian Talmon wrote:
I'm sorry, but with this path the headers are set correct, but
MS Outlook still shows the footer as a pseudo-Attachement
(giving it the name ATT00010.txt or so)
Then it's definitely an MS Outlook bug, and there's not a whole lot we
can do until Mailman gets fully inte
Sebastian Talmon wrote:
* Ben Gertzfield <[EMAIL PROTECTED]> wrote
Are there really so many people out there who are using
non-MIME-compliant mail readers that this is necessary?
yes, there are some people out there using MS Outlook or so...
there the footer is not shown in the messag
Sebastian Talmon wrote:
I think a good solution for this would be, to do just the
same as with the us-ascii-footer on this list:
to switch the whole message to the 'higher' charset and then
integrate the footer as normal...
For a us-ascii-Message it should be no problem to have a
ISO-8859-1-Char
Sebastian Talmon wrote:
on my lists (Mailman 2.1, language: DE) I have the problem that:
- if the user send with charset="iso-8859-1" anything is fine
- if user sends with charset=us-ascii (some mailers do if there
are no german umlauts) then the footer from the mailinglist
gets attached an
Sam Li wrote:
Hello,
I am wondering if mailman support unicode in Subject for showing
Chinese character?
Mailman 2.1 beta supports both Traditional Chinese (big5 encoding) and
Simplified Chinese (gb2312) in the web and email interfaces.
The pipermail web archiver that comes with Mailman 2.
On Tuesday, April 16, 2002, at 12:44 , Richard Barrett wrote:
> Surely, if you are using the built-in pipermail archiver, you can also
> set a list's archive to private on the Archive Options web GUI admin
> page. The list archives are then not available through the /pipermail/
> URI path elem
On Monday, April 15, 2002, at 11:30 , Timothy Murphy wrote:
> While I am an enthusiastic user of mailman,
> doesn't majordomo still have a well-defined usage,
> for essentially private lists like committee minutes?
>
> This is a genuine question --
> am I right in assuming that mailman lists are
On Saturday, April 6, 2002, at 03:53 , Bill Wagner wrote:
> When passing mail through qmail-to-mailman.py, lines 87 and 88 point to
> $prefix/mail/wrapper. I've done plenty of test installs of 2.1b1, but
> in
> none ofthem is there ever a $prefix/mail/wrapper.
This has been fixed in CVS, I bel
> "James" == James Madill <[EMAIL PROTECTED]> writes:
James> Users of one of my mailing lists got a nasty surprise when
James> a posted message was repeatedly sent to them.
James> I traced the problem down to an instance of the standard
James> End-Of-Message marker (a lone pe
22 matches
Mail list logo
