Re: [Zope] Web mail with POP3
If all you need is POP3 mail, you might want to check out http://www.zope.org/Members/dshaw/POPMailProduct. Doug Aleksander Salwa wrote: > > I need to build a web mail product with pop3 back-end. > There is WorldPilot, but AFAIK it has no pop3 support. > I'm thinking about taking web inteface/application design from WorldPilot > and writing code to talk to pop3 server (probably based on POPMail > product). > > Is this a good approach, or someone already has wrote something like this > for Zope ? > > [EMAIL PROTECTED] > > /--\ > | `long long long' is too long for GCC | > \--/ > > ___ > Zope maillist - [EMAIL PROTECTED] > http://lists.zope.org/mailman/listinfo/zope > ** No cross posts or HTML encoding! ** > (Related lists - > http://lists.zope.org/mailman/listinfo/zope-announce > http://lists.zope.org/mailman/listinfo/zope-dev ) ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Version Control in Zope / Managing releases
Shane Hathaway wrote: > > I would say there are simply too many developments happening for anyone to > keep up. I can understand why my little proposal has been overlooked--it > doesn't seem very exciting. :-) There *is* too much going on, but I'm *very* excited by this proposal. Using versions to isolate development from current users is useful but only in a limited fashion. Most environments don't allow development on production servers, and if you're doing serious development you're probably working on the filesystem (at least partially) anyway. We're facing this challenge at ZapMedia, and I had the same problem at WebMD. The solution there was a bit easier because we had fewer developers working on more isolated projects. We have some tools in place for doing releases at ZapMedia, but there's still an uncomfortable feeling because we're all using the same development server. Doug ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] doesn't? Please fix... ;-)
I missed the beginning of this thread, so I'm not sure if this will help. I've attached a patch file which will add a DTML-commentline tag. This is different from the standard DTML-comment in that it does not require an end tag. Here's an example of its use: This segment prints the 'title_or_id' for the current method, and does not execute the loop. Obviously the DTML-in syntax isn't correct, but that's part of how the commentline tag works. It eats up everything in its own <> markers, and allows the DTML parser to ignore it. It *does not* go all the way to the end of the input line, as the name might imply. Doug Chris Withers wrote: > > Andrew Kenneth Milton wrote: > > | What's wrong with that? > > > > It's wrong :-) > > > > > > crap > > more crap > > > > Lots of crap > > > > > > > > In order to parse that fragment, you need to parse the blocks in case you > > find another opening block, so that you can recursively process comments. > > Yeah, fair point... > > > | > It doesn't look difficult to provide what you want, but, I'm not motivated > > | > enough to fix it either at this stage. d8) > > | > > | Aww... go on, you know you want to really ;-) > > > > Now you know the problem domain, it shouldn't be hard for you to create > > a cut-down equivalent of the DT_String parser that only parses comment blocks. > > You obviously have a better understanding of DT_String than me and so > would be much better suited to the task ;-) > > Good luck, we're all rootin' for ya :P > > Chris > > PS: > > Take you less time than writing these emails I'm sure d;) > Er... no! > > ___ > Zope maillist - [EMAIL PROTECTED] > http://lists.zope.org/mailman/listinfo/zope > ** No cross posts or HTML encoding! ** > (Related lists - > http://lists.zope.org/mailman/listinfo/zope-announce > http://lists.zope.org/mailman/listinfo/zope-dev ) Index: DT_String.py === RCS file: /cvs-repository/Zope2/lib/python/DocumentTemplate/DT_String.py,v retrieving revision 1.38 diff -r1.38 DT_String.py 91c91 < from DT_Var import Var, Call, Comment --- > from DT_Var import Var, Call, CommentLine, Comment 143a144 > 'commentline': CommentLine, Index: DT_Var.py === RCS file: /cvs-repository/Zope2/lib/python/DocumentTemplate/DT_Var.py,v retrieving revision 1.36 diff -r1.36 DT_Var.py 448c448 < class Comment: --- > class CommentLine: 462,463c462 < name='comment' < blockContinuations=() --- > name='commentline' 470a470,473 > > class Comment(CommentLine): > name='comment' > blockContinuations=()
Re: [Zope] Odp: [Zope] strategies for starting zope on redhat
I've attached a startup script that I use on my RedHat 6.2
installation. You'll want to change the path /stor/zope/current to the
directory where you have Zope installed. That probably should have been
a variable. The Zope process will be owned as "nobody" so that user
needs write permission to the var directory and its contents to create
PID files and update the Data.fs.
Install the file to /etc/rc.d/init.d as "zope" and then you can use
linuxconf to control whether or not the "zope" service is started when
the system boots.
One other thing -- You have to make sure that the server does not run in
debug mode (by passing -D to z2.py in the start script), or your boot
sequence will hang.
Doug
Bill Anderson wrote:
>
> Adam Karpierz wrote:
> >
> > >Hello
> > >
> > >A friend reports he cannot start zope automatically at boot on his new
> > Linux
> > >RedHat installation, but that it works fine when he does it manually from
> > >shell prompt.
--
Doug Hellmann
Director of Portal Development
ZapMedia.com
678.420.2744
#!/bin/sh
#
# Startup script for the Zope Application Server
#
# chkconfig: 345 85 15
# description: Zope is a web-based Application server.
# processname: z2.py
# pidfile: /stor/zope/current/var/Z2.pid
# config: /stor/zope/current/var/Data.fs
# Source function library.
. /etc/rc.d/init.d/functions
# See how we were called.
case "$1" in
start)
echo -n "Starting zope: "
daemon /stor/zope/current/start
echo
touch /var/lock/subsys/zope
;;
stop)
echo -n "Shutting down zope: "
#killproc httpd
/stor/zope/current/stop
echo
rm -f /var/lock/subsys/zope
rm -f /stor/zope/current/var/Z2.pid
;;
status)
status z2.py
;;
restart)
$0 stop
$0 start
;;
*)
echo "Usage: $0 {start|stop|restart|status}"
exit 1
esac
exit 0
