Quantcast
Channel: iRedMail — iRedMail Support
Viewing all 43488 articles
Browse latest View live

Run iRedMail on the same server as hosted websites?

$
0
0

Hi there

A general question as I cannot find the answer anywhere... I have a server with multiple vhosts. Can iRedMail be installed on the same server or does it have to be on it's own server?

Cheers

Ubuntu 16.04


Re: Reviving Email Problem in Replication

$
0
0
ZhangHuangbin wrote:

Try to read the log lines one by one by yourself. smile

thanks as you mentioned my glusterfs has problem ..!!!

do you know any tools that i use for syncing /var/vmail/ in my 2 servers ?

Re: Reviving Email Problem in Replication

$
0
0

Why not to use Dovecot Replication? I'm still on beginning of mail server management, but what are you doing seems like overly complicated workaround for task which has actual tools available.

Re: DKIM Selector

$
0
0

I would like to have two servers in sync and I believe that having two selectors is cleaner than sharing the same Key.

A log of junk mail send into mail server, how to block it.

$
0
0

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


Our user will forward email to google for backup purpose. Recently, our mail server received a lot of SPAM, so the SPAM is forward to google. After that, out mail server is block by google now.

HOW to block the SPAM ON amavisd or postfix or iredmail?
the SPAM domain name is XXX.icu, XXX.ic XXX.ru,  but i worry the mis-blocking if force block the XXX.icu  XXX.ic  XXX.ru on postfix [ check_sender_access pcre:/etc/postfix/reject_domains ]




