That explanation has really helped, but still things aren't clear enough
for me.
So, this is really an implementation of the sieve language by SOGo, but
what executes them is what I still haven't figured out.
If I did these with dovecot, they will be executed with dovecot-lda. Below
are what I have for my dovecot.conf:
```
sieve_script default {
driver = file
path = /var/virtual/domains/sieve/default.sieve
type = default
}
sieve_script before {
driver = file
path = /var/virtual/domains/sieve/after.sieve
type = before
}
sieve_script after {
driver = file
path = /var/virtual/domains/sieve/after.sieve
type = after
}
sieve_script personal {
active_path = /var/virtual/domains/%{user | domain }/%{user | username
}/sieve/default.sieve
driver = file
path = /var/virtual/domains/%{user | domain }/%{user | username }/sieve/
type = personal
}
sieve_script global {
driver = file
path = /var/virtual/domains/sieve/
type = global
}
```
So, if my understanding is correct, I could adjust my sogo.conf as follows:
SOGoSieveScriptHeaderTemplateFile =
"/var/virtual/domains/sieve/after.sieve"; # matching sieve_script before
SOGoSieveScriptFooterTemplateFile =
"/var/virtual/domains/sieve/after.sieve"; # matching sieve_script after
And since SOGo is not involved in mail delivery, but instead invokes the
system's sendmail daemon, I still don't see the use case for SOGo's two
config parameters above.
They are templates. At what point does SOGo use them?
The content of SOGoSieveFilters would be copied to
/var/virtual/domains/%{user | domain }/%{user | username
}/sieve/default.sieve, afterwhich, a user can append their own rules.
This is the only one I seem to see a use case for, but still I am not
succeeding in wrapping my head around this.
My mind is clogged :-(
On Thu, May 8, 2025 at 9:50 AM Christian Mack <[email protected]> wrote:
> Hello
>
> You as administrator can provide sieve scripts in 2 files.
> The one provided by SOGoSieveScriptHeaderTemplateFile will be executed
> before the users sieve scripts.
> The second provided by SOGoSieveScriptFooterTemplateFile will be
> executed after the users sieve scripts.
>
> With those you can do something like filtering Spam or Newsletters into
> special folders.
>
> The difference to having those sieve scripts in the users default config
> is, that those are valid for all users, not just newly created ones, and
> the user can not disable or delete them.
>
> Hope this helps a bit.
>
>
> Kind regards,
> Christian Mack
>
> Am 07.05.25 um 17:58 schrieb Odhiambo Washington ([email protected]):
> > Hello Quentin,
> >
> > Thank you for the response.
> > I am trying to understand the use case of the two file -
> > SOGoSieveScriptHeaderTemplateFile and SOGoSieveScriptFooterTemplateFile -
> > with examples.
> > Please see if you can provide examples. Right now I am just floating.
> >
> > On Wed, May 7, 2025 at 6:31 PM qhivert <[email protected]> wrote:
> >
> >> Hello, it should be at the root of your sogo.conf file like this
> >>
> >> Be aware that will only set the filter for new users and they can change
> >> it in their preferences.
> >>
> >>
> >>
> >> SOGoSieveScriptHeaderTemplateFile and SOGoSieveScriptFooterTemplateFile
> >> values must be the path of the file. The file must contain your scieve
> >> script in UTF8. They can be written at the root of sogo.conf or in your
> >> domain configuration if you have one.
> >>
> >>
> >> Regards,
> >>
> >> --
> >>
> >> Quentin Hivert || Alinto || R&D Lead Developer
> >>
> >> 19 Quai Perrache 69002 Lyon
> >>
> >> www.alinto.com
> >>
> >>
> >>
> >> *From:* [email protected] <[email protected]> *On Behalf Of
> *Odhiambo
> >> Washington
> >> *Sent:* mercredi 7 mai 2025 15:58
> >> *To:* [email protected]
> >> *Subject:* [SOGo] SOGoSieveFilters
> >>
> >>
> >>
> >> In which section of sogo.conf should this one go to?
> >>
> >> I was working on my setup and found this link:
> >> https://www.mail-archive.com/[email protected]/msg33129.html.
> >>
> >>
> >>
> >> Also, are there examples for the two below?
> >>
> >> SOGoSieveScriptHeaderTemplateFile
> >> SOGoSieveScriptFooterTemplateFile
> >>
> >>
> >>
> >> --
> >>
> >> Best regards,
> >> Odhiambo WASHINGTON,
> >> Nairobi,KE
> >> +254 7 3200 0004/+254 7 2274 3223
> >>
> >> In an Internet failure case, the #1 suspect is a constant: DNS.
> >> "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
> >>
> >> [How to ask smart questions:
> >> http://www.catb.org/~esr/faqs/smart-questions.html]
> >>
> >
> >
>
> --
> Christian Mack
> Universität Konstanz
> Kommunikations-, Informations-, Medienzentrum (KIM)
> Abteilung IT-Dienste Forschung, Lehre, Infrastruktur
> 78457 Konstanz
> +49 7531 88-4416
>
>
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
In an Internet failure case, the #1 suspect is a constant: DNS.
"Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
[How to ask smart questions:
http://www.catb.org/~esr/faqs/smart-questions.html]
