Nethserver-piler needs your tests

Development
41

hum I recall something like this mybe in my test

42

https://wiki.nethserver.org/doku.php?id=module:piler

2 Likes
43

Nice progress :slight_smile:

1 Like
44

Thank a lot for you help, Let’s break it to improve it. I have some others things on the stove, but I am still available

1 Like
45

I’ll give it a try on the weekend, and keep you posted.

1 Like
46

I’ve managed to deploy piler based on the steps described in the wiki, and it went smoothly. Great work, Stephane!

I’ll write a blog entry that Nethserver supports piler.

4 Likes
47

yeahhhhh

3 Likes
48

This is the blog entry: https://mailpiler.com/running-piler-on-nethserver/
Let me know if there’s something to add, clarify or fix.

5 Likes
49

Beer for two? If is suits your taste


2 Likes
50

Not quite, but I appreciate your intention :slight_smile:

2 Likes
51

hello,
can i install piler in a second NS server ? the first one is doing mail jobs but has a small disk


52

Designed to be on a host with the email stack, we could think to do differently but the container cannot use the smtp ports, we have to create container which listen on custom ports and do a BCC to the remote host

In term of security I see benefits, however this needs some works, it is not possible to get another drive and use a mount to the /var/lib/docker

53

I installed piler today. It seems to be a no-brainer. Many thanks to @stephdl with support from @jsuto creating this package.

One question to @jsuto: Is there an overview somewhere to compare the Enterprise and Community versions?

best regards, Marko

2 Likes
54

Something found: https://www.mailpiler.org/wiki/current:comparison-to-enterprise-edition

1 Like
55

A new experience with multiple mail domains:
So far piler only forwards mails addressed to the main domain to the archive.
Wouldn’t it be a better solution to define the forwarding in the settings generally and for all domains?

image
image1220×386 30.4 KB

Otherwise, the forwarding would have to be configured manually at each mail domain. You have to come up with this first, there is nothing about it in the documentation.

1 Like
56

On holiday right now and only a smartphone in my hand, lets talk next week and surely ping me if I forget

57

IIUC you want to use one BCC to avoid to set the BCC in each email domains. Do I am right ?

Reading the documentation

The address will be the same for each domain archive@piler.domain.org where domain.org is your first created domain.

So your request should be workable

58

I have two mail domains configured.
mydomain1.de is the main Domain with mail.mydomain1.de and the same RDNS.
mydomain2.de an additional mail domain.

Thats why I configured:

db domains setprop mydomain1.de AlwaysBccAddress archive@piler.mydomain1.de AlwaysBccStatus enabled

signal-event domain-modify mydomain1.de

After that I noticed that not all mails were archived.
So I repeated the procedure for the 2nd domain.

db domains setprop mydomain2.de AlwaysBccAddress archive@piler.mydomain1.de AlwaysBccStatus enabled

signal-event domain-modify mydomain2.de

Now are all mails are archived.

My suggestion was to use the email settings to forward all mail to the piler archive and save the need for multiple configuration.

The address will be the same for each domain archive@piler.domain.org where domain.org is your first created domain.


was not enaugh.

1 Like
59

maybe you are right, I thought that to use the same archive@piler.firstdomain.org was enough, but we probably need to set it individually ???

https://www.mailpiler.org/wiki/current:post-install?s[]=*config&s[]=site&s[]=php*

How does it works, does the email of the two domains are sent to the archive ?

60

yes ist works

1 Like