1

Topic: AWS S3 sync/backup fail because dovecot.sieve

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

Warning from aws-cli sync command:
warning: Skipping file dovecot.sieve -> /var/vmail/vmail1/mydomain.com/t/o/n/tony-2017.01.12.05.27.50/sieve/managesieve.sieve
File does not exist.

this file is a link to another file into the same folder which is: managesieve.sieve.

here how it look if you ls the folder:
dovecot.sieve -> /var/vmail/vmail1/mydomain.com/t/o/n/tony-2017.01.12.05.27.50/sieve/managesieve.sieve
the link is red, mean not linked?

other account the link is green and not linked to managesieve.sieve but look like this:
dovecot.sieve -> Forward Tina Code to support team.sieve

Any solution? Can i delete those broken link file?
tnx

----

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

2

Re: AWS S3 sync/backup fail because dovecot.sieve

tony_ph wrote:

Any solution? Can i delete those broken link file?

Yes.

3

Re: AWS S3 sync/backup fail because dovecot.sieve

Thank you sir.