1

Topic: Spider Archive Address Using Host IP

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release):
1.5.1 MARIADB edition
- Deployed with iRedMail Easy or the downloadable installer?
Easy
- Linux/BSD distribution name and version:
Ubuntu 18.04.3 LTS
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
MySQL
====

I've deployed Spider Email Archive on an AWS  Ubuntu 22.04.1 LTS in same VPC of iRedmail server.

Can confirm the two instances see each other locally within same VPC. SMTP 25 open for archive server.

iredmail server 172.31.YY.YY
archive server 172.31.XX.XX

Will be using archive@[172.31.XX.XX) as archive address. Have ensured the tick is enabled for host ip address as archiving domain name under Settings -> Archiving Address.

First I want to confirm that with the tick enabled, am I still expected to enter the domain name as [172.31.XX.XX] in the domain name field under Archive Address?

I get INVALID_EMAIL_DOMAIN if I try this.

On dashboard, I see under settings heading :

Archiving Address    archive@[HOST_IP]

Is this correct?

In /etc/postfix/main.cf:

always_bcc = archive@[172.31.XX.XX]

have also tried

always_bcc = archive@archive.domain.com (where domain.com is my domain to be archived)

Under /etc/postfix/transport

archive.domain.com smtp:[172.31.XX.XX]:25
[172.31.XX.XX] smtp:[172.31.XX.XX]:25

Thanks

----

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

2

Re: Spider Archive Address Using Host IP

I've figured it out and am now archiving inbound and outbound.

Basically when ticking the tickbox address as archiving domain name under Settings -> Archiving Address, you are not required to actually enter anything in the domain field on that page.

I also had to ensure that I entered the right IP for the always_bcc option.

For those who are not linux professionals, here are my updates to iredmail once Spider was installed and communicating with iredmail in AWS vpc.

# /etc/postfix/main.cf
always_bcc = archive@[172.31.XX.XX]
# still in /etc/postfix/main.cf Update parameter transport_maps
transport_maps = hash:/etc/postfix/transport
#still in /etc/postfix/main.cf under sender restrictions add the following
check_recipient_access pcre:/etc/postfix/add-x-envelope-to.pcre


# /etc/postfix/transport
archive.domain.com smtp:[172.31.XX.XX]:25
[172.31.XX.XX] smtp:[172.31.XX.XX]:25

#run command
postmap hash:/etc/postfix/transport

#create /etc/postfix/add-x-envelope-to.pcre
sudo nano /etc/postfix/add-x-envelope-to.pcre
#add the following to it
/(.*)/  prepend X-Envelope-To: $1

#restart postfix
service postfix restart

3

Re: Spider Archive Address Using Host IP

Would also like to add how I managed to maildir import using spider-import which worked well.

Using WinSCP I copied spider-import from Archive AWS instance to iRedmail AWS instance.

Copied it to same location /usr/local/bin/

Generate an API code via the admin login to Spider Archive http://XX.XX.XX.XX:8080 (if no SSL was installed)

Under /usr/local/bin on the iRedmail server I then ran the following command for each mailbox

spider-import maildir --api-endpoint http://172.31.XX.XX:8080 --api-token 12312123456789123456789123456789 --path /var/vmail/vmail1/domain.com/a/b/c/name-date/

4

Re: Spider Archive Address Using Host IP

Thanks for sharing. smile