> > Do you have any idea what I should
> > do so that more messages are being purged? Especially the retention
> > period seems suspect I think...
> For already archived spam, you should identify them in the metadata
table, eg. check the subject
> field. Then set the retained column for such
Hello,
What is the process/possibility of mass exporting emails (such as if all
emails for a certain domain for years need to be handed off; e.g. 1 million
emails) need to be offloaded and zipped up?
Thank you.
Apologies- I jumped the gun on this request. The pilerexport --help
indicates that -F and -R can be used for a specific domain, which is not
found on http://www.mailpiler.org/wiki/current:exporting-emails (only the
specific email address). Thank you.
On Thu, Sep 26, 2019 at 12:57 PM Ryan Blenis
Hi Janos,
I see the enterprise version you offer it says one of the features piler
has is S3 object storage, which looks like it was originally requested on
the mailing list in 2018:
https://www.mail-archive.com/piler-user@list.acts.hu/msg01335.html
Does this mean that it is fully implemented
? Or would starting back from scratch be the only
option?
Thank you as always again.
On Sun, Apr 5, 2020 at 7:16 AM wrote:
>
> Hello Ryan,
>
> On 2020-04-05 10:55, Ryan Blenis wrote:
> >
> > I see the enterprise version you offer it says one of the features
> >
nd get an enterprise
license anyway. So here's hoping that's the case! I'd love to get rid of
the proprietary options I've got some clients on and move everyone to Piler
if possible.
Thanks again Janos!
On Mon, Apr 6, 2020 at 3:11 AM wrote:
>
> Hello Ryan,
>
> On 2020-04-06 00:45, Ryan
Hello,
Just a question about the table. I took a look at the data, and I've got 23
million rows in there, however I kept seeing id 37 pop up. I queried for
"SELECT COUNT(*) FROM rcpt WHERE id = 37" and got a count of 3,116,977.
I was under the impression (perhaps mistakenly) that the table was
ill get new rcpt rows for id=37?
> I suspect that piler tries to keep processing the very same email.
>
> Janos
>
>
> On 2020-05-02 09:41, Ryan Blenis wrote:
> > Hello,
> >
> > Just a question about the table. I took a look at the data, and I've
> >
Hi Janos,
Quick question on reindexing and its effect on the size of the sphinx files.
If I reindex something that is already in the index, will there be
duplicates in sphinx wasting space, or is this detected and removed?
Background: We weren't searching for anything old normally, so we
Hi Janos,
On Sun, May 2, 2021 at 2:24 AM wrote:
>
>
> Hello Ryan,
>
> On 2021-05-02 01:15, Ryan Blenis wrote:
>
> > 1. Is there a way to have the pilerexport dry run output the number of
> > attachments linked to the query?
>
> Just to clarify. Let's say
Hi again!
Loving the updates to pilerexport since our last chat. A couple questions
for upgrades based on requests I've had:
1. Is there a way to have the pilerexport dry run output the number of
attachments linked to the query?
2. Would it be possible in the web UI to have an "expert"
Hi Janos,
I have to export potentially a ton of emails and was looking to use
pilerexport versus multiple batches of GUI searches. I saw the -w flag and
thought "great, I can use this" but it doesn't seem to respond
appropriately for my test case. I have 2 emails that match the following
x query syslogged. Then re-run the
> pilerexport command, and record the new sphinx query, and compare it
> with the previous value.
>
> Verify that even the single-quotes and double quotes are the same in
> both queries.
>
> Janos SUTO
>
>
> On 2021-04-07 18:18, Ryan Blenis wro
Disregard that last email. Coffee is good, not re-running ./configure after
installing deps is bad. Following up shortly with more pertinent info.
Thank you.
On Wed, Apr 7, 2021 at 3:58 PM Ryan Blenis wrote:
> Hi Janos,
>
> Thanks for the response, in trying to do this (I cloned
ubmit a patch.
When trying to just compile the latest, I get the error "error: cannot
connect to 127.0.0.1:9306" so I'm not sure if that's an issue because not
all the components are upgraded, or if I had a different configure
flag/path configured during the original install.
On W
I should clarify the "error: cannot connect to 127.0.0.1:9306" error
message.
This error does not occur at compile time, but only at runtime of the
latest pilerexport, and only when the -w switch is used.
On Wed, Apr 7, 2021 at 7:36 PM Ryan Blenis wrote:
> Hi Janos,
>
>
can reproduce this
on your end or not.
The odd part is, cfg.mysqluser and cfg.mysqlpwd _IS_ utilized in the
"init_session_data(, );" line above the
"init_session_data(, );" and it passes the database "open" test
just fine there...
Thank you.
On Thu, Apr 8, 2021 at 12:13
17 matches
Mail list logo
