Date: Tue, 1 Jun 2004 22:30:43 +0200 From: Oliver Fuchs <oliverfuchs@onlinehome.de> To: freebsd-questions@freebsd.org Subject: Re: archivemail-0.6.1 not working as expected Message-ID: <20040601203042.GA2236@oliverfuchs.ath.cx> In-Reply-To: <20040531230813.GD9354@zi025.glhnet.mhn.de> References: <20040531222248.GA2494@oliverfuchs.ath.cx> <20040531230813.GD9354@zi025.glhnet.mhn.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 01 Jun 2004, Simon Barner wrote: > Oliver Fuchs wrote: > > Hi, > >=20 > > I want to use archivemail-0.6.1 (Python 2.3.2) on FreeBSD 5.2.1-RELEA= SE. > > I have three questions/problems with the proper use: > >=20 > > 1) I get the error message: > > /usr/local/bin/archivemail:760: SyntaxWarning: assignment to None > > (None, last_dir) =3D os.path.split(os.path.dirname(message.fp.name)= ) > > I found the answer (Google) and a patch (it is a problem depending=20 > > on Python 2.3). Is there another solution to this problem? >=20 > Update your ports. It's fixed in archivemail-0.6.1_1. Apart from that, > it's only a syntax _warning_ (which of course can be quite annoying if = you > rung archivemail from a cron job and receive an error report every > day), i.e. archivemail works despite of that message. Good advice ... thanx for that ... >=20 > > 2) Running=20 > > archivemail -d90 -o $HOME/Mail/Archive $HOME/Mail/* >=20 > [...] I still have no clue about that >=20 > > 3) I want to run it in a cron job but to be honest I am not quiet sur= e where > > to put my archive script. >=20 > [...] >=20 > You're lucky: >=20 > Several months ago, I did exactly the same thing. You should put the > cron job into your personal cron tab, i.e. as the user who's mail shoul= d > be processed by archivemail, run=20 >=20 > crontab -e Ah ... o.k=20 >=20 > (The other stuff you were looking at were system wide cron jobs). So to make it clear: If I want to run a cron job for a special user I use crontab and otherwise to run a system-wide cron-job that is not defined b= y FreeBSD itself I use /usr/local/etc/periodic? >=20 > Okay, here comes my config: >=20 > From my cron tab (the following line starts my mailexpire script every > day at 19:30) >=20 > 30 19 * * * /home/simon/bin/mailexpire.sh >=20 > ------------------------- >=20 > #!/bin/sh >=20 > # mail boxes to by processed by archive mail > MBOXES=3D"freebsd-ports.box\ > freebsd-questions.box" >=20 > cd /home/simon/Mail; >=20 > # be sure to change the archivemail options to your personal needs > for box in $MBOXES; do > /usr/local/bin/archivemail -d 21 --delete -q $box > done Gr=E6at - thanx for the script >=20 > ------------------------- >=20 > All this works very well for me, although every other day, I get an ema= il > from archivemail that one of my mail boxes changed during its operation. this is only happening on FreeBSD side - I never saw it on Linux before > This shouldn't normally happen, since both archivemail and fetchmail (w= hich > I use to download my email) use several locking mechanisms to insure th= at > only one of them is operating on particular mail box. IIRC the > archivemail man page elaborates more on this. Yes, a little bit skimped > >=20 >=20 > Since archivemail is designed not to trash/loose your mail boxes under = any > circumstances, this was never a problem for me. Anyway, I wouldn't use > archive mail for my personal mail boxes, but only for mailing lists, > where you still have the archives, just in case ... I never saw it from this angle but I am going to consider this >=20 > Cheers, > Simon So thank you again for all your help and work Oliver --=20 ... don't touch the bang bang fruit
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040601203042.GA2236>