Mailcow-dockerized: Add Piler to archive emails

[phillipplum]

I would like to add the following Docker (https://github.com/heri16/docker-piler-php) and then also configure Postfix so that the e-mails are archived. How do I customize docker-compose and postfix?

Can someone help me? Thanks!

[catcun]

I would love to have piler integrated with mailcow. But I guess it is way out of the scope of mailcow.

[phillipplum]

Yes, i think this too @catcun. But maybe someone can help to integrate it. I'm new with docker compose and I don't know how I have to adjust the network, for example.

[Braintelligence]

Actually servercow is selling piler as optional service to mailcow 😸
I'd understand if @andryyy wouldn't want to implement this special feature into the open-source docker-compose.

[andryyy]

Archiving should be done on dedicated hardware. Besides only a very small number of users who need it, I don't see any good reason to ship it with mailcow on the same machine. If you want it, go ahead and include it into your installations. :-)

Am 30.07.2017 um 14:56 schrieb Braintelligence [e-mail]:

Actually servercow is selling piler as optional service to mailcow 😸
I'd understand if @andryyy wouldn't want to implement this special feature into the open-source docker-compose.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[Braintelligence]

Maybe we could create a chapter in the documentation on how to run a dockerized piler on another machine and connect it to mailcow?

[andryyy]

Sure, go ahead.

[Braintelligence]

Now I only have to read up on piler 😸.

[Braintelligence]

@andryyy I've send you a little "Aufmerksamkeit" for all your hard work 😺.

[kwisatz]

Was any progress made on this? (@Braintelligence ?) If so, could the documentation be updated with that information? If not, I'll have to give it a spin myself.

[andryyy]

Install Piler on another host, add bcc maps, profit. 👍

[kwisatz]

Sounds easy enough ;)

[Braintelligence]

@kwisatz Sorry I didn't have the time to do this yet ☹️ . I'd be very happy to hear about your steps to success on doing this, though!

@andryyy Thanks for the hint! I should try it out on FreeNAS 😸.

[andryyy]

I can create a new install guide.

Am 09.03.2018 um 13:58 schrieb Braintelligence [e-mail]:

@kwisatz Sorry I didn't have the time to do this yet ☹️ . I'd be very happy to hear about your steps to success on doing this, though!

@andryyy Thanks for the hint! I should try it out on FreeNAS 😸.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[ghost]

@andryyy
This is a great idea!

[ghost]

@andryyy
Is there some kind of "How to".
I'm really interested in this ...
Perhaps I can help you writing this install guide?

[lucianlazar1983]

I am too very interested in this, for now i will creaste a separate VM for Mailpiler and modify manually postfix main.cf including: always_bcc = [email protected]
On Piler i would run a cron this way: 01 20 * * * /usr/local/bin/pilerimport –K mailcowserver.com -u bcc@emailaddress -p bccpassword
Would be nice to have it automated somehow...
Any clues?

[ghost]

I would like to ask if there are plans to write an install guide.
As i mentioned before i am very interested in using piler.

[Braintelligence]

@andryyy Is there any progress on this? I'd really like to test this out, but would rather follow your educated knowledge.

[andryyy]

No. It is basically installing Piler and setting up BCC maps in mailcow. :)

[Braintelligence]

Do you recommend running an isolated Piler for each mailcow instance or do you run one for all? And do you rather recommend a bare-metal/vm install or a dockerized install? (Last questions, gonna try it after knowing the answers :P)