Hi Gang,
I've got one mailing list for a customer who wants public archives. The box hosts many sites, and
he wants his domain in the URL for the archives. This isn't a problem for private archives, but
there doesn't seem to be a way to set the URL for public archives.
I recall we hashed this one over a while ago, but was there ever a solution?
Bob
Hi Developers,
I've done backporting the changes in Release_2_1-maint into the MAIN
branch which was not updated more than a year and this has caused
confusion for the people who want to try CVS checkout. For I was a
little bit tired of maintaining two branches (or of the pressure to do
so) I want to check in to the MAIN branch only hereafter, although some
serious security bug fix (if any) should be committed in the 2.1 branch.
I believe the MAIN CVS checkout is now ready to be tested but plese let
me know if you notice something.
Cheers,
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
One more thing: just caught this today, with the current stable release:
in logs/smtp-failure:
smtp-failure:Aug 28 17:28:31 2005 (1433) All recipients refused: {'randiminetor@
highfallsfilmfe...': (501, 'Bad address syntax')}, msgid: <1b89848bfc55965b74421
44bb122ad4d(a)minetor.com>
smtp-failure:Aug 28 17:29:18 2005 (1433) delivery to randiminetor@highfallsfilmf
e... failed with code 501: Bad address syntax
I assume it is abbreviating the email address, because I am certain the sender is using the proper
email address. What might be causing the error?
Bob
I've noticed that when I use a web interface to create or delete a
mailing list, (CGI or my XMLRPC interface), the ownership of my
data/aliases file does not change. However if I use bin/newlist or
bin/rmlist as root, the ownership on data/aliases changes to
root:root. bin/genaliases does not seem to modify the ownership.
After the ownership has changed, the web interface is no longer able
to modify this file. It should be noticed that the permissions do not
change, just the ownership. Other than "don't run it as root" can
someone point me in the right direction to fix this?
I can see why it happens with a remove: the removal happens in a newly
created .tmp file which is then renamed. For a create list operation,
the error crops up during _check_for_virtual_loopaddr. There is a
checkperms function, but it doesn't seem to be called by anything but
bin/check_perms.
--
Joseph Tate
Personal e-mail: jtate AT dragonstrider DOT com
Web: http://www.dragonstrider.com
Hello,
a natural extension of an anonymous list is a pseudonym list:
if the user specifies a pseudonym, then the messages posted by
this user carry this pseudonym in the name section of the From:
field (along with the list email address).
I hacked my mailman 2.1.5 installation to accept pseudonyms
for all anonymous lists. The pseudnym is an additional
component of UserDesc with very similar behavior as the user
name. Users who subscribe through the web to an anonymous
list have the option to specify a pseudonym.
Please look at
http://marx.econ.utah.edu/mailman/listinfo
and feel free to subscribe to the pseud and test lists and
take them through the paces. I need this feature for a class
in the Fall Semester and would like to iron out any bugs.
This feature fits painlessly into the ordinary mailman
interface, and if there is interest I would be happy to
submit the code.
Hans G. Ehrbar
--
Hans G. Ehrbar http://www.econ.utah.edu/~ehrbar ehrbar(a)economics.utah.edu
Economics Department, University of Utah (801) 581 7797 (my office)
1645 Campus Center Dr., Rm 308 (801) 581 7481 (econ office)
Salt Lake City UT 84112-9300 (801) 585 5649 (FAX)
We would like to request that Web Accessibility be added to the Mailman
wishlist.
The Mailman user community includes an increasing number of
individuals. Some have disabilities and rely on adaptive technologies.
Incorporating accessibility would help increase the availability and
accessibility of your software to people of all needs.
It would be great to have Mailman at a minimum meet World Wide Web
Consortium (W3C) Web Content Accessibility Single A Guidelines[1] and
adhere to Section 508[2] of the Americans with Disabilities Act.
There are some simple things that can help. For instance when the end
user views templates like the information page and the user specific
options page they get form fields that are not accessible. Forms are a
problem because the extra accessibility tags are simply not known to
many developers. Forms aren't the easiest of things to use for people
with disabilities. Navigating around a page with written content is one
thing, hopping between form fields and inputting information is
another. Because of this, it is a good idea to add a number of elements
to the form. Most of culprit HTML in question is in the python code.
One of the main things that needs to be done is to associate form
labels explicitly with their controls. Markup for labels needs to have
the <label> tag and for attribute and the corresponding input needs an
id attribute.
Also adding alt attributes to images, using good html heading
structure, and validating [3] to W3C standards would aid accessibility.
If we can be of help in this effort please let us know.
Thank you for your consideration.
Sincerely,
Laura Carlson and the ITSS University of Minnesota Duluth Web Team
http://www.d.umn.edu/itss/about/teams.html#www
[1] http://www.w3.org/TR/WAI-WEBCONTENT/
[2] http://www.access-board.gov/sec508/guide/1194.22.htm
[3] http://validator.w3.org/
___________________________________________
Laura L. Carlson
Information Technology Systems and Services
University of Minnesota Duluth
Duluth, MN 55812-3009
http://www.d.umn.edu/goto/webdesign/
I've noticed of late that emails sent by yahoo users that get relayed
by mailman end-up without the domainkey header entry [1] and thus in
various yahoo users' bulk (ie. spam) folder. Is there anything that
can be done to remedy this issue ? Can a site's mailman application
add a locally qualified domainkey entry header (or keep the original
entry as-is) ? If so, how and/or is there a place I can read more
about this (didn't see any mention in the FAQ).
[1] http://antispam.yahoo.com/domainkeys
Regards,
- Nadim
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
Well, it came back... I was poking around because I was having cron
problems, and some jobs weren't running.. There's nothing in error, but
if you run disabled by hand, you get:
/usr/local/bin/python -S /home/mailman/cron/disabled
Traceback (most recent call last):
File "/home/mailman/cron/disabled", line 220, in ?
main()
File "/home/mailman/cron/disabled", line 204, in main
mlist.sendNextNotification(member)
File "/home/mailman/Mailman/Bouncer.py", line 270, in sendNextNotification
msg['Subject'] = 'confirm ' + info.cookie
/usr/local/bin/python -S /home/mailman/cron/disabled
Traceback (most recent call last):
File "/home/mailman/cron/disabled", line 220, in ?
main()
File "/home/mailman/cron/disabled", line 204, in main
mlist.sendNextNotification(member)
File "/home/mailman/Mailman/Bouncer.py", line 270, in sendNextNotification
msg['Subject'] = 'confirm ' + info.cookie
TypeError: cannot concatenate 'str' and 'NoneType' objects
It worked fine for a while.
Hi,
I think you are right! I have to make warning when checking in because
this may cause incompatible behavior for already installed other
patterns. :-(
Iain Pople wrote:
> Hi,
>
> I have noticed some unexpected behaviour with header_filter_rules.
>
> I wanted to reject messages with an empty subject line so i came up
> with the following regex:
>
> ^subject:\s*$
>
> However it wasn't working as desired. After delving around in the
> SpamDetect.py code i noticed that the re.search call is not using
> MULTILINE mode. So the headers are treated as one long string and ^
> would only match the beginning of the string.
>
> Is this the desired behaviour? To me it makes more sense that it
> should use multiline mode.
>
> i.e.:
>
> --- SpamDetect.py.bak 2005-08-02 15:56:42.083270000 +1000
> +++ SpamDetect.py 2005-08-02 17:33:59.698226000 +1000
> @@ -127,7 +127,7 @@
> for pattern in patterns.splitlines():
> if pattern.startswith('#'):
> continue
> - if re.search(pattern, headers, re.IGNORECASE):
> + if re.search(pattern, headers, re.IGNORECASE|re.MULTILINE):
> if action == mm_cfg.DISCARD:
> raise Errors.DiscardMessage
> if action == mm_cfg.REJECT:
> @@ -137,3 +137,4 @@
> hold_for_approval(mlist, msg, msgdata,
> HeaderMatchHold)
> if action == mm_cfg.ACCEPT:
> return
>
> --
> Iain Pople
> Systems Programmer
> University of Melbourne
>
> ------------------------------------------------------
> Mailman-Users mailing list
> Mailman-Users(a)python.org
> http://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe: http://mail.python.org/mailman/options/mailman-users/tkikuchi%40is.kochi-u.…
>
> Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
>
>
>
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
