Hi everyone...

Quite new to qmail, and just got a qmail/qmail-scanner/clamav/spamassassin going on a PLESK CentOS5 VPS.

Look forward to adding some of these interesting ART features to PLESK!

I needed qmail-scanner mainly for the archiving feature, and now that I have it working, I was wondering if anybody can give me some direction in order to download these emails via POP to an email client? I'd like to back up all emails going in and out of the server off-site and POP sounds like the way forward, as it'll delete files as I download them...

Thanks in advance!

hi,

Did you find a way to do this already?

thanks, Patrick

Its in maildir format, so on a plesk box I just have a job that moves the files into a mailbox plesk manages (and change the permissions!)

Hey Patrick,

Yeah, I did after a little experimenting.

Scott's right. Just move the files from the archives folder into the /new folder of a Maildir email account and change permissions to the delivery agent (e.g. courrier uses popuser)

I wrote a little tutorial here
http://blog.netweblogic.com/linux/mail/email-archive-google-style/
that helps you set up archiving with Gmail, so it pulls it from a new email account!

Ah, now that IS a good solution. Gmail. Genius!

a great bonus is you free up space on a server... great stuff once you have 40 accounts receiving mail all day!

I don't know if you want to change your instructions a bit though?

rather than editing qmail-scanner-queue.py (it is .pl in the Perl version anyway), change /etc/qmail-scanner.ini then run qmail-scanner-reconfigure

I don't know if you are using something different (because of the python .py extension) but in the versions I use ( Perl .pl), every time you run qmail-scanner-reconfigure, it will overwrite the qmail-scanner-queue.pl with the settings from qmail-scanner.ini

Faris.

Edit: Also you might want to change the bash script that copies the messages so that it checks if something new is in the new folder or not, otherwise you'll get a nessage from cron saying it can't copy anything Or you could just add a >/dev/null 2>&1 jobbie to the end of the cron command.

faris, you are very right about the .ini file, thanks for pointing that out. In fact the thought crossed my mind when writing, but twas a late night post and never got round to fixing it!

I suppose you're right on the script too.... considering my server gets an email every few seconds though, it wouldn't be an issue for me but for a tutorial that's a more complete solution...

Thanks