1

Topic: Out of Office for alias/forwarding

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.6.1
- Deployed with iRedMail Easy or the downloadable installer? downloadable installler
- Linux/BSD distribution name and version: Ubuntu Server 20.04 LTS
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx):
- Manage mail accounts with iRedAdmin-Pro? No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

Hi,
Is there a way to make Out of Office messages work for alias or forwarding accounts? My accounts are mostly aliases or forwardings (I have tried both) for the department account.
Thank you!

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: Out of Office for alias/forwarding

no, since this works with sieve scripts,  only real mail accounts have the possibility to archive this

3

Re: Out of Office for alias/forwarding

Cthulhu wrote:

no, since this works with sieve scripts,  only real mail accounts have the possibility to archive this

Thank you!

But these are real mail accounts, I can logon in Roudcube and the sieve scripts are in place when the Out Of Office is on... I actually play with the values of is_alias and is_forwarding in the forwardings table...

4

Re: Out of Office for alias/forwarding

If you set the sieve rules for real mail user, the forwarding / alias account should work too.
If not, please turn on debug mode in Dovecot and check the detailed log.

5

Re: Out of Office for alias/forwarding

I have real users but used to set them as alias in mysql tables.

Now I have resorted to having real users (in sql they are forwarding to themselves) and put a sieve rule that redirects all messages to the dept account. also the out-of-office rule redirects all messages to the dept account.

To avoid mail duplication, i put a sieve rule in the dept account to delete all duplicate messages and it seems to work ok for the moment.

Probably not the most elegant solution, but it's easy to do!