Had some heartburn trying to code if mm_cfg.attach_filter does not exist leave it
alone, never quit got it, but The code is tested
and working.
MJM
in mm_cfg.py
attach_filter = ['image/bmp', 'image/jpeg', 'image/tiff', 'image/gif', 'image/png',
'image/pjpeg', 'image/x-png', 'image/x-wmf']
In
Barry -- Nigel M. suggested a couple of tweaks to README.EXIM on
exim-users; here's the patch. Not tested yet.
--- README.EXIM 15 Oct 2002 22:14:16 - 2.5
+++ README.EXIM 16 Oct 2002 14:01:23 -
@@ -26,10 +26,10 @@
The drawback of this configuration is that it will work poorly on
sy
Patches item #624112, was opened at 2002-10-16 14:05
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=624112&group_id=103
Category: mail delivery
Group: Mailman 2.0.x
Status: Open
Resolution: None
Priority: 5
Submitted By: Marcin Deranek (marcin_deranek)
I just updated to the latest CVS version, turned on personalization and
subscribed a bunch of people. I got an "Uncaught Bounce Notification" back,
but as far as I can tell, there was no personalization on the reply-to
address going out.
I put this in my mm_cfg.py:
VERP_PASSWORD_REMINDERS = 1
VE
I'm using Mailman 2.1b+, from a CVS build earlier today.
I sent a batch of messages out, and got a dozen bounces. Each one was
forwarded to me as "uncaught", but the reply-to had the verp'd address in
it.
An example bounce to: address is
[EMAIL PROTECTED]
Is the bounce detector simply not coded
Barry, why is mailman encoding the subject line when it doesn't have to?
In-Reply-To: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: =?iso-8859-1?q?10/19_game_moved_to_1pm=2E=2E=2E?=
X-BeenThere: [EMAIL PROTECTED]
X-Mailman-Version: 2.1b3+
Precedence: l
Chuq Von Rospach wrote:
> Barry, why is mailman encoding the subject line when it doesn't have to?
>
> Subject: =?iso-8859-1?q?10/19_game_moved_to_1pm=2E=2E=2E?=
This is a message that came from outside? How are you sure that it
wasn't encoded in the first place?
Mailman doesn't (as far as
On Wednesday, October 16, 2002, at 02:59 PM, Ben Gertzfield wrote:
> This is a message that came from outside? How are you sure that it
> wasn't encoded in the first place?
as far as I know, it wasn't.
went and checked. here's the subject for that message as it is in the
mbox format file
FYI, I just sent a test.
Subject: =?iso-8859-1?q?test=2C_one_two?=
*I* definitely didn't encode in 8859 going out, but it came back that
way. the body is still in us-ascii, so this is something specific to
the subject line, and it seems to be turned on when I turn on
personalization.
--
> "CVR" == Chuq Von Rospach <[EMAIL PROTECTED]> writes:
CVR> not 8859. So Mailman is making that change to the subject
CVR> line. I believe it started when I turned on personalization
CVR> last night after I did the latest CVS update with Barry's
CVR> fixes. Don't know if it
Hi all,
Does anyone know if there is a patch, a HOW-TO, or something that explains
how to integrate MHonArc with Mailman? I've checked the archives of the
users and developers lists as well as the FAQs at http://www.list.org/ and
http://www.python.org/cgi-bin/faqw-mm.py. At the latter FAQ , I fou
On Wednesday, October 16, 2002, at 04:00 PM, Barry A. Warsaw wrote:
> bin/config_list -o - mylist | grep subject_prefix
subject_prefix = ''
It's happening on all of my lists, FWIW. And I don't think it's
sendmail, because the subject isn't encoded when I receive it, but it
seems to be enco
On Wednesday, October 16, 2002, at 04:00 PM, Barry A. Warsaw wrote:
>
> to an English list, where the user has English as their language. The
> Subject comes through unencoded.
>
Stupid comment: are you sure? Because I didn't know this until a user
using an explicitly non-MIME mailer wrote t
On 10/16/02 7:10 PM, "Chuq Von Rospach" <[EMAIL PROTECTED]> wrote:
> Stupid comment: are you sure? Because I didn't know this until a user
> using an explicitly non-MIME mailer wrote to complain, and I started
> looking at email in "raw source" mode. All I see is the subject line
> looking just f
On Wednesday, October 16, 2002, at 04:20 PM, Stonewall Ballard wrote:
> I've had a couple mailings go out today after I converted to
> personalized,
> and I'm not seeing this (in raw mode).
>
weird. Barry, if you want my full mm_cfi and a config_list to see how
I'm set up, let me know.
--
Chuq Von Rospach wrote:
>
> Barry, why is mailman encoding the subject line when it doesn't have to?
Why? because the recipient prefers it.
The member has set his preferred language as non-english.
You will see this on a non-personalized list if it's language
has set non-english.
The subject
Tokio Kikuchi wrote:
> May be email should not encode the header if the string doesn't
> contain non-ascii charcter.
What happens to iso-2022-jp strings, then? :) They have no non-ascii
characters. (Here we go again..)
Ben
___
Mailman-Developers
On Wednesday, October 16, 2002, at 05:07 PM, Tokio Kikuchi wrote:
>
> Chuq Von Rospach wrote:
>> Barry, why is mailman encoding the subject line when it doesn't have
>> to?
>
> Why? because the recipient prefers it.
>
> The member has set his preferred language as non-english.
> You will see t
Ben Gertzfield wrote:
> Tokio Kikuchi wrote:
>
>> May be email should not encode the header if the string doesn't
>> contain non-ascii charcter.
>
>
>
> What happens to iso-2022-jp strings, then? :) They have no non-ascii
> characters. (Here we go again..)
OK. non-ascii-printable characters
>>> Barry, why is mailman encoding the subject line when it doesn't have to?
>>
>>
>> Why? because the recipient prefers it.
>>
>> The member has set his preferred language as non-english.
Some time ago, in CookHeader.py, english is determined to use
'iso-8859-1' because many like to use 8bit ch
What's the downside of qrunner not running each minute?
Would every 10 minutes be less cpu intensive and still generally effective?
What am I trading off?
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listin
21 matches
Mail list logo
