Thanks for answering my questions.
The automatic function looks like it worked as last night as it uploaded everything to the S3 archive.
However when I run tellmail la_transfer I still receive the same error..
NA.log simply states this when the command is run.
30 08:41:45.00:-1407514880: s3_list_path: failed with s3ret2: 403 Forbidden
The S3.log I'll send along to support shortly as it posts the key/secret in the log.
--
Steven Kenney
WaveDirect Telecommunications
http://www.wavedirect.net
(519)737-WAVE (9283)
From: "Surgemail Support" <surgemailHIDDEN@t@netwinsite.com>
To: surgemail-liHIDDEN@insite.com
Sent: Monday, August 29, 2016 5:57:13 PM
Subject: Re: [SurgeMail List] Legal Archive
On 30/08/2016 8:06 a.m., Steven wrote:
v7.1e-1
I've enabled the legal archive and made sure the
connectivity to S3 is working. I ran a test successfully.
However when I run tellmail la_transfer
manually it does spit back an error:
s3_list_path: failed with s3ret2: 403 Forbidden
which doesn't show up in any error list even via Google.
Send me s3.log and na.log after attempting this. and surgemail.ini
It can't be an access issue because Surgemail was able to
write the test.dat file to the directory.
The other issue is that it is still demanding I have a
local path for the data. My goal was not to triple the size
of our storage. I wanted the archive to be sent to S3 and
only held locally temporarily. Will the data be held in the
specified folder by temporary?
Yes it needs a local cache to build up data blocks before it sends
them.
So I did set up a local backup archive directory with
permissions for the
mail server to write.
Will it purge the data daily/weekly? Or hold it
permanently?
Yes it purges it daily, it keeps the indexes.
The setting: "Time to keep archive, e.g. 5 years or 3
months " is that locally or remote stored data?
Also some typo's and errors on the GUI page:
Thanks I'll fix that.
ChrisP.
1)
Path for local storage (Estimated annual use 1.9e+02gb) (It
keeps changing and not giving me an actual number.)
2)
In round
figures, $5/month plus $0.50 per Gig per month. Here is a
very very rough estimate based on storing current incoming
data for 1 year, 2429MB per day, 8.9e+02Gig per year =
$4.5e+02/month . (Based on sample over the last 0 minutes)
3)
Encryption Password, REQUIRED! (if you loose
this all your archives will be permantently lost - write it
down NOW)
Please correct spelling for loose to
lose, and permantently to permanently
Thanks!