l just silently discard mail they don't like. Thus in
these cases, you won't see a bounce and the recipient won't see the
mail and the ISP may not admit that this has happened. ISPs tend to
think that it's to their advantage to protect their users from spam
even if it means dis
of any
add_virtualhost() ), and VIRTUAL_HOST_OVERVIEW has its default value
of On.
What do you have in Defaults.py/mm_cfg.py for DEFAULT_URL_HOST,
DEFAULT_EMAIL_HOST and add_virtualhost()?
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californi
005-July/045749.html
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python
te and just post URLs to the list.
If the attached file problem is because posts with attached files are
too big, see the previous paragraph. If it is because the attachments
are being stripped out, see the list's Content filtering page or
discuss this with the list owner.
--
Mark Sapiro
irtual-mailman'
files and run postalias and postmap.
Also, you don't say, and it has nothing to do with the problem, but if
you want the new mail domain for lists created prior to changing
mm_cfg.py, you need to manually change host_name on the General
Options page for those lists or ru
MTA (postfix) configuration issue.
>I have in mm_cfg.py domain.com as e-mail address for the server.
>
>I am using Kolab 2 and postfix as e-mail setup.
Or maybe it's a Kolab 2/postfix issue. I don't think it's Mailman.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway
a list header or footer? I suppose there might be some spam
filter reason if that is in fact the setup, but anyway, there's no
header/footer replacement variable for the sender.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiab
://mail.python.org/pipermail/mailman-users/2005-October/047082.html
for a little more detail and the above mentioned patch.
Also search this list's archives for things like 'external mail server'
and 'fetchmail'.
>Searchable Archives: http://www.mail-archive.com/mailman-u
hat provides list services.
One more thing you might consider which I think works well for some is
if you are willing to have your lists in a separate domain from your
main email domain, you can run an MTA on your Mailman host just for
the lists.
--
Mark Sapiro <[EMAIL PROTECTED]>
JOSEPH DAMICO wrote:
>Now, I see no error messages, but the notes I post to the list are ending up
>in the "shunt" queue.
>
>Any idea what I'm doing wrong here?
No, but there should be a detailed error report in Mailman's error log
for each shunted message.
-
ot;shunt" queue.
>
Actually, running from the group that the wrapper expects should be
sufficient. The fact that it wasn't indicates you still have
permission problems in your Mailman hierarchy. Run
bin/check_perms
as root. If there are errors, run
bin/check_perms -f
until they
er's icons) and that
IMAGE_LOGOS specifies the correct base path of the directory or a path
which is aliased to the directory.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
---
ist"
Mailman then calls the POSTFIX_ALIAS_CMD which in your case is the
default '/usr/sbin/postalias' to update the aliases.db file. It is
these aliases together with the above alias_maps in the postfix config
that tell postfix how to deliver to 'list'.
In your c
??
>>
>> See http://www.list.org/mailman-install/node12.html and subordinates.
>> If you still can't figure it out, try a postfix support list. This is
>> not a Mailman problem. The mail never gets to Mailman.
>I was on this site already. Seems kind of outdated? or M
Also, see the FAQ
>Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Articles 1.22 and 1.23, and search the archives of this list (see FAQ
1.18). This question has been answered many times on this list.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Fra
't want users to be able to post to the list at all, go to
the FAQ wizard
>Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
and search for one-way or announcement or newsletter which will find
Article 3.11 which will tell you how to set it up.
--
Mark Sapiro <[EMAIL PROTECTED]>
ngDomain.py) to do it and insert the new handler at
the beginning of the pipeline with something like
GLOBAL_PIPELINE.insert(0, 'MungDomain')
in mm_cfg.py. This won't work for any list which has a 'pipeline'
attribute, but that is rare.
--
Mark Sapiro <[EMAIL PROT
t_destination on Privacy options...->Recipient filters
or post with an Approved: header, or the post will be held for
approval.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter
27;reply' to reply to the poster and 'reply all' to reply to the poster
and the list.
2) prevent your list members from posting at all by setting up the list
as described in the FAQ.
At the risk of flogging a dead horse, you can't PREVENT your users from
addressing replies to the l
Mark Sapiro wrote:
>
>If you don't want this, and you DO want to allow list members in
>general to post, then you have to arrange for the list posting address
>to NOT appear in the To: or Cc: headers of the posts which you CAN NOT
>do.
Not quite correct. You can post by addres
t need 3). 1) never hurts.
Reputable search engine robots will honor these. Spambots probably
won't.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
-
Mark Sapiro wrote:
>
>2)You can configure your web server to add a
>
>Robots: noindex,nofollow
>
>header when it delivers the pages.
>
>3)You can edit the various arch*.html and article.html templates to add
>a
>
>
>
>tag. See
>http://www.python.org/cgi-
do reply all, and the reply is addressed to the list and to the
explicit reply-to address and to any other addresses that were in the
To: an Cc: of the received post (except perhaps their own).
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Ca
you don't actually see this output, just
except Errors.MMSubscribeNeedsConfirmation:
pass
to the excepts following the try: of the AddMember call. You probably
want to also handle the Errors.MMNeedApproval exception in case you do
this on a list where subscription re
One other thing that hasn't been mentioned, but all the answers in this
thread apply to replies to non-digest messages. Digests always have
Reply-To: the list posting address.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, California
Mark Sapiro wrote:
>David wrote:
> >
> >One more thing. If people are on moderation is there some place to set
> >it that they dont get notification of being moderated and their message
> >is just held without them knowing it.
>
>
>No. If member_moderation_act
ST and maybe DEFAULT_URL_HOST are wrong.
>So my two questions :
>1) How to create a valid Mailing List Email Adress,
See above.
>2) Does it comme from "postfix" => "/etc/postfix/main.cf" file bad configured
> o
If I create this user (# adduser starinux) only the account "[EMAIL PROTECTED]"
>receives the mail.
This is a problem with aliases or with your postfix configuration. You
should not have a local user starinux.
See http://www.list.org/mailman-install/node12.html and it's
subordina
/cgi-bin/faqw-mm.py?req=show&file=faq03.060.htp
As far as the notices of new subscribers and the disabling is
concerned, it seems that mailman can't successfully mail to the owner
address or to the matching member address. What does the copy of the
bounce in the disable notification say? And
es will never
disable/unsubscribe a member because only one bounce is scored per day
and yesterday's bounce is always stale. This seems a little lenient,
but may in fact be OK
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californi
f, but the
alias is better.
Also, on the subscription options for the [EMAIL PROTECTED] subscription
to the main list, be sure to set "Get password reminder email for this
list?" to No.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay
ion: 2.1.6
>> >Sender: [EMAIL PROTECTED]
>> >Errors-To: [EMAIL PROTECTED]
>> >
>> >bhavsar <[EMAIL PROTECTED]> has been successfully subscribed to
>> >Woodlake_el_school.
This message looks very suspicious (i.e.faked). What do you see in
Eudora if y
for the list?
If you have access to Mailman's bounce log, what's there associated
with this address?
I guess it is possible that there is some wierd alias loop causing
this, but I can't think how. I only say that because the member's user
name is apparently the same as the l
t system with Mailman 2.1.6. Thanks to your
description of the triggering conditions, I can duplicate the problem.
It will be a few days before I have time to look at this further, but
I'll report what I find to the list.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is
and
the relevant directories and symlinks in archives/private and
archives/public.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Use
-]
admin(pid): [- Traceback --]
followed by the traceback.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing
o create a lock
file.
It appears that the crontab belongs to you (antoine). It needs to be
installed as 'mailman' so it runs as group 'mailman'.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your s
the right
command file (if not, set it in mm_cfg.py.).
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Us
later, etc. until all are gone? We want to leave a 50 e-mail margin for
>error, and so we can still send ordinary mail in the hours after a mailout.)
No, there's nothing in Mailman to do that. You could modify
Mailman/Handlers/SMTPDirect.py to do it, but it's not currently any
kind of
. Look for error log entries at these times. Most likely, these
SIGTERM signals were generated externally, either automatically by the
OS because of some OS limit or other condition, or by some other
process (maybe manually invoked).
There may be further information in some OS log.
--
Mark Sapir
the passwords - using
the mlist.getMemberPassword(member) method - and produce something
which can be easily processed in a shell script to make an
AuthUserFile file which you would reference from a .htaccess file.
Or you could probably make a single Python script to create the
AuthUserFile file directly.
--
Mar
$1 [L,R]
Of course the one big issue I see is the following. Can you access
www.host.domain from your side of the router? If not, then you have a
problem and probably the best you can do is set VIRTUAL_HOST_OVERVIEW
= Off if that is an option.
--
Mark Sapiro <[EMAIL PROTECTED]>
x27; requires character as left operand
>
>In mm_cfg.py:
>
>DEFAULT_URL_HOST = 'www.univexsystems.com'
>DEFAULT_EMAIL_HOST = 'univexhosting.com'
>MTA = 'Postfix'
>POSTFIX_STYLE_VIRTUAL_DOMAINS = 'univexhosting.com'
POSTFIX_STYLE_VI
der, Reply-To: or Sender: is a
list member.
2) you can open the archive list to anyone by setting Privacy
options...->Sender filters->generic_nonmember_action to Accept. I
don't actually suggest this as it opens the archive to spa
Heather Madrone wrote:
>At 3:28 PM -0800 10/30/05, Mark Sapiro wrote:
>>Heather Madrone wrote:
>>
>>What you need to do is pick one canonical url host and email host and
>>set DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST to those values (probably
>>'www.host.doma
e able to create a list
from the web if you access the create page from this host.
>Anyway, everything seems to be working beautifully. It's been almost too easy
>this time around.
That's great!
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San
re might
be a SetEnv or PassEnv in httpd.conf to set HTTP_HOST to
www.host.domain in all cases.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailm
be different in your case.)
See http://www.list.org/mailman-install/node10.html.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-User
n assignment to LOG_DIR. If there isn't one,
look in Defaults.py in case someone changed it there.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
-
so see Brad's reply in this thread
<http://mail.python.org/pipermail/mailman-users/2005-October/047440.html>.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
antoine wrote:
>
>But how to declare the "cron" job for "mailman" user ?
>
>I type : # cron crontab.in
First do
su mailman
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californ
Mark Sapiro wrote:
>antoine wrote:
>>
>>But how to declare the "cron" job for "mailman" user ?
>>
>>I type : # cron crontab.in
>
>First do
>
>su mailman
The above reply was a bit hasty. It may work in your case, but normally
'
Nov 1 12:49 sitelist.cfg
>
>What am I missing here?
Most likely your lists have host_name attributes different from
'univexhosting.com'.
Run bin/fix_url.py stand alone for instructions on how to run it under
withlist to fix this problem.
--
Mark Sapiro <[EMAIL PROTECTED]>
/2005-October/046934.html
which might have helped.
Anyway, thanks for the report. I have developed a patch for the message
which will make it to SourceForge and into CVS as soon as I have a
chance to compile and test it.
--
Mark Sapiro <[EMAIL
ne list with a host_name matching a name in
POSTFIX_STYLE_VIRTUAL_DOMAINS.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Users@p
In your
case, the From: header value may be [EMAIL PROTECTED]
even thouge the envelope is sent by [EMAIL PROTECTED]
This is just a consequence of the way password reminders are done "by
host". But in any case, running fix_url should solve the problem as
long as the mm_cfg.py stuff is right (
b or
perhaps crontabs installed for mailman in two different ways, e.g.
/var/spool/cron/mailman and /etc/cron.d/mailman?
Whatever the reason, it appears that cron/mailpasswds was run twice.
Either that or maybe you have a "backup" list on another server that
also mailed passwords.
--
lman.
Either Exim on the server with Mailman is not properly configured to
deliver to Mailman, or mail never reaches that Exim although that
doesn't appear to be the case as windfinder.com, www.windfinder.com
and server.windfinder.com all resolve to the same IP address.
--
Mark Sapiro <[EMAIL
PROTECTED], size=0, class=0, nrcpts=0,
>proto=SMTP, daemon=MTA, relay=biwebs1-2 [192.171.196.100]
>Nov 1 13:07:10 biwebs1 sendmail[29973]: [ID 702911 mail.info] alias
>database /etc/mail/aliases.db out of date
Here it is again. I'd say aliases.db hasn't been updated.
>Nov
>scantime=0.0,size=591,mid=<[EMAIL PROTECTED]>,autolearn=failed
>
>Any idea what is going wrong?
It looks like the above is an issue with spamassassin not Mailman. Is
the attempted post rejected by Exim or does it get to Mailman (is
there anything in Mailman's logs or qfiles/*/ direc
ssue is that the above change
only affects new lists. After doing the above, you have to run fix_url
to fix existing lists. See bin/fix_url.py for instructions.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabett
low changing list level
passwords only and not allow the other things the site admin password
allows, you'd have to implement it - it doesn't currently exist.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisc
bscribe: "|/usr/local/mailman/mail/mailman unsubscribe lugnn"
>
>that i must read?
>What it is possible to make?
Your aliases are good. The problem appears to be that Postfix does not
recognize "|/usr/local/mailman/mail/mailman post lugnn" as a pipe and
is trea
lman/private/list_name.mbox/list_name.mbox
regardless of whether or not there is a public link to it. It does
require authorization even if the archive is public.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B.
ions -> msg_header and
msg_footer and the problem goes away, then that is the cause. This is
a limitation as discussed in the FAQ.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiab
trftime('%d-%b-%Y', day +
>(0,)*6))
>Nov 01 09:16:07 2005 qrunner(22015): ValueError : day of year out of range
This is a known problem with Mailman 2.1.5 and Python 2.4. See
http://mail.python.org/pipermail/mailman-user
x27;t there, the list hasn't been accessed
since pre 2.1.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Ma
1 -s
>/var/lib/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s
>/var/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s
>/var/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s
>/var/lib/mailman/bin/qrunner --runner=VirginRunner:0:1 -s
>/var/lib/mailman/bin/qrunner --runner=Re
ion issue. I.e., an
alias of the form
name: "|/path/to/command args"
is trying to redirect mail addressed to [EMAIL PROTECTED] to
"|/path/to/command args"@domain instead of piping it to the command.
You would be more likely to get timely help by using Postfix support
resources ra
t).
Yes. Use the mass subscribe feature on the web interface.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing li
Brad Knowles wrote:
>
> If you're lucky, you may be able to make slight modifications to the
> sample URL that Mark provided, and stumble into wherever your
> provider put the older archive mbox. Otherwise, you may be able to
> re-construct the raw source format archive mbo
orm is a checkbox,
>"Subscribe me to the listserve". I'm trying to get this checkbox to work.
If you don't mind the user receiving the opt-in confirmation, see
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.033.htp
--
Mark Sapiro <[EMAIL PROTECTED]>
t running.
What if anything is in the Mailman log files?
Also see
>Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Article 3.14
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
-
m.py?req=show&file=faq03.009.htp>
for some suggestions as to how.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing
to
>addresses that it can see on the To: and Cc: headers, ...
if they've selected no dupes. It doesn't supress digest delivery since
digests can contain other posts. It works in current versions AFAIK.
(You are addressed in this post. Do you get a duplicate?). This may be
an is
, any dead addresses will
be automatically deleted after a number of days equal to the product
of bounce_you_are_disabled_warnings and
bounce_you_are_disabled_warnings_interval following their initial
disable. You can set bounce_you_are_disabled_warnings to zero if you
want them unsubscribed immedia
e list's General Options
page and A) set send_reminders to No or B) (not quite your 'B') set
umbrella_list to Yes and umbrella_member_suffix to '-owner' (the
default) and all password reminders will be sent to listname-owner
instead of the member.
--
Mark Sapiro <[EMA
JT wrote:
>On 11/03/2005 10:44 PM, Mark Sapiro wrote:
>>
>>Anyone?
>>
>>The only password reminder that should be sent to
>>[EMAIL PROTECTED] is the one for that member, and you can
>>turn off reminders for that member on that member's options pag
tely, the subscriber gets a confirmation message to choose whether
>they want to unsubscribe or not. My goal is to unsubscribe the person from
>the list as soon as their service expires.
>
See the thread in the archives beginning at
<http://mail.python.org/pipermail/mailman-users/2004-Decembe
essages to the list administrator(s).
The rest of this message including attached bounce is snipped.
Why is this message undeliverable to <[EMAIL PROTECTED]>
when the disable notice is delivered successfully to the same address?
The logs will say for sure, but what I see is the envelope se
issue
with the data/ directory as held messages are stored there so it may
need to be shared too.
It may turn out to have too many gotchas, but I wouldn't rule it out
without investigating.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, C
u can find discussed somewhat in the archives
of this and/or the mailman-developers list is to have one live
installation and a second 'hot spare' installation. Then the problem
reduces to just keeping the spare's data current which is more
manageable.
--
Mark Sapiro <[EMAIL PROTEC
Eric Hamburg wrote:
>Is there a way to flag an existing list as inactive?
Not within Mailman per se, but if you give us more detail about what
result you actually want, we may be able to suggest ways to achieve it.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamb
how them
the bounce action notification and my analysis thereof, and ask them
to look into it. At least, they could find the relevant log entries.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your se
not send. Then
>i restart mailman and all mails received are sending.
This seems to indicate that the mail reaches Mailman and is queued, but
there is some problem with one or more of the qrunners. Look at the
Mailman logs 'error' and 'qrunner' to see if qrunners are dyin
osting and other email
access to the list, and replace them when you want to reactivate the
list.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
-
AgustÃn Barahona wrote:
>El Thu, 3 Nov 2005 17:11:44 -0800, Mark Sapiro <[EMAIL PROTECTED]> escribió:
>
>>This is number one under list administration on the wishlist of new
>>features <http://www.list.org/todo.html>.
>
>Thank you. And when is supposed the ne
gabo wrote:
> Mark Sapiro wrote:
>
>> gabo wrote:
>>
>>
>>> I have run mailman with an qmail-ldap server.Once or twice per day,
>>> mailman not delivery mail.
>>> The mails are received in qmail-ldap server and it calls
>>> /var/lib
thon's smtplib can't find your host name or the IP
address for your hostname because it isn't in /etc/hosts or maybe
because of a resolve.conf problem as described in the FAQ.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway
Thomas Spuhler wrote:
>Is there a way to use virtual.db instead of alias.db?
Not instead of - in addition to.
See <http://www.list.org/mailman-install/postfix-virtual.html>.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californi
s is not accepting mail from the host
>>idea5.anoeticconcepts.com since Mailman apparently uses the host name
>>rather than the "preferred domain" for some of its delivery
>>notifications.
I don't think this is the reason, because I thing the me
om list-b to be sure no posts
leak through, and then bin/add_members to add them back the next time.
If you don't have access to the command line, you can script the web
interface to get the members of list-a and mass subscribe them to
list-b. See
<http://starship.python.net/crew/jwt/mailman/
Mark Sapiro wrote:
>It will be a few days before I have time to look at this further, but
>I'll report what I find to the list.
See the post at
<http://mail.python.org/pipermail/mailman-developers/2005-November/018288.html>
for more information on this problem and a tentativ
OMAINS = 'btspuhler.com'
It is a list so even though it is a list of one, it needs to be written
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['btspuhler.com']
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers
il to '[EMAIL PROTECTED]' doesn't work at all,
this is a consequence of the cPanel changes to 'localize' list names
to a domain and has to be addressed by cPanel.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Calif
ust don't work because the site list is
[EMAIL PROTECTED], this is a cPanel problem. See
<http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq06.011.htp>.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter
work.
But, the simple answer to your question if it means what it says on its
face is don't tell them the list admin password, the list creator
password if any and the site password if any.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Fra
es/. The archive ones are
arch*.html and article.html.
After editing the templates, they will only affect new pages. To change
all archive pages for a list or lists, you need
bin/arch --wipe
assuming you have the cumulative
archives/private/.mbox/.mbox file intact.
--
Mark Sapiro <[EMAIL PRO
serves the Mailman pages must either be on the mailman
host machine or it must otherwise have access to the file system that
Mailman is installed on. It doesn't seem that your congiguration meets
this requirement.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San F
ry effective system.
>
>What I don't see is a way to get MM to utilize the headers created by
>the 3 packages.
If you want mailman to deal with it, you can use header_filter_rules to
recognize the headers and act accordingly, but why not just delete the
spam before it gets to mailman?
601 - 700 of 14817 matches
Mail list logo