[root@svr log]# mailq
-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
29E9C5C00CA     5993 Tue Jan  8 16:48:12  nitid@preynne.icu
(host alt1.gmail-smtp-in.l.google.com[64.233.168.26] said: 421-4.7.0 [202.181.178.189      15] Our system has detected that this message is 421-4.7.0 suspicious due to the very low reputation of the sending domain. To 421-4.7.0 best protect our users from spam, the message has been blocked. 421-4.7.0 Please visit 421 4.7.0  https://support.google.com/mail/answer/188131 for more information. p81si14516247oia.75 - gsmtp (in reply to end of DATA command))
                                         user@gmail.com

B245B5C00C9     5163 Tue Jan  8 16:47:17  nitid@preynne.icu
(host alt1.gmail-smtp-in.l.google.com[64.233.168.26] said: 421-4.7.0 [202.181.178.189      15] Our system has detected that this message is 421-4.7.0 suspicious due to the very low reputation of the sending domain. To 421-4.7.0 best protect our users from spam, the message has been blocked. 421-4.7.0 Please visit 421 4.7.0  https://support.google.com/mail/answer/188131 for more information. p10si548788otl.267 - gsmtp (in reply to end of DATA command))
                                         user@gmail.com

C83D55C00C6     5992 Tue Jan  8 16:45:11  vinie@preynne.icu
(host alt1.gmail-smtp-in.l.google.com[64.233.168.27] said: 421-4.7.0 [202.181.178.189      15] Our system has detected that this message is 421-4.7.0 suspicious due to the very low reputation of the sending domain. To 421-4.7.0 best protect our users from spam, the message has been blocked. 421-4.7.0 Please visit 421 4.7.0  https://support.google.com/mail/answer/188131 for more information. l13si30398808otf.147 - gsmtp (in reply to end of DATA command))
                                         user@gmail.com

877495C00C7     8874 Tue Jan  8 17:42:58  pulse@homylie.icu
(host alt1.gmail-smtp-in.l.google.com[64.233.169.27] said: 421-4.7.0 [202.181.178.189      15] Our system has detected an unusual rate of 421-4.7.0 unsolicited mail originating from your IP address. To protect our 421-4.7.0 users from spam, mail sent from your IP address has been temporarily 421-4.7.0 rate limited. Please visit 421-4.7.0  https://support.google.com/mail/?p=Unso … LimitError to 421 4.7.0 review our Bulk Email Senders Guidelines. y203si22939945oiy.164 - gsmtp (in reply to end of DATA command))
                                         user@gmail.com

D0EA55C00C4     8641 Tue Jan  8 17:39:41  yquem@homylie.icu
(host alt1.gmail-smtp-in.l.google.com[64.233.169.26] said: 421-4.7.0 [202.181.178.189      15] Our system has detected an unusual rate of 421-4.7.0 unsolicited mail originating from your IP address. To protect our 421-4.7.0 users from spam, mail sent from your IP address has been temporarily 421-4.7.0 rate limited. Please visit 421-4.7.0  https://support.google.com/mail/?p=Unso … LimitError to 421 4.7.0 review our Bulk Email Senders Guidelines. t202si24843192oih.223 - gsmtp (in reply to end of DATA command))
                                         user@gmail.com

1E9EA5C00CC     7620 Tue Jan  8 17:41:39  yquem@homylie.icu
(host alt1.gmail-smtp-in.l.google.com[64.233.169.26] said: 421-4.7.0 [202.181.178.189      15] Our system has detected an unusual rate of 421-4.7.0 unsolicited mail originating from your IP address. To protect our 421-4.7.0 users from spam, mail sent from your IP address has been temporarily 421-4.7.0 rate limited. Please visit 421-4.7.0  https://support.google.com/mail/?p=Unso … LimitError to 421 4.7.0 review our Bulk Email Senders Guidelines. 94si36150554oto.184 - gsmtp (in reply to end of DATA command))
                                        user@gmail.com




[root@svr log]# cat /var/log/maillog | grep nitid@preynne.icu
Jan  8 16:47:16 mail postfix/qmgr[7552]: C20735C00BC: from=<nitid@preynne.icu>, size=4088, nrcpt=2 (queue active)
Jan  8 16:47:17 mail postfix/qmgr[7552]: C053C5C00CA: from=<nitid@preynne.icu>, size=5165, nrcpt=1 (queue active)
Jan  8 16:47:17 mail postfix/qmgr[7552]: B245B5C00C9: from=<nitid@preynne.icu>, size=5163, nrcpt=1 (queue active)
Jan  8 16:47:17 mail amavis[8664]: (08664-16) Passed CLEAN {RelayedInbound}, [37.44.228.26]:47675 [37.44.228.26] <nitid@preynne.icu> -> <user@gmail.com>, Queue-ID: C20735C00BC, Message-ID: <a5mXnsmMx7OEM0q58q37j_Fj6CFuarQ_-SuedNVjFFs.BcUlZfvnbV4bZYWBxRABeU5jk5LBBrmjPgKhQb_3CyA@preynne.icu>, mail_id: 7IJ-oPMrRrhi, Hits: 3.198, size: 4080, queued_as: B245B5C00C9, dkim_sd=mta:preynne.icu, 1612 ms
Jan  8 16:47:17 mail amavis[9333]: (09333-07) Passed CLEAN {RelayedInbound}, [37.44.228.26]:47675 [37.44.228.26] <nitid@preynne.icu> -> <USER@DOMAIN.com>, Queue-ID: C20735C00BC, Message-ID: <a5mXnsmMx7OEM0q58q37j_Fj6CFuarQ_-SuedNVjFFs.BcUlZfvnbV4bZYWBxRABeU5jk5LBBrmjPgKhQb_3CyA@preynne.icu>, mail_id: p0vHc8-Tt3S2, Hits: 3.198, size: 4080, queued_as: C053C5C00CA, dkim_sd=mta:preynne.icu, 1646 ms
Jan  8 16:48:08 mail postfix/qmgr[7552]: 732B95C00CB: from=<nitid@preynne.icu>, size=4251, nrcpt=1 (queue active)
Jan  8 16:48:10 mail postfix/qmgr[7552]: 5E95A5C00CA: from=<nitid@preynne.icu>, size=5318, nrcpt=1 (queue active)
Jan  8 16:48:10 mail amavis[9333]: (09333-08) Passed CLEAN {RelayedInbound}, [37.44.228.26]:46735 [37.44.228.26] <nitid@preynne.icu> -> <johnchu@lision.com.hk>, Queue-ID: 732B95C00CB, Message-ID: <IubjQ0LD1gk1zCy-0IXSyjB98BJbR3r4XHDllDwwP0c.-fVQwyp4oJS0suWakYUsGJCkzPxmgWCmfQkDIIf5SDo@preynne.icu>, mail_id: jcBhs87o2gqT, Hits: 3.198, size: 4243, queued_as: 5E95A5C00CA, dkim_sd=mta:preynne.icu, 1550 ms
Jan  8 16:48:10 mail postfix/pickup[5177]: 7A9895C00CB: uid=2000 from=<nitid@preynne.icu>
Jan  8 16:48:10 mail postfix/qmgr[7552]: 7A9895C00CB: from=<nitid@preynne.icu>, size=5550, nrcpt=1 (queue active)
Jan  8 16:48:12 mail postfix/qmgr[7552]: 29E9C5C00CA: from=<nitid@preynne.icu>, size=5993, nrcpt=1 (queue active)
Jan  8 16:48:12 mail amavis[8664]: (08664-17) Passed CLEAN {RelayedInbound}, [127.0.0.1] [37.44.228.26] <nitid@preynne.icu> -> <lisionhongltd@gmail.com>, Message-ID: <IubjQ0LD1gk1zCy-0IXSyjB98BJbR3r4XHDllDwwP0c.-fVQwyp4oJS0suWakYUsGJCkzPxmgWCmfQkDIIf5SDo@preynne.icu>, mail_id: aGYsSAm-6JX3, Hits: 3.199, size: 5542, queued_as: 29E9C5C00CA, dkim_sd=mta:preynne.icu, 1682 ms
Jan  8 16:48:24 mail postfix/qmgr[7552]: F24395C00CC: from=<nitid@preynne.icu>, size=4023, nrcpt=1 (queue active)
Jan  8 16:48:25 mail postfix/qmgr[7552]: DBCCE5C00D1: from=<nitid@preynne.icu>, size=5078, nrcpt=1 (queue active)
Jan  8 16:48:25 mail amavis[8885]: (08885-16) Passed CLEAN {RelayedInbound}, [37.44.228.26]:41454 [37.44.228.26] <nitid@preynne.icu> -> <sc@camieliu.com>, Queue-ID: F24395C00CC, Message-ID: <_RapTKeLIiKgGgQQBtB3RlVgHdpa8UPvqPTcQ0rQq64.5DmwmbJFQHq1P3ntXKwXbg@preynne.icu>, mail_id: gQPIEJdnDe1I, Hits: 3.198, size: 4015, queued_as: DBCCE5C00D1, dkim_sd=mta:preynne.icu, 1609 ms
Jan  8 16:48:41 mail postfix/qmgr[7552]: DCE795C00CC: from=<nitid@preynne.icu>, size=4237, nrcpt=1 (queue active)
Jan  8 16:48:42 mail postfix/qmgr[7552]: D36125C00CD: from=<nitid@preynne.icu>, size=5302, nrcpt=1 (queue active)
Jan  8 16:48:42 mail amavis[8615]: (08615-18) Passed CLEAN {RelayedInbound}, [37.44.228.26]:55985 [37.44.228.26] <nitid@preynne.icu> -> <newton@newton.com.hk>, Queue-ID: DCE795C00CC, Message-ID: <QoEkm7BesqEmklBUoXe_mbrOzCzDgfvdJa2fM_n6sDA.3JSqPxTDTgZb-S8x0w0s68xdYGUMfhoobjpEONb5uCI@preynne.icu>, mail_id: IcjOwn542hvF, Hits: 3.198, size: 4229, queued_as: D36125C00CD, dkim_sd=mta:preynne.icu, 1673 ms
Jan  8 16:54:49 mail postfix/qmgr[7552]: 29E9C5C00CA: from=<nitid@preynne.icu>, size=5993, nrcpt=1 (queue active)
Jan  8 16:54:49 mail postfix/qmgr[7552]: B245B5C00C9: from=<nitid@preynne.icu>, size=5163, nrcpt=1 (queue active)
Jan  8 17:04:49 mail postfix/qmgr[7552]: 29E9C5C00CA: from=<nitid@preynne.icu>, size=5993, nrcpt=1 (queue active)
Jan  8 17:04:49 mail postfix/qmgr[7552]: B245B5C00C9: from=<nitid@preynne.icu>, size=5163, nrcpt=1 (queue active)
Jan  8 17:24:49 mail postfix/qmgr[7552]: 29E9C5C00CA: from=<nitid@preynne.icu>, size=5993, nrcpt=1 (queue active)
Jan  8 17:24:49 mail postfix/qmgr[7552]: B245B5C00C9: from=<nitid@preynne.icu>, size=5163, nrcpt=1 (queue active)



[root@svr log]# cat /var/log/maillog | grep yquem@homylie.icu
Jan  8 17:41:37 mail postfix/qmgr[7552]: 25DED5C00C7: from=<yquem@homylie.icu>, size=6963, nrcpt=2 (queue active)
Jan  8 17:41:39 mail postfix/qmgr[7552]: 0B3F25C00CB: from=<yquem@homylie.icu>, size=7622, nrcpt=1 (queue active)
Jan  8 17:41:39 mail amavis[13728]: (13728-16) Passed CLEAN {RelayedInbound}, [37.44.228.27]:35092 [37.44.228.27] <yquem@homylie.icu> -> <USER@DOMAIN.com.hk>, Queue-ID: 25DED5C00C7, Message-ID: <HvSBAR3dvm_oiseUMDuvx4AJCuvIYUxn9awaz-mYRhY.rAJ7JPzgol1NlqqlCEGaJGtxgk-GO8XSBCFzb6kOwpE@homylie.icu>, mail_id: CTpG4ZpDqj5H, Hits: 1.503, size: 6951, queued_as: 0B3F25C00CB, dkim_sd=svr1:homylie.icu, 1589 ms
Jan  8 17:41:39 mail postfix/qmgr[7552]: 1E9EA5C00CC: from=<yquem@homylie.icu>, size=7620, nrcpt=1 (queue active)
Jan  8 17:41:39 mail amavis[13981]: (13981-14) Passed CLEAN {RelayedInbound}, [37.44.228.27]:35092 [37.44.228.27] <yquem@homylie.icu> -> <rebecca.hs.chiu@gmail.com>, Queue-ID: 25DED5C00C7, Message-ID: <HvSBAR3dvm_oiseUMDuvx4AJCuvIYUxn9awaz-mYRhY.rAJ7JPzgol1NlqqlCEGaJGtxgk-GO8XSBCFzb6kOwpE@homylie.icu>, mail_id: NJ1BPxaZW9Ln, Hits: 1.503, size: 6951, queued_as: 1E9EA5C00CC, dkim_sd=svr1:homylie.icu, 1671 ms
Jan  8 17:44:49 mail postfix/qmgr[7552]: D0EA55C00C4: from=<yquem@homylie.icu>, size=8641, nrcpt=1 (queue active)


nslookup

> preynne.icu
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
preynne.icu     MX preference = 10, mail exchanger = aspmx.l.google.com

> homylie.icu
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
homylie.icu     MX preference = 10, mail exchanger = aspmx.l.google.com

Re: Reviving Email Problem in Replication

$
0
0
aida wrote:

Why not to use Dovecot Replication? I'm still on beginning of mail server management, but what are you doing seems like overly complicated workaround for task which has actual tools available.

thanks for reply
i don`t know what is Dovecot ?
my senario is :
i have 2 iredmail servers with PostgreSQL back end
and i want to sync all my send or receive email in /var/vmail directory on my both servers

and my questions is:
does Dovecot Replication support my senario ?

Logs file Empty since IredAPD

$
0
0

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail 0.9.9 MARIADB edition.
- Deployed with downloadable installer
- Ubuntu 18.04 64bit LTS
- Store mail accounts in which backend MySQL
- Web server Nginx
- Manage mail accounts with iRedAdmin-Pro? No
- Log is not properly running
====

Dear All,

I found mail.log,sieve.log,pop3.log,lda.log,imap.log and dovecot.log 0 size every time since I try to update iRedAPD iRedAPD-2.4 that i found from https://dl.iredmail.org/yum/misc/.

I got email as bellow :

/etc/cron.daily/logrotate:
Job for rsyslog.service failed.
See "systemctl status rsyslog.service" and "journalctl -xe" for details.
error: error running non-shared postrotate script for /var/log/php-fpm/php-fpm.log of '/var/log/php-fpm/*.log '
run-parts: /etc/cron.daily/logrotate exited with return code 1

systemctl status rsyslog.service Result :
systemctl status rsyslog.service
● rsyslog.service - System Logging Service
   Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset:
   Active: failed (Result: start-limit-hit) since Sun 2019-01-06 06:25:07 WIB; 2
     Docs: man:rsyslogd(8)
           http://www.rsyslog.com/doc/
  Process: 9270 ExecStart=/usr/sbin/rsyslogd -n (code=exited, status=0/SUCCESS)
Main PID: 9270 (code=exited, status=0/SUCCESS)

Jan 06 06:25:06 mail.myserver.com rsyslogd[9270]: imuxsock: Acquired UNIX socket
Jan 06 06:25:06 mail.myserver.com rsyslogd[9270]: rsyslogd's groupid changed to 1
Jan 06 06:25:06 mail.myserver.com rsyslogd[9270]: rsyslogd's userid changed to 10
Jan 06 06:25:06 mail.myserver.com rsyslogd[9270]:  [origin software="rsyslogd" sw
Jan 06 06:25:07 mail.myserver.com systemd[1]: Stopping System Logging Service...
Jan 06 06:25:07 mail.myserver.com rsyslogd[9270]:  [origin software="rsyslogd" sw
Jan 06 06:25:07 mail.myserver.com systemd[1]: Stopped System Logging Service.
Jan 06 06:25:07 mail.myserver.com systemd[1]: rsyslog.service: Start request repe
Jan 06 06:25:07 mail.myserver.com systemd[1]: rsyslog.service: Failed with result
Jan 06 06:25:07 mail.myserver.com systemd[1]: Failed to start System Logging Serv
...skipping...
● rsyslog.service - System Logging Service


run-parts /etc/cron.daily/logrotate
run-parts: failed to open directory /etc/cron.daily/logrotate: Not a directory
root@mail:/home/myserver#



I know almost nothing about linux, so any help will be highly appreciated

Regards

Re: Reviving Email Problem in Replication


Re: Run iRedMail on the same server as hosted websites?

$
0
0

iRedMail is quite picky and expects an empty system for install. Once it is spawned up you will be able to reconfigure all bits and pieces which you would need. So yes it is possible, but quite inconvenient.

I love separation and on my systems, everything runs in Jail (FreeBSD term sorry) so I would recommend containerization.

Missing packages for installing mlmmh and uwsgi

$
0
0

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 0.9.8 upgrading to 0.9.9
- Deployed with iRedMail Easy or the downloadable installer? installer
- Linux/BSD distribution name and version: RHEL
- 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.
====

# yum install mlmmj uwsgi uwsgi-plugin-python2 uwsgi-logger-syslog python-requests
Loaded plugins: priorities, protectbase, replace
Setting up Install Process
121 packages excluded due to repository priority protections
0 packages excluded due to repository protections
No package mlmmj available.
No package uwsgi available.
No package uwsgi-plugin-python2 available.
No package uwsgi-logger-syslog available.

Getting stuck on upgrading as my system did not have mlmmj installed which when trying to upgrade from 0.9.8 gave me this error:
# bash upgrade_iredadmin.sh
<<< ERROR >>> No mlmmjadmin installation found (/opt/mlmmjadmin).
<<< ERROR >>> Please follow iRedMail upgrade tutorials to the latest
<<< ERROR >>> stable release first, then come back to upgrade iRedAdmin-Pro.
<<< ERROR >>> mlmmj and mlmmjadmin was first introduced in iRedMail-0.9.8.
<<< ERROR >>> https://docs.iredmail.org/iredmail.releases.html

I've followed all tutorials for upgrading, but I'm thinking that because these packages were not available during install they were missed inadvertently in previous upgrades.  I have the iRedMail repository installed - do I need something else in order to add these missing packages?

Re: Run iRedMail on the same server as hosted websites?

$
0
0

Ar ok. Looking around at other solutions, it is starting to look like I will need to set up a dedicated server just for mail... More expense haha oh well...

Thank you for responding!

Re: Run iRedMail on the same server as hosted websites?

$
0
0

Adding to what you said, do you know you think the mail server can be run in a docker set up?

Re: Run iRedMail on the same server as hosted websites?

$
0
0
ckhatton wrote:

Adding to what you said, do you know you think the mail server can be run in a docker set up?

I never tried, but I think that there should not be any problem. It might be actually easier.

Re: Logs file Empty since IredAPD

$
0
0

Dear All,

It back normal after restarting rsyslogd.
Thanks You.

how to update ClamAV ?

$
0
0

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): latest
- Deployed with iRedMail Easy or the downloadable installer? installer
- Linux/BSD distribution name and version: debian
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): mysql
- Web server (Apache or Nginx): N
- Manage mail accounts with iRedAdmin-Pro? No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
ast ClamAV update process started at Tue Jan  8 23:27:39 2019

Last Status:
   WARNING: Your ClamAV installation is OUTDATED!
   WARNING: Local version: 0.99.4 Recommended version: 0.101.1
   DON'T PANIC! Read http://www.clamav.net/documents/upgrading-clamav
   main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
   daily.cld is up to date (version: 25280, sigs: 2201981, f-level: 63, builder: raynman)
   bytecode.cld is up to date (version: 328, sigs: 94, f-level: 63, builder: neo)
====


hi there,

how to update clamAV within iredmail? is it ok to follow their documentation or are there some custom steps involved?

thanks!


Per-user alias addresses have stopped working after 0.9.9 update

$
0
0

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

Problem: Per-user alias addresses on my system have stopped working, possibly as a result of 0.9.9 update. Messages to the target mailbox are working normally, but messages to any associated aliases are being refused with 'user unknown'.

Background: I had been running on 0.9.8 for about six months and per-user alias addresses had been working normally. However recently messages to any per-user alias addresses has been failing with a 'user unknown' bounce.

Looking at the dovecot log the problem appears to be a database lookup failure however I do not know why the lookup is now failing since nothing has changed in the SQL forwardings table since the prior working config, and furthermore non-forwarded mailboxes are receiving mail normally (only forwards to aliases are failing.)

This is possibly coincident with my recent update to 0.9.9 but not absolutely certain. All (manual) update steps during the update were performed without any problems, and I have confirmed that the two new fields in the SQL vmail database table are present, and the dovecot.conf file was modified as instructed (I do not know if these are a factor in the problem, but are the only things that I can see that would be related to the upgrade.)

Any ideas as to why per-user alias forwarding is now failing after working properly since the initial installation?

Thanks in advance.


(In all examples primary mailbox is 'target@mydomain.com' and alias is 'alias_address@mydomain.com')




Relevant data from logs:

Postfix:

Jan 10 03:05:33 mx1 postfix/pipe[25684]: D63CE425FE: to=<alias_address@mydomain.com>, relay=dovecot, delay=0.05, delays=0/0.02/0/0.02, dsn=5.1.1, status=bounced (user unknown)

Dovecot:

Jan 10 03:05:33 mx1 dovecot: lda(alias_address@mydomain.com): Debug: Loading modules from directory: /usr/lib/dovecot/modules
Jan 10 03:05:33 mx1 dovecot: lda(alias_address@mydomain.com): Debug: Module loaded: /usr/lib/dovecot/modules/lib01_acl_plugin.so
Jan 10 03:05:33 mx1 dovecot: lda(alias_address@mydomain.com): Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so
Jan 10 03:05:33 mx1 dovecot: lda(alias_address@mydomain.com: Debug: Module loaded: /usr/lib/dovecot/modules/lib15_notify_plugin.so
Jan 10 03:05:33 mx1 dovecot: lda(alias_address@mydomain.com): Debug: Module loaded: /usr/lib/dovecot/modules/lib20_mail_log_plugin.so
Jan 10 03:05:33 mx1 dovecot: lda(alias_address@mydomain.com): Debug: Module loaded: /usr/lib/dovecot/modules/lib20_mailbox_alias_plugin.so
Jan 10 03:05:33 mx1 dovecot: lda(alias_address@mydomain.com): Debug: Module loaded: /usr/lib/dovecot/modules/lib90_sieve_plugin.so
Jan 10 03:05:33 mx1 dovecot: lda(alias_address@mydomain.com): Debug: Module loaded: /usr/lib/dovecot/modules/lib90_stats_plugin.so
Jan 10 03:05:33 mx1 dovecot: auth: Debug: master in: USER#0111#011alias_address@mydomain.com#011service=lda
Jan 10 03:05:33 mx1 dovecot: auth-worker(25651): Debug: sql(alias_address@mydomain.com): SELECT 'alias_address@mydomain.com' AS master_user, LOWER(CONCAT(mailbox.storagebasedirectory, '/', mailbox.$
Jan 10 03:05:33 mx1 dovecot: auth-worker(25651): sql(alias_address@mydomain.com): unknown user
Jan 10 03:05:33 mx1 dovecot: auth: Debug: userdb out: NOTFOUND#0111

Jan 10 03:05:33 mx1 dovecot: lda(alias_address@mydomain.com): Debug: auth USER input:


Contents of dovecot-mysql.conf:

driver = mysql
default_pass_scheme = CRYPT
connect = host=127.0.0.1 port=3306 dbname=vmail user=vmail password=sql_password

# Required by doveadm tools which require to list all mail users.
iterate_query = SELECT username AS user FROM mailbox

password_query = SELECT mailbox.password, mailbox.allow_nets \
        FROM mailbox,domain \
       WHERE mailbox.username='%u' \
             AND mailbox.`enable%Ls%Lc`=1 \
             AND mailbox.active=1 \
             AND mailbox.domain=domain.domain \
             AND domain.backupmx=0 \
             AND domain.active=1

user_query = SELECT \
            '%u' AS master_user, \
            LOWER(CONCAT(mailbox.storagebasedirectory, '/', mailbox.storagenode, '/', mailbox.maildir)) AS home, \
            CONCAT(mailbox.mailboxformat, ':~/', mailbox.mailboxfolder, '/') AS mail, \
            CONCAT('*:bytes=', mailbox.quota*1048576) AS quota_rule \
        FROM mailbox,domain \
       WHERE mailbox.username='%u' \
             AND mailbox.`enable%Ls%Lc`=1 \
             AND mailbox.active=1 \
             AND mailbox.domain=domain.domain \
             AND domain.backupmx=0 \
             AND domain.active=1


SQL database entries:

MariaDB [vmail]> SELECT * FROM forwardings;
+----+---------------------------+-------------------------+----------------+----------------+-------------+---------+---------------+----------+--------+
| id | address                   | forwarding              | domain         | dest_domain    | is_maillist | is_list | is_forwarding | is_alias | active |
+----+---------------------------+-------------------------+----------------+----------------+-------------+---------+---------------+----------+--------+
|  4 | target@mydomain.com       | target@mydomain.com     | mydomain.com   | mydomain.com   |           0 |       0 |             1 |        0 |      1 |
|  5 | info@mydomain.com         | target@mydomain.com     | mydomain.com   | mydomain.com   |           0 |       0 |             1 |        1 |      1 |
|  6 | contact@mydomain.com      | target@mydomain.com     | mydomain.com   | mydomain.com   |           0 |       0 |             1 |        1 |      1 |
|  7 | postmaster@mydomain.com   | target@mydomain.com     | mydomain.com   | mydomain.com   |           0 |       0 |             1 |        1 |      1 |
|+----+-------------------------+-------------------------+----------------+----------------+-------------+---------+---------------+----------+--------+

Mail to the target mailbox (target@mydomain.com) is working but forwards to all aliases have stopped working.

Re: Per-user alias addresses have stopped working after 0.9.9 update

$
0
0
smiller50 wrote:

Jan 10 03:05:33 mx1 dovecot: auth-worker(25651): Debug: sql(alias_address@mydomain.com): SELECT 'alias_address@mydomain.com' AS master_user, LOWER(CONCAT(mailbox.storagebasedirectory, '/', mailbox.$

Try to run this SQL command manually, if you believe it should return a record but doesn't, please compare the SQL statements with the value in SQL table carefully.

Re: how to update ClamAV ?

Re: Missing packages for installing mlmmh and uwsgi

Re: Reviving Email Problem in Replication

$
0
0
arshambh9 wrote:

does Dovecot Replication support my senario ?

Yes. Dovecot is the POP3/IMAP/SMTP AUTH/SIEVE/... server running in iRedMail, Dovecot replication supports real-time two way mailbox sync, it's much easier than GlusterFS i guess.

FYI: https://wiki.dovecot.org/Replication

Viewing all 43488 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>