Hi,
> I've seen a increase in use of Unicod'ed email address which fail
> HyperArch email obscuring and thus cause the msg to be shunted and not
> archived.
>
> Specifically the problem lies in the encoding (strangely the error says
> "Decode") of the text ' at ' (as a substitute for "@") for
Mark Sapiro wrote:
> All you have to do is change it to
> if bodylen/1024.0 > mlist.max_message_size:
> rej_msg = 'Message too big: limit = %d KB' %
> mlist.max_message_size
> raise Errors.RejectMessage, rej_msg
That's great, tanks!!!
> Descisions are distributed t
Eric Smith wrote:
>Is there any easy way to get Mailman to reject oversize messages,
>rather than holding them for moderation, or does anyone have a patch?
>I'm really getting sick of dealing with those.
>
>I spent a few minutes looking at whether I could hack it in myself.
>I quickly found the co
Is there any easy way to get Mailman to reject oversize messages,
rather than holding them for moderation, or does anyone have a patch?
I'm really getting sick of dealing with those.
I spent a few minutes looking at whether I could hack it in myself.
I quickly found the code that makes the "hold"
I've seen a increase in use of Unicod'ed email address which fail
HyperArch email obscuring and thus cause the msg to be shunted and not
archived.
Specifically the problem lies in the encoding (strangely the error says
"Decode") of the text ' at ' (as a substitute for "@") for Russian
users of
Keith Daniels wrote:
>
>Two questions:
>
>I set the mailman alias to "mailman: mailman". Is that correct?
No. You want to remove this alias altogether so that the 10 aliases for
mailman, mailman-admin, etc. which are in Mailman's data/aliases will
be effective and not preempted by the /etc/alias
On 11/24/07, Mark Sapiro <[EMAIL PROTECTED]> wrote:
> Keith Daniels wrote:
>
> Did this post go through mailman? What are the full headers? Is ther an
> "X-BeenThere: mailman@com" header and or other mailman
> headers?
>
After looking at your alias question below I realize that -- no, it
was not g
Keith Daniels wrote:
>
>What the mailman list does do:
>
>1 - It receives and sends post to the list
>2 - It saves the web interface configuration changes to the *.pck file
>( I tested this several ways)
>3 - You can create a new list.
>
>What the mailman list does not do:
>
>1 - It does not apply
I am at a total loss. I have run check_perms and then compared all my
directories and their permissions/ownership to the ones I have seen in
the forums and I can see no problems. There are no error entries in
either Mailman's logs or in the apache logs for .com
nor in the postfix logs.
Note: Wh
[EMAIL PROTECTED] wrote:
>
>But when I try to connect to duinheks.xs4all.nl/pipermail/amc-support
>I get a "403: forbidden" error:
>Symbolic link not allowed or link target not accessible:
>/opt/mailman/archives/public/amc-support
>
>What else should I look at?
The information in the 'warning' bo
Hallo,
I created a mailing list using Mailman for the first time and have
a problem accessing the public archives.
The FAQ told me to put the FollowSymLinks option into the httpd.conf.
I did that:
AddDefaultCharSet off
AllowOverride None
Options FollowSymLinks
Order allow,deny
Hello,
> >I get a lot of below errors and worse some of the lists that have been
> >created no longer send out emails. Can you help me troubleshoot it?
> >
> >Thank you!
> >
> >Nov 23 15:06:12 2007 (70462) SHUNTING:
> >1195826769.306325+db3247f3fd9baf0ca519cd58e37b4c1875fc76b3
> >Nov 23 15:06:3
12 matches
Mail list logo
