>gus wrote:
>
> I am use apache2 in debian , and my question is:
> where I must put the lines of
> Script Alias /cgi-bin/ /usr/lib/cgi-bin
> ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin
See <http://httpd.apache.org/docs/2.0/>
--
Mark Sapiro <[EMAIL PROTECTED
to the
admin mass (un)subscribe function as discussed in the archives of this
list, e.g., the thread beginning at
<http://mail.python.org/pipermail/mailman-users/2004-December/041209.html>.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, California
mberError: exception that resulted from an attempt to
unsubscribe a non-member. This error would not normally occur because
that particular 'post' comes from a member's options page, so the
address would be a member's address.
>At 11:07 AM 11/30/2005, Mark Sapiro wrote:
>>Th
ng a reply-to header (see
><http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.048.htp>
>for why this is strongly discouraged), I don't think you're going to
>be able to "fix" a user problem by making changes on the server.
Also see
<http://www.py
o receive _other_ bounce
messages. There are apparently many non-compliant MTAs in use that
will return a bounced post to the poster rather than to the
listname-bounces address, but these messages will not have the
charastics of an "Uncaught bounce notification".
--
Mark S
on". The original "bounce" appears to be a post erroneously
sent to [EMAIL PROTECTED] instead of [EMAIL PROTECTED]
My question now, is are we sure there isn't some miscommunication
between you, the list owner and the original user? Do we even really
know that the original user (
that says
Date: 2002-05-01 13:57
Sender: marcmerlin
Logged In: YES
user_id=6500
This was rewritten and integrated in mailman 2.1 cvs
If the patch isn't in the tracker, it could still be incorporated, but
it's much less likely.
--
Mark Sapiro <[EMAIL PR
e(1, msg)
-if len(args) < 1:
-usage(1)
-
filename = None
all = False
alllists = False
@@ -134,6 +131,9 @@
elif opt in ('-N', '--noadminack'):
admin_notif = False
+if len(args) < 1 and not (filename and alllists):
+usage(1)
+
-- Marc'
If you tried more than once, the .orig file may not be the actual
original either. See if you can revert to a true base and then try
patching with the patch with no wrapped lines. If you no longer have a
true base, let me know off list and I'll send you everything as
attach
to 'disabled'
(nomail in the admin membership page). Then members in both domains
will be able to post from either, but will only receive at new_domain
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B.
n't had the need
>to post to this list in many months, however, almost every time I have a
>question (95+%) you have had an answer. Kudo's and thanks.
Thank you. OCD is a terrible thing to waste. :-)
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers
cfg.py
which will then place a list deletion link on the list's various admin
pages. If you don't want owners to be able to do it, you could hack
the Mailman/Cgi/rmlist.py script to require a password instead or in
addition, or just create your own CGI based on that script.
--
Mark Sapiro
t then if you
haven't set "OWNERS_CAN_DELETE_THEIR_OWN_LISTS = Yes", you'll get the
"You're being a sneaky list owner!" error, so yes, to use the
unmodified script, you have to set the option.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San
there is no "cc".
Did you try this *before* running configure? I.e. did you rerun
configure after taking /usr/ucb out of the path?
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dyla
list --help"), or you can use bin/config_list run from a
shell script that iterates over all the names in the lists/ directory.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, California
Andy Gao wrote:
>I guess that is the mailman bounce, not specific to the list.
>domain name is not added to mailman-bounce ..
What is the host_name attribute on the General Options page of the
mailman list?
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for g
of what your
problem is and why you want to do this, but I hope I've answered your
question.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
]
address with 'confirm' and the 'token' copied exactly into the subject
of the new mail?
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
-
y for more info.
--
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.org/mailman/l
at mailman serves.
Also see <http://www.list.org/mailman-install/qmail-issues.html>.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailm
come from. Otherwise, they are
sent from the site list bounces address @DEFAULT_EMAIL_HOST.
So in your case, either VIRTUAL_HOSTS_OVERVIEW is off and
DEFAULT_EMAIL_HOST is localhost.localdomain in mm_cfg.py/Defaults.py
or VIRTUAL_HOSTS_OVERVIEW is on and you have at least one list with
members and wit
N_USER=mailman
MAILMAN_GROUP=mailman
Note that it says these should match your --with-mail-gid switch, i.e.
they're not necessarily supposed to be 'mailman'.
Search the FAQ wizard <http://www.python.org/cgi-bin/faqw-mm.py> for
'group mismatch' (simple string,
lar garbled variants with something like
bin/list_members | grep 'likely pattern'
where 'likely pattern is things like 'user' or 'example.com'.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for
Mark Sapiro wrote:
>
>Get a copy of the actual reminder notice which will say something like
>
>Passwords for [EMAIL PROTECTED]:
>
>List Password // URL
>
>[EMAIL PROTECTED]
Moss, Patricia wrote:
>
>If you, or anyone else, has any insight into switching from listserv
>format to mbox format that, too, would be appreciated.
Assuming listserv cannot already export archives in mbox format, see
man formail
--
Mark Sapiro <[EMAIL PROTECTED]> The
hing like 'Hi (Member Name)' at the start of the message body
because under some circumstances, msg_header can be a separate MIME
part. See
<http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.039.htp>.
--
Mark Sapiro <[EMAIL PROTECTED]>
at happens if you interactively give the command
/opt/local/bin/python
and then in response to the '>>>' prompt, type
from compileall import *
If you get an error, something is seriously wrong with your Python
installation.
--
Mark Sapiro <[E
ore information.
>>>> from compileall import *
>>>>
>>>>
>>>> ^D
>isd80{mailman}3:
>isd80{mailman}3:
>
>
>The python complier did not report any errors.
OK. That's good.
>On 12/5/05, Mark Sapiro <[EMAIL PROTECTED]> wrote:
man/Mailman")
Actually, this whole step strictly isn't required as each module will
be compiled when first imported anyway, but pre-compiling will speed
up the initial operation of Mailman a bit.
--
Mark Sapiro <[EMAIL PROTECTED]>
,
defaulting new ones, and then saves it as config.pck. config.pck.last
is the previous config.pck as a backup.
With either method, you'll want to go through the configuration after
conversion and make sure things are OK.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gam
'()' and '[]' in the above is critical - they aren't
interchangeable. The name 'mlist' is literally that (it's used by
config_list). It is not replaced with the list name. The list name is
given as an option to the config_list command as always.
--
Mark Sa
in the
admins-list directory, is there a config.pck and config.pck.last with
ownership and permissions like the ones in mailman and windows?
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
---
Mark Sapiro wrote:
>
>I can't find an address for listas.ipiscmg.rimed.cu in DNS, although
>that probably isn't your problem, it prevents me from trying.
Actually, I see I should have been trying mail.ipiscmg.rimed.cu, but I
couldn't find an address for that in DNS. T
g/cgi-bin/faqw-mm.py?req=show&file=faq03.003.htp>
for some caveats if you've ever edited the listname.mbox files.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
---
y, the sender of the post is the
address in the From: header of the post which is the original poster
unless the all-parents list is anonymous in which case, the From: is
[EMAIL PROTECTED]
If you have set USE_ENVELOPE_SENDER = Yes in mm_cfg.py, then the sender
that's used will be [EMAIL PROTECTED
r to me
whether Mailman is even involved here. Does this message come on
attempt to post that doesn't even reach the list or an attempt to
deliver from the list?
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sen
/ /var/mailman/archives/public/
You also need
Options +FollowSymlinks
To allow symlinks to be followed anywhere in the archives (there is
also one in the monthly archive linking index.html to thread.html).
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Fra
x27;s accept_these_nonmembers, run
bin/withlist --all --run ListMods.del_accept [EMAIL PROTECTED]
You could also define a new_accept(mlist) function to simply assign a
list of addresses to mlist.accept_these_nonmembers analagous to the
new_footer function except with a list of addresses instead of a
mul
ruption in his mailing list cause this? I havent found
> any error that show me what is the exact problem in the logs.
> Anyone had this problem before? any solution?
What do you mean by "going down"? What are the specific symptoms? What
do you do to "br
am not finding
>documentation that can assist me. Can some help me to obtain the
>documentation for this migration? Thanks much.
See
<http://mail.python.org/pipermail/mailman-developers/2005-November/018297.html>
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
S
to me. You're telling
Mailman to send to 2000 recipients in one transaction, and it appears
you're telling the MTA to only accept up to 1000.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Ba
onnections.
I don't think this is correct. Unless there are multiple outgoing
runners processing slices, I don't see how SMTP delivery is
multi-threaded, and even if there are multiple runners, a single
message to even 4000 recipients is going to be processed in its
entirety by one
iles if you
are in doubt about what to delete.
Of course, none of this deals with messages that have already been
delivered to the MTA and are queued there.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B.
(the last entry on the
form). Are you providing either the site password or the special list
creator password (both generated by bin/mmsitepass) in this entry?
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabet
could instead patch the ConfirmUnsubscription method in
Mailman/MailList.py if one wanted to skip confirmations of
unsubscribes from all sources (conditionally by list or not).
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
S
is not.
emailhost depends on the setting of VIRTUAL_HOSTS_OVERVIEW and is
either DEFAULT_EMAIL_HOST or the email host corresponding to the url
host of the create page fron the VIRTUAL_HOSTS dictionary.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay
Paul Williams wrote:
>Mark Sapiro wrote:
>>
>> What Mailman version is this? Current Mailman (2.1.6) is pretty good
>> about weeding out addresses with non-printable ascii characters. In
>> particular, it won't accept whatever characters were displaying as a
&
client waits for the transaction to complete they of course
>you're right.
The client (Mailman) waits for the response to the 'DATA' command for
each chunk. This doesn't mean the mail has been sent, but it has been
accepted and queued within the MTA. How many queues the MTA
Python header file
/usr/local/include/python2.4/Python.h is included in many Python
modules and thus this whole include path was exercised during the
original compile of Python for Solaris 10 (maybe with some other c
compiler).
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for
>archives, all working as they should be. Any suggestions as to why
>the monthly reminders aren't being sent? The initial notices with the
>password when someone subscribes do go out okay.
Is the cron to run cron/mailpasswds at 5 a.m. on the first of the month
(or other time)
very time any list
attribute is changed and saved (i.e. whenever a post is processed or
the admin or admindb interfaces are changed or a member changes
options, etc., etc.), a new config.pck is created with 'standard'
permissions.
--
Mark Sapiro <[EMAIL PROTECTED]> The
ew file that's written - the old one
is only read.
>Is there a way
>to change what it uses as standard permissions?
Only by changing the code in MailList.py.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay
sages look at all
like the above.
If you haven't modified the wrapper, then the mail probably isn't
getting that far and the above message is coming from qmail. Do you
have the appropriate .qmail-cvs, .qmail-cvs-request, etc. alias files?
>--- Below this line is a copy of the mes
bpage")
userdesc is not a valid UserDesc instance for AddMember which is where
things go wrong.
I think you need to do the following in your script.
Add
from Mailman.UserDesc import UserDesc
Remove
class UserDesc: pass
It looks like that's all you need, but I haven't looked too
Ren Bucholz wrote:
>
>Quick question before trying this fix - can I just erase pending.pck,
>or do I need to replace it with a non-corrupted version from another
>list?
You can just remove it. It will be recreated when needed.
--
Mark Sapiro <[EMAIL PROTECTED]>
ourceforge.net/tracker/index.php?func=detail&aid=981188&group_id=103&atid=100103>
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
archives can
be transferred from the old host, but this would require cooperation
and assistance at both ends. Many discussions of the actual process
are in the archives of this list.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, California
l as
well as the owner. See
<http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq06.016.htp>
for more detail on this.
The real issue is bin/check_perms doesn't check aliases.db. This is a
known problem; see
<https://sourceforge.net/tracker/?func=detail&atid=100103&aid
hrough the if - elif to the else
where we call the HyperArch.HyperArchive.processUnixMailbox() method
to add the message to the HTML archive. This apparently fails, but it
is the exact same method called by bin/arch to do the archiving, and
it works when bin/arch calls it.
It seems that this must
Todd Zullinger wrote:
>
>(I'd attach this to the tracker item listed above, but I have no idea
>how to do that from a quick look at the SF site.)
Create an account if necessary and log in (links just left of search
box at top right of pages). Then you will be able to add a comm
ass to set new ones.
--
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.
being archived properly and see if it doesn't
>contain an unquoted From (a line that beings with "From " in the body.
>If you find one, make the line read >From and try the import again.
>I've had this happen to me numerous times when importing old archives.
The script
n and SETGID. Then they should
work no matter how they are run.
The best way is to do as John Dennis suggested and create a SETGID
wrapper to be executed by your PHP scripts. The wrapper would check to
insure it was properly invoked before calling the appropriate bin/*
script.
--
Mark Sapiro <[
# no return
I think all you need to do is replace
hold_for_approval(mlist, msg, msgdata, ImplicitDestination)
with
raise Errors.DiscardMessage
The discard will still be logged in 'vette', but otherwise, the message
will just disappear.
--
Mark Sapiro <[EMAIL PROTECTED]>
hould turn up
a lot more.
One other thing not mentioned in the above post. If the domain names
are different on the new server, you will need to run fix_url after
moving the lists. Run bin/fix_url.py for instructions and see
<http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.02
ly determines who gets the mail, you could set
up a few different input files for bin/config_list to set the
different moderators and run those on a schedule via cron.
You could also just have moderator always go to some forwarding address
and change where that ultimately goes on a schedule via cron
ror.
The exim log looks fine. I think the messages are being delivered just
fine and are in /var/lib/mailman/qfiles/in/, but they aren't being
processed because the queue runners aren't running because of problem
1.
BTW, John Dennis has posted in the past that the FC4 Mailman packag
also links in article 1.11 to other search tools, but there
are no specific instructions for using these with Mailman.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
---
al, then no, there isn't a bin/
script (other than withlist) for changing user options in general.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
n/Handlers/CookHeaders.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-Users@python.org
http://mail.pyth
terface.
If you're running the Apple installed Mailman on OSX server, there is
also some Apple GUI for administering things, but few people on this
list know anything about it.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisc
omain. If this
is a problem, you can rebuild the archives from the
listname.mbox/listname.mbox files with bin/arch. run "bin/arch --help"
for info.
Since Mailman is apparently already running on the new server, you may
not want to copy the site list info (lists/mailman/ or whatever t
xclude
owners from some notices if there are moderators, but Mailman does not
currently do that.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
M
pers as group 'www'.
What may change is the effective group set via the SETGID bit and the
group ownership of the wrapper, but the wrapper doesn't check these
things, so no recompilation of the wrapper should be necessary. Just
make sure that the wrappers' group is the one that
Robert Haack wrote:
>I'm working on a procedure to change the number of recipients in lists.
>Following a sample Mark Sapiro (Thank You Mark) I created the below
>procedure. When I run it though I a bunch of errors. Being that I know
>nothing about Python I was hoping that on
ceived from someone else, as the Bcc will normally
have been removed.
Although the RFC declines to address the operation of automatic reply
commands, I note that this is in the area of which destination
addresses might be included in the reply. I don't thing it
contemplates substituting Sender
we disable him to receive the message from our list.
>
>I just wonder if there's other solution to this kind of problem?
I think the FAQ pretty much covers it. If you come up with anything
additional, please add it to the FAQ.
--
Mark Sapiro <[EMAIL PROTECTED]> The high
if you ultimately plan to do it for all lists. It comes down to
whether it's easier to write a python script to do the change via
withlist vs. a shell or other script to run config_list for all lists.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamble
pe mail to the mailman mail wrapper before trying normal delivery
for this host.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Use
Author
>format.
>Is there a way to see it in the Subject - Author - Datestamp format ?
There's a patch for this at
<http://sourceforge.net/tracker/index.php?func=detail&aid=1290317&group_id=103&atid=300103>
--
Mark Sapiro <[EMAIL PROTECTED]> The highway i
qw-mm.py?req=show&file=faq04.039.htp>
--
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
g ('bin/mailmanctl stop' to stop it if it is),
remove everything from Mailman's locks/ directory. That will clear the
locks and maybe the rest of the update can proceed.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francis
omething about "post-rewriting"
>URLs in the archive, but can't find the post again.
Run bin/fix_url.py for instruction on how to update your pre-existing
lists.
This is covered in at least two FAQ entries. For example, go to
<http://www.python.org/cgi-bin/faqw-mm.py> an
All confirmations including confirmation (acceptance) of invitations
expire as set by the Defaults.py/mm_cfg.py setting
PENDING_REQUEST_LIFE which defaults to 3 days.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, California
e normal mailman functions in that directory work fine, just the ones
>added by the htdig integration come up not found.
>
>I'd love to get this to work. Any suggestions?
Have you modified the patches in any way? In particular, have you
replaced 'mmsearch' with 'htse
th
>99% of use.
Which specific qrunner process is it that's looping and won't die.
Whichever one it is, the queue that it processes is probably the one
that is causing the problem.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay A
d process the queue entry and
another runner has dequeued it. It is likely that you did a
'mailmanctl -s start' when mailman was still running and got two sets
of qrunners running at once.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Are
The outgoing mail
server has dropped the SMTP connection.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailm
ound this by finding the offending
message and editing the digest.mbox, or see
<http://cvs.sourceforge.net/viewcvs.py/mailman/mailman/Mailman/Handlers/Scrubber.py?r1=2.18.2.12&r2=2.18.2.13>
for a fix.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay
John Poltorak wrote:
>On Sat, Dec 17, 2005 at 10:18:27AM -0800, Mark Sapiro wrote:
>>
>> All confirmations including confirmation (acceptance) of invitations
>> expire as set by the Defaults.py/mm_cfg.py setting
>> PENDING_REQUEST_LIFE which defaults to 3 days.
>
; the mailman jobs.
>
> What can be wrong with my setup?
The installation manual assumes you'll use cron.
fcron by default runs commands using the user's login shell from
/etc/passwd. Thus you have to either specify a valid shell in
/etc/passwd or override it by assigning
u run bin/check_perms on the upgraded installation?
--
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.o
fcrontab, but USER may not. Every other environment
assignments defined in the user fcrontab are then made, and the
command is executed.
Note the word 'always'. This suggests that you need
SHELL = /bin/sh
preceding any commands in the fcrontab entry itself.
--
Mark Sapiro <[EMA
27;nn pending requests' messages, are these being
mailed from the old installation?
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
y_gzip run daily at different times, and
mailpasswds runs monthly. Do any of these run successfully? Do any
crons for any user run successfully?
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
-
ilman/listinfo
which you have in your global configuration and which redirects
http://lists.tblc.org/mailman to the listinfo page. If you want to
redirect http://lists.tbls.org/ to the listinfo page, you could try
RedirectMatch ^[/]+$ http://lists.tblc.org/mailman/listinfo
--
Mark Sapiro <[E
Y - %H:%M:%S",date)
date = CGIescape(date, self.lang)
If you change
date = time.gmtime(date)
to
date = time.localtime(date)
you'll get local time.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area
ile=faq04.048.htp>
for more detailed info about where edited templates go.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
hings. Assuming DEFAULT_EMAIL_HOST is not 'snoopy.tblc.org'
either the host name part of the web_page_url attribute of the bentest
list when looked up in the VIRTUAL_HOSTS dictionary (add_virtualhost)
returns 'snoopy.tblc.org' or your outgoing MTA is changing the domain
for the outsi
people have saved or
posted in messages.
--
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
801 - 900 of 14817 matches
Mail list logo
