配置到雷鸟客户端,经常配不上,还非常容易掉。
fail2ban 也許擋到了!
fail2ban 加入被擋 IP
ignoreip = 127.0.0.1 127.0.0.0/8 10.0.0.0/8 172.16.0.0/12 192.168.0.0/16 IP
請參考.
支持 Red Hat Enterprise Linux, CentOS, Scientific Linux, Debian, Ubuntu, FreeBSD, OpenBSD
您尚未登陆。 请选择登陆或是注册一个新账号。
iRedMail 开源邮件服务解决方案 » 由 rain6966 发表的文章
配置到雷鸟客户端,经常配不上,还非常容易掉。
fail2ban 也許擋到了!
fail2ban 加入被擋 IP
ignoreip = 127.0.0.1 127.0.0.0/8 10.0.0.0/8 172.16.0.0/12 192.168.0.0/16 IP
請參考.
rain6966 写道:# ll /usr/lib/systemd/system/iredapd.service
-r-x------ 1 root root 325 12月 25 12:19 /usr/lib/systemd/system/iredapd.service
更改為 0644後, 目前未看到上面錯誤訊息iRedMail-0.9.9 里是设置为 0644 的:
https://bitbucket.org/zhb/iredmail/src/ … h#lines-47
Hi 版主:
48: chmod 0644 ${IREDAPD_ROOT_DIR_SYMBOL_LINK}/rc_scripts/iredapd.service
可否再加 chmod 0644 ${SYSTEMD_SERVICE_DIR}/iredapd.service
因為系統新裝,沒動過它 , 也許我又撞牆了! (對我這不懂程式的人)
感謝回覆.
Hi 版主:
1).
重新安裝 還是無法登入
發現是網卡設定, 在安裝時 zone 未更改
#ZONE=public
ZONE=iredmail
手動更改後, 可以登入/
2). iRedApd.servie 錯誤訊息
Dec 25 12:42:02 mail systemd: Configuration file /usr/lib/systemd/system/iredapd.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Dec 25 12:42:02 mail systemd: Configuration file /usr/lib/systemd/system/iredapd.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
# ll /usr/lib/systemd/system/iredapd.service
-r-x------ 1 root root 325 12月 25 12:19 /usr/lib/systemd/system/iredapd.service
更改為 0644後, 目前未看到上面錯誤訊息
# chmod 0644 /usr/lib/systemd/system/iredapd.service
# systemctl restart iredapd.service
3), 官網文件, 版主有空 , 須更改了
Hi 版主:
查了 官網 :
https://docs.iredmail.org/file.locations.html#roundcube
RHEL/CentOS: /var/www/roundcubemail.
Debian/Ubuntu: /opt/www/roundcubemail.https://docs.iredmail.org/file.locations.html#iredadmin
on RHEL/CentOS, it's /var/www/iredadmin/settings.py.
on Debian/Ubuntu, it's /opt/www/iredadmin/settings.py (in recent iRedMail releases)
再仔細查看 : iRedMail-0.9.9 的 ChangeLog , 以後的目錄是在 /opt/www 下了.(本人不查啊!)
4). 建議 ,https://docs.iredmail.org/index.html 有 feed 訂閱功能 ,
原本以前:https://bitbucket.org/zhb/iredmail-docs/commits/all 可使用 TB 的feed 定閱,現無此功能了.
像doc官網上的"https://docs.iredmail.org/letsencrypt.html" 什摩時候加上去的也不知道, 看了版主在論壇討論才知道,
若 doc 官網 在每篇文章, 加上編修日期, 在閱讀上也許更容易區分辨別.
感謝 .
Hi 版主:
查了 官網 :
https://docs.iredmail.org/file.locations.html#roundcube
RHEL/CentOS: /var/www/roundcubemail.
Debian/Ubuntu: /opt/www/roundcubemail.
https://docs.iredmail.org/file.locations.html#iredadmin
on RHEL/CentOS, it's /var/www/iredadmin/settings.py.
on Debian/Ubuntu, it's /opt/www/iredadmin/settings.py (in recent iRedMail releases)
好像裝成Debian/Ubuntu 的版本了, 非常奇怪啦!! 第一次碰到.
# cat /etc/redhat-release
CentOS Linux release 7.6.1810 (Core)
我可要重新安裝了, 問題怎會裝到Debian/Ubuntu?
版主, 我要重新安裝, 官網的SOURCE code 是否正常?
感謝.
Hi 版主:
重開機過, 查了各個服務,
uwsgi.service
slapd.service
這兩個未啟動,
uwsgi 可手動起用. slapd 則不可.
messages:
Dec 24 13:39:12 mail systemd: Configuration file /usr/lib/systemd/system/iredapd.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Dec 24 13:39:12 mail systemd: Configuration file /usr/lib/systemd/system/iredapd.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Dec 24 13:39:13 mail systemd: Starting OpenLDAP Server Daemon...
Dec 24 13:39:13 mail check-config.sh: Warning: Usage of a configuration file is obsolete!
Dec 24 13:39:13 mail check-config.sh: Checking configuration file failed:
Dec 24 13:39:13 mail check-config.sh: 5c207101 could not open config file "/etc/openldap/schema/calentry.schema": Permission denied (13)
Dec 24 13:39:13 mail check-config.sh: slaptest: bad configuration file!
Dec 24 13:39:13 mail systemd: slapd.service: control process exited, code=exited status=1
Dec 24 13:39:13 mail systemd: Failed to start OpenLDAP Server Daemon.
Dec 24 13:39:13 mail systemd: Unit slapd.service entered failed state.
Dec 24 13:39:13 mail systemd: slapd.service failed.
ll /etc/openldap/schema/
總計 380
-rw-r--r-- 1 root root 36394 12月 24 11:28 amavisd-new.schema
-rwx------ 1 root root 3907 12月 24 11:28 calentry.schema
-rwx------ 1 root root 6469 12月 24 11:28 calresource.schema
-r--r--r-- 1 root root 2036 10月 31 07:14 collective.ldif
-r--r--r-- 1 root root 6190 10月 31 07:14 collective.schema
-r--r--r-- 1 root root 1845 10月 31 07:14 corba.ldif
-r--r--r-- 1 root root 8063 10月 31 07:14 corba.schema
-r--r--r-- 1 root root 20612 10月 31 07:14 core.ldif
-r--r--r-- 1 root root 20499 10月 31 07:14 core.schema
-r--r--r-- 1 root root 12006 10月 31 07:14 cosine.ldif
-r--r--r-- 1 root root 73994 10月 31 07:14 cosine.schema
-r--r--r-- 1 root root 4842 10月 31 07:14 duaconf.ldif
-r--r--r-- 1 root root 10388 10月 31 07:14 duaconf.schema
-r--r--r-- 1 root root 3330 10月 31 07:14 dyngroup.ldif
-r--r--r-- 1 root root 3289 10月 31 07:14 dyngroup.schema
-r--r--r-- 1 root root 3481 10月 31 07:14 inetorgperson.ldif
-r--r--r-- 1 root root 6267 10月 31 07:14 inetorgperson.schema
-rwx------ 1 root root 19525 12月 24 11:28 iredmail.schema
-r--r--r-- 1 root root 2979 10月 31 07:14 java.ldif
-r--r--r-- 1 root root 13901 10月 31 07:14 java.schema
-r--r--r-- 1 root root 2082 10月 31 07:14 misc.ldif
-r--r--r-- 1 root root 2387 10月 31 07:14 misc.schema
-r--r--r-- 1 root root 6809 10月 31 07:14 nis.ldif
-r--r--r-- 1 root root 7640 10月 31 07:14 nis.schema
-r--r--r-- 1 root root 3308 10月 31 07:14 openldap.ldif
-r--r--r-- 1 root root 1514 10月 31 07:14 openldap.schema
-r--r--r-- 1 root root 6904 10月 31 07:14 pmi.ldif
-r--r--r-- 1 root root 20467 10月 31 07:14 pmi.schema
-r--r--r-- 1 root root 4570 10月 31 07:14 ppolicy.ldif
-r--r--r-- 1 root root 20489 10月 31 07:14 ppolicy.schema
權限好像有問題 , 這4個正確權現為何?
-rw-r--r-- 1 root root 36394 12月 24 11:28 amavisd-new.schema
-rwx------ 1 root root 3907 12月 24 11:28 calentry.schema
-rwx------ 1 root root 6469 12月 24 11:28 calresource.schema
-rwx------ 1 root root 19525 12月 24 11:28 iredmail.schema
改為 0444 , slapd 可整常啟動.
但還是無法登入.
ps: iredapd.service
Dec 24 13:39:12 mail systemd: Configuration file /usr/lib/systemd/system/iredapd.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
在0.9.8 就有此問題 , 0.9.9 全新安裝 ,還是會出現此問題 .
我先前的處理方法:
chmod 0644 /opt/iredapd/rc_scripts/iredapd.service
不知此方法是正確.
Hi 版主:
iRedMail0-0.9.9 安裝的iRedAdmin和roundcubemai目錄是已預設變更?
全改為在 /opt/www 目錄下 , 無法登入使用(後端及webmai).
# ls -al /root/
總計 1348
dr-xr-x---. 5 root root 4096 12月 24 12:24 .
dr-xr-xr-x. 18 root root 256 12月 24 11:55 ..
-rw-------. 1 root root 2032 12月 22 17:51 anaconda-ks.cfg
-rw-------. 1 root root 8208 12月 24 11:33 .bash_history
-rw-r--r--. 1 root root 18 12月 29 2013 .bash_logout
-rw-r--r--. 1 root root 176 12月 29 2013 .bash_profile
-rw-r--r-- 1 root root 27861 12月 23 22:05 .bashrc
-rw-r--r--. 1 root root 100 12月 29 2013 .cshrc
drwx------ 13 33 tape 278 12月 22 19:29 iRedAdmin-Pro-LDAP-3.2
-rwx------ 1 root root 1103631 12月 23 10:34 iRedAdmin-Pro-LDAP-3.2.tar.bz2
dr-------- 9 root root 214 12月 24 11:29 iRedMail-0.9.9
-rwx------ 1 root root 160754 12月 23 10:34 iRedMail-0.9.9.tar.bz2
-r-------- 1 root root 216 12月 24 11:28 .my.cnf
-rw-r--r-- 1 root root 89 12月 24 11:29 .my.cnf-amavisd
-rw-r--r-- 1 root root 91 12月 24 11:29 .my.cnf-iredadmin
-rw-r--r-- 1 root root 89 12月 24 11:29 .my.cnf-iredapd
-rw-r--r-- 1 root root 91 12月 24 11:29 .my.cnf-roundcube
-rw-r--r-- 1 root root 86 12月 24 11:29 .my.cnf-sogo
-rw-r--r-- 1 root root 87 12月 24 11:28 .my.cnf-vmail
-rw-r--r-- 1 root root 92 12月 24 11:28 .my.cnf-vmailadmin
drwxr----- 3 root root 19 12月 23 21:58 .pki
-rw------- 1 root root 1024 12月 24 11:28 .rnd
-rw-r--r--. 1 root root 129 12月 29 2013 .tcshrc
-rw------- 1 root root 5682 12月 24 12:23 .viminfo
# ls -la /opt
總計 0
drwxr-xr-x. 6 root root 106 12月 24 11:29 .
dr-xr-xr-x. 18 root root 256 12月 24 11:55 ..
lrwxrwxrwx 1 root root 16 12月 24 11:29 iredapd -> /opt/iRedAPD-2.3
dr-x------ 9 root root 321 12月 24 11:54 iRedAPD-2.3
lrwxrwxrwx 1 root root 19 12月 24 11:28 mlmmjadmin -> /opt/mlmmjadmin-1.9
drwxr-xr-x 10 mlmmj mlmmj 292 12月 24 11:36 mlmmjadmin-1.9
drwxr-sr-x 10 netdata netdata 263 12月 24 11:29 netdata
drwxr-xr-x 4 root root 94 12月 24 11:29 www
# ls -la /opt/www/
總計 4
drwxr-xr-x 4 root root 94 12月 24 11:29 .
drwxr-xr-x. 6 root root 106 12月 24 11:29 ..
lrwxrwxrwx 1 root root 24 12月 24 11:29 iredadmin -> /opt/www/iRedAdmin-0.9.3
dr-xr-xr-x 11 iredadmin iredadmin 4096 12月 24 12:01 iRedAdmin-0.9.3
lrwxrwxrwx 1 root root 28 12月 24 11:29 roundcubemail -> /opt/www/roundcubemail-1.3.8
drwxr-xr-x 13 root root 300 12月 24 11:29 roundcubemail-1.3.8
# ls -la /var/www
總計 0
drwxr-xr-x 4 root root 33 12月 24 11:26 .
drwxr-xr-x. 20 root root 278 12月 24 11:28 ..
drwxr-xr-x 2 root root 6 11月 5 09:47 cgi-bin
drwxr-xr-x 2 root root 42 12月 24 11:28 html
感謝
Hi 版主:
在Profile of user: 頁面裡的Forwarding > Enable mail forwarding 打勾 框框 ,無法限定 ,
需在 Advanced 裡設定.
建議 : Enable mail forwarding的打勾 框框 , 設計為只顯示狀態(打勾或未打勾) ,框框mark起來,無法讓操作者去設定, (在此頁面下, 設定是無效的, 需至Advanced 頁面設定)
或 取消 "Enable mail forwarding的打勾 框框" , 實際上在Advanced 裡就可查看其狀態了(Forwarding mails to other addresses).
除非其意涵是不同的, 但在Advanced 裡把其打勾, Forwarding 裡會跟著打勾.
為何重複功能顯示? 在 Forwarding 頁面會有設定無效的現象困惑?
感謝.
1). test@ 啟動 BCC , test2@ 未啟動 BCC
log 檔 2200 多行 , 我從 @gmail 分別寄給 test@ 及 test2@
2).
# postconf sender_bcc_maps recipient_bcc_maps
sender_bcc_maps = proxy:ldap:/etc/postfix/ldap/sender_bcc_maps_user.cf proxy:ldap:/etc/postfix/ldap/sender_bcc_maps_domain.cf
recipient_bcc_maps = proxy:ldap:/etc/postfix/ldap/recipient_bcc_maps_user.cf proxy:ldap:/etc/postfix/ldap/recipient_bcc_maps_domain.cf
3).
A). domain:
LDIF: mydomain.com
accountSetting: defaultSenderBcc:admin@mydomain.com
accountSetting: defaultLanguage:
accountSetting: defaultRecipientBcc:admin@mydomain.com
accountSetting: timezone:Asia/Taipei
accountSetting: defaultQuota:4024
accountSetting: minPasswordLength:8
accountStatus: active
domainCurrentAliasNumber: 0
domainCurrentListNumber: 1
domainCurrentQuotaSize: 67750592512
domainCurrentUserNumber: 10
domainName: mydomain.com
domainRecipientBccAddress: admin@mydomain.com
domainSenderBccAddress: admin@mydomain.com
enabledService: mail
enabledService: recipientbcc
enabledService: senderbcc
mtaTransport: dovecot
objectClass: mailDomain
B).user: test@ 啟用 bcc
LDIF: test@mydomain.com
accountStatus: active
amavisLocal: TRUE
cn: test
enabledService: managesievetls
enabledService: managesieve
enabledService: imaptls
enabledService: displayedInGlobalAddressBook
enabledService: deliver
enabledService: smtp
enabledService: lda
enabledService: smtpsecured
enabledService: pop3
enabledService: lmtp
enabledService: lib-storage
enabledService: sieve
enabledService: imap
enabledService: dsync
enabledService: shadowaddress
enabledService: sogo
enabledService: imapsecured
enabledService: pop3tls
enabledService: senderbcc
enabledService: recipientbcc
enabledService: pop3secured
enabledService: internal
enabledService: doveadm
enabledService: managesievesecured
enabledService: mail
enabledService: indexer-worker
enabledService: sievesecured
homeDirectory: /var/vmail/vmail1/mydomain.com/t/e/s/test-2018.12.09.15.54.46/
mail: test@mydomain.com
mailMessageStore: vmail1/mydomain.com/t/e/s/test-2018.12.09.15.54.46/
mailQuota: 1073741824
mailboxFolder: mdbox
mailboxFormat: mdbox
objectClass: inetOrgPerson
objectClass: mailUser
objectClass: shadowAccount
objectClass: amavisAccount
preferredLanguage: en_US
shadowLastChange: 17874
sn: test
storageBaseDirectory: /var/vmail/
uid: test
userPassword: {SSHA}xxxxxxxx
userRecipientBccAddress: admin@mydomain.com
userSenderBccAddress: admin@mydomain.com
C).user: test2@ 未啟用BCC
LDIF: test2@mydomain.com
accountStatus: active
amavisLocal: TRUE
cn: test2
enabledService: managesievetls
enabledService: managesieve
enabledService: imaptls
enabledService: displayedInGlobalAddressBook
enabledService: deliver
enabledService: smtp
enabledService: lda
enabledService: smtpsecured
enabledService: pop3
enabledService: lmtp
enabledService: lib-storage
enabledService: sieve
enabledService: imap
enabledService: dsync
enabledService: shadowaddress
enabledService: sogo
enabledService: imapsecured
enabledService: pop3tls
enabledService: pop3secured
enabledService: internal
enabledService: doveadm
enabledService: managesievesecured
enabledService: mail
enabledService: indexer-worker
enabledService: sievesecured
homeDirectory: /var/vmail/vmail1/mydomain.com/t/e/s/test2-2018.12.09.21.04.06/
mail: test2@mydomain.com
mailMessageStore: vmail1/mydomain.com/t/e/s/test2-2018.12.09.21.04.06/
mailQuota: 1073741824
mailboxFolder: mdbox
mailboxFormat: mdbox
objectClass: inetOrgPerson
objectClass: mailUser
objectClass: shadowAccount
objectClass: amavisAccount
preferredLanguage: en_US
shadowLastChange: 17874
sn: test2
storageBaseDirectory: /var/vmail/
uid: test2
userPassword: {SSHA}xxxxxxxx
感謝 版主.
Hi 版主:
好了一半.
BCC incoming emails to other address
BCC outgoing emails to other address現要取消 , 無法清空 , 會自動出現 "None"
可以取消,不會出現"None"了, BCC 可正常運作
但另一半:
我再填入 admin@mydomain.com ,
有啟動 BCC 的帳戶或未啟動的帳戶, admin@ 皆會收到一份;
我先前的問題又出現了, 從網域帳號或Gmail 帳號寄出皆一樣. 頭大啊!
不過若不是 與此bug 有關,我只能暫時維持欄位 "空白", 它是正常運作的.
感謝 版主.
BTW, 如果你现在获取 iRedAdmin-Pro-LDAP-3.2 的版本,它就是已经 patch 过的了。
# ll /root/iRedAdmin-Pro-LDAP-3.2*
-r-------- 1 root root 1103747 12月 18 15:26 /root/iRedAdmin-Pro-LDAP-3.2.tar.bz2
/root/iRedAdmin-Pro-LDAP-3.2:
總計 100
-rw-r--r-- 1 33 33 36 12月 17 14:03 AUTHORS
-rw-r--r-- 1 33 33 67646 12月 17 14:03 ChangeLog.ldap
drwxr-xr-x 7 33 33 130 12月 17 14:03 controllers
drwxr-xr-x 3 33 33 110 12月 17 14:03 docs
-rw-r--r-- 1 33 33 550 12月 17 14:03 EULA
drwxr-xr-x 22 33 33 322 12月 17 14:03 i18n
-rw-r--r-- 1 33 33 432 12月 17 14:03 iredadmin.py
drwxr-xr-x 7 33 33 4096 12月 17 14:03 libs
drwxr-xr-x 3 33 33 49 12月 17 14:03 plugins
drwxr-xr-x 4 33 33 130 12月 17 14:03 rc_scripts
-rw-r--r-- 1 33 33 894 12月 17 14:03 README
drwxr-xr-x 2 33 33 6 12月 17 14:03 samples
-rw-r--r-- 1 33 33 4813 12月 17 14:03 settings.py.ldap.sample
drwxr-xr-x 3 33 33 68 12月 17 14:03 SQL
drwxr-xr-x 5 33 33 102 12月 17 14:03 static
drwxr-xr-x 3 33 33 21 12月 17 14:03 templates
drwxr-xr-x 2 33 33 4096 12月 17 14:03 tools
# ll /var/www/
總計 4
drwxr-xr-x 2 root root 6 11月 5 09:47 cgi-bin
drwxr-xr-x 3 root root 100 12月 9 15:02 html
lrwxrwxrwx 1 root root 22 12月 18 15:41 iredadmin -> iRedAdmin-Pro-LDAP-3.2
dr-xr-xr-x 10 iredadmin iredadmin 331 12月 8 13:01 iRedAdmin-0.9.1
dr-xr-xr-x 11 iredadmin iredadmin 4096 12月 18 12:01 iRedAdmin-0.9.2
dr-xr-xr-x 11 iredadmin iredadmin 284 12月 11 12:01 iRedAdmin-Pro-LDAP-3.0
dr-xr-xr-x 11 iredadmin iredadmin 284 12月 17 15:01 iRedAdmin-Pro-LDAP-3.1
dr-xr-xr-x 13 iredadmin iredadmin 317 12月 18 16:01 iRedAdmin-Pro-LDAP-3.2
lrwxrwxrwx 1 root root 28 12月 18 11:48 roundcubemail -> /var/www/roundcubemail-1.3.8
drwxr-xr-x 13 root root 300 12月 8 12:34 roundcubemail-1.3.6
drwxr-xr-x 13 root root 322 12月 18 11:45 roundcubemail-1.3.8
iRedMail 的忠實粉絲 , 也許我下載的是早了一點點的版本 ,
它還沒修正.
比官網 News 發布時間2018-12-17 15:40:12 還早.
自己上patch 後, 期待能解決.
感謝.
Hi 版主:
在我先前 "無法取消BCC" 問題有提到:
"但在 Profile of user: >Advanced >Forwarding mails to other addresses ,取消打勾後 ,上面 Forwarding >Enable mail forwarding 直接跟著取消打勾 .
無法在 Forwarding 裡設定 , 需在 Advanced 裡設定."
iRedAdmin-Pro 主控台(後端):
其實在 Advance 才能設定 ,但在"Forwarding >Enable mail forwarding "
應無法直接在此取消打勾 , 可否把打勾框框 "馬塞克" , 只能作顯示 ,無法像我這樣會嘗試去更改,卻無法設定的錯誤現象; 或直接不顯示 , 把其取消 打勾的畫框.
感謝.
应该是 bug,明天我测试后给您反馈。
Hi 版主:
我非常期待它確實是bug!!!!!
再啟用 postfix debug:
main.cf:
debug_peer_level = 10
debug_peer_list = 127.0.0.1
debug_peer_list = mydomain.com
#mynetworks = 127.0.0.1
mynetworks = 10.10.10.0/24
master.cf:
cleanup unix n - n - 0 cleanup -v
qmgr unix n - n 300 1 qmgr -v
從gmail 給啟用BCC 的 test@ 帳號 , 結果正常 , admin@ 也收到
從gmail 給未啟用BCC 的 test2@ 帳號 , 結果正常 , admin@ 未收
但從 maillog 察看是有錯誤訊息:
# grep 'Dec 19 11:5' /var/log/maillog|grep -in none@mail.mydomain.com
1801:Dec 19 11:58:14 mail postfix/cleanup[16149]: input attribute value: None@mail.mydomain.com
1804:Dec 19 11:58:14 mail postfix/cleanup[16149]: rewrite_clnt: local: None -> None@mail.mydomain.com
1805:Dec 19 11:58:14 mail postfix/cleanup[16149]: been_here_check: None@mail.mydomain.com: 0
1809:Dec 19 11:58:14 mail postfix/cleanup[16149]: send attr key = None@mail.mydomain.com
1818:Dec 19 11:58:14 mail postfix/cleanup[16149]: dict_proxy_lookup: table=ldap:/etc/postfix/ldap/virtual_alias_maps.cf flags=lock|fold_fix key=None@mail.mydomain.com -> status=1 result=
1822:Dec 19 11:58:14 mail postfix/cleanup[16149]: send attr key = None@mail.mydomain.com
1831:Dec 19 11:58:14 mail postfix/cleanup[16149]: dict_proxy_lookup: table=ldap:/etc/postfix/ldap/virtual_group_maps.cf flags=lock|fold_fix key=None@mail.mydomain.com -> status=1 result=
1835:Dec 19 11:58:14 mail postfix/cleanup[16149]: send attr key = None@mail.mydomain.com
1844:Dec 19 11:58:14 mail postfix/cleanup[16149]: dict_proxy_lookup: table=ldap:/etc/postfix/ldap/virtual_group_members_maps.cf flags=lock|fold_fix key=None@mail.mydomain.com -> status=1 result=
1848:Dec 19 11:58:14 mail postfix/cleanup[16149]: send attr key = None@mail.mydomain.com
1857:Dec 19 11:58:14 mail postfix/cleanup[16149]: dict_proxy_lookup: table=ldap:/etc/postfix/ldap/catchall_maps.cf flags=lock|fold_fix key None@mail.mydomain.com -> status=1 result=
1858:Dec 19 11:58:14 mail postfix/cleanup[16149]: maps_find: virtual_alias_maps: None@mail.mydomain.com: not found
1965:Dec 19 11:58:14 mail postfix/cleanup[16149]: mail_addr_find: None@mail.mydomain.com -> (not found)
1966:Dec 19 11:58:14 mail postfix/cleanup[16149]: mail_addr_map: None@mail.mydomain.com -> (not found)
1967:Dec 19 11:58:14 mail postfix/cleanup[16149]: been_here: None@mail.mydomain.com: 0
2050:Dec 19 11:58:14 mail postfix/qmgr[17410]: qmgr_message_sort: None@mail.mydomain.com
2054:Dec 19 11:58:14 mail postfix/qmgr[17410]: qmgr_message_sort: None@mail.mydomain.com
2095:Dec 19 11:58:14 mail postfix/qmgr[17410]: send attr recipient = None@mail.mydomain.com
2175:Dec 19 11:58:15 mail postfix/10025/smtpd[16160]: < mail.mydomain.com[127.0.0.1]: RCPT TO:<None@mail.mydomain.com> NOTIFY=NEVER
2176:Dec 19 11:58:15 mail postfix/10025/smtpd[16160]: extract_addr: input: <None@mail.mydomain.com>
2177:Dec 19 11:58:15 mail postfix/10025/smtpd[16160]: smtpd_check_addr: addr=None@mail.mydomain.com
2184:Dec 19 11:58:15 mail postfix/10025/smtpd[16160]: send attr address = None@mail.mydomain.com
2192:Dec 19 11:58:15 mail postfix/10025/smtpd[16160]: input attribute value: None@mail.mydomain.com
2195:Dec 19 11:58:15 mail postfix/10025/smtpd[16160]: rewrite_clnt: local: None@mail.mydomain.com -> None@mail.mydomain.com
2199:Dec 19 11:58:15 mail postfix/10025/smtpd[16160]: send attr address = None@mail.mydomain.com
2213:Dec 19 11:58:15 mail postfix/10025/smtpd[16160]: input attribute value: None@mail.mydomain.com
2219:Dec 19 11:58:15 mail postfix/10025/smtpd[16160]: resolve_clnt: `' -> `None@mail.mydomain.com' -> transp=`local' host=`mail.mydomain.com' rcpt=`None@mail.mydomain.com' flags= class=local
2220:Dec 19 11:58:15 mail postfix/10025/smtpd[16160]: ctable_locate: install entry key None@mail.mydomain.com
2221:Dec 19 11:58:15 mail postfix/10025/smtpd[16160]: extract_addr: in: <None@mail.mydomain.com>, result: None@mail.mydomain.com
2329:Dec 19 11:58:15 mail postfix/cleanup[16149]: initial envelope A dsn_orig_rcpt=rfc822;None@mail.mydomain.com
2330:Dec 19 11:58:15 mail postfix/cleanup[16149]: initial envelope R None@mail.mydomain.com
2333:Dec 19 11:58:15 mail postfix/cleanup[16149]: send attr address = None@mail.mydomain.com
2339:Dec 19 11:58:15 mail postfix/cleanup[16149]: input attribute value: None@mail.mydomain.com
2342:Dec 19 11:58:15 mail postfix/cleanup[16149]: rewrite_clnt: local: None@mail.mydomain.com -> None@mail.mydomain.com
2343:Dec 19 11:58:15 mail postfix/cleanup[16149]: been_here: None@mail.mydomain.com: 0
2416:Dec 19 11:58:15 mail postfix/cleanup[16149]: cleanup_header_callback: 'Received: from mail.mydomain.com (mail.mydomain.com [127.0.0.1])??by mail.mydomain.com (Postfix) with ESMTP id 90E8998000882??for <None@mail.mydomain.com>; Wed, 19 Dec 2018 11:58:15 +0800 (CST)'
2423:Dec 19 11:58:15 mail postfix/cleanup[16149]: cleanup_header_callback: 'Received: from mail.mydomain.com ([127.0.0.1])??by mail.mydomain.com (mail.mydomain.com [127.0.0.1]) (amavisd-new, port 10024)??with ESMTP id l51jpNSLuwZ5 for <None@mail.mydomain.com>;??Wed, 19 Dec 20'
2885:Dec 19 11:58:15 mail postfix/qmgr[17410]: qmgr_message_sort: None@mail.mydomain.com
2914:Dec 19 11:58:15 mail amavis[22743]: (22743-02) Passed CLEAN {RelayedInbound}, [209.85.214.195]:39856 [xx.xx.xx.xx] <xxxxxxxxxxx@gmail.com> -> <None@mail.mydomain.com>, Queue-ID: 3938498000880, Message-ID: <0d12bac1-0bdd-8a40-0a95-4d43986c429e@gmail.com>, mail_id: l51jpNSLuwZ5, Hits: 2.652, size: 2824, queued_as: 90E8998000882, dkim_sd=20161025:gmail.com, 1030 ms, Tests: [BODY_SINGLE_WORD=2.5,DKIM_SIGNED=0.1,DKIM_VALID=-0.1,DKIM_VALID_AU=-0.1,FREEMAIL_ENVFROM_END_DIGIT=0.25,FREEMAIL_FROM=0.001,RCVD_IN_DNSWL_NONE=-0.0001,RCVD_IN_MSPIKE_H3=0.001,RCVD_IN_MSPIKE_WL=0.001,SPF_PASS=-0.001]
2919:Dec 19 11:58:15 mail postfix/qmgr[17410]: send attr address = None@mail.mydomain.com
2924:Dec 19 11:58:15 mail amavis[22743]: (22743-02) Passed CLEAN, <xxxxxxxxxxx@gmail.com> -> <None@mail.mydomain.com>, Hits: 2.652, tag=2, tag2=6.2, kill=6.9, queued_as: 90E8998000882, L/Y/0/0
2960:Dec 19 11:58:15 mail postfix/qmgr[17410]: input attribute value: None@mail.mydomain.com
2978:Dec 19 11:58:15 mail postfix/qmgr[17410]: resolve_clnt: `xxxxxxxxxxx@gmail.com' -> `None@mail.mydomain.com' -> transp=`local' host=`mail.mydomain.com' rcpt=`None@mail.mydomain.com' flags= class=local
2984:Dec 19 11:58:15 mail postfix/qmgr[17410]: qmgr_message_sort: None@mail.mydomain.com
3011:Dec 19 11:58:15 mail postfix/amavis/smtp[16150]: 3938498000880: to=<None@mail.mydomain.com>, relay=127.0.0.1[127.0.0.1]:10024, delay=1.4, delays=0.4/0/0/1, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 90E8998000882)
3079:Dec 19 11:58:15 mail postfix/qmgr[17410]: qmgr_peer_select: 90E8998000882 local none@mail.mydomain.com (1 of 2)
3114:Dec 19 11:58:15 mail postfix/qmgr[17410]: send attr recipient = None@mail.mydomain.com
3116:Dec 19 11:58:15 mail postfix/qmgr[17410]: send attr dsn_orig_rcpt = rfc822;None@mail.mydomain.com
3118:Dec 19 11:58:15 mail postfix/qmgr[17410]: qmgr_deliver: site `none@mail.mydomain.com'
3220:Dec 19 11:58:15 mail postfix/local[16236]: 90E8998000882: to=<None@mail.mydomain.com>, relay=local, delay=0.14, delays=0.04/0.05/0/0.04, dsn=5.1.1, status=bounced (unknown user: "none")
3247:Dec 19 11:58:15 mail postfix/qmgr[17410]: qmgr_queue_unthrottle: queue none@mail.mydomain.com
在:
3220:Dec 19 11:58:15 mail postfix/local[16236]: 90E8998000882: to=<None@mail.mydomain.com>, relay=local, delay=0.14, delays=0.04/0.05/0/0.04, dsn=5.1.1, status=bounced (unknown user: "none")
此會 bounce 給gmail ? 在gmail 卻未收到此bounce 信件
在iRedAdminPro 控制台沒有 none@mydomain.com bounce的收信log , 若能加上 bounce的log分析也許會更好.
這iRedMail 的BCC 問題, 確實讓我頭痛好些時日了! 希望是這個臭蟲.
版主大人, 對不起我這個期待了.
感謝.
建议发到英文论坛去,中文这个论坛会逐步放弃,用的人太少了。
英文論壇 ,有限制規定, 如使用中文提問?
Hi 版主:
在做BCC有關測試 :
原先在 profile of domain > BCC 下面兩欄有填寫帳號:
BCC incoming emails to other address
BCC outgoing emails to other address
現要取消 , 無法清空 , 會自動出現 "None"
## iRedAdmin-Pro-LDAP-3.1 , CentOS7
上面,實際的log 有2200多行, 在開始出現 admin@ 附近的log,我把其節錄出來.
附件 log檔
Hi 版主, 現才回覆 ,抱歉.
- 能否确认没有 user 将邮件 forward 给 admin@?
- 需要贴出 postfix log 和 Dovecot log 来帮助判断到底收件人有哪些。
現我從gmail 的網頁寄給 test2@mydomain.com
此帳號 user profile 的BCC 是關掉的 ;
我在 postfix 啟用debug:
main.cf:
debug_peer_level = 10
debug_peer_list = 127.0.0.1
debug_peer_list = mydomain.com
#mynetworks = 127.0.0.1 [::1]
mynetworks = 127.0.0.1
master.cf:
smtp inet n - n - 1 postscreen -v
smtpd pass - - n - - smtpd -v
pickup unix n - n 60 1 pickup -v
cleanup unix n - n - 0 cleanup -v
cleanup unix n - n - 0 cleanup -v
qmgr unix n - n 300 1 qmgr -v
下面為log :
Dec 14 13:45:17 mail postfix/cleanup[5523]: dict_proxy_lookup: table=ldap:/etc/postfix/ldap/virtual_group_maps.cf flags=lock|fold_fix key=test2@mydomain.com -> status=1 result=
Dec 14 13:45:17 mail postfix/cleanup[5523]: send attr request = lookup
Dec 14 13:45:17 mail postfix/cleanup[5523]: send attr table = ldap:/etc/postfix/ldap/virtual_group_members_maps.cf
Dec 14 13:45:17 mail postfix/cleanup[5523]: send attr flags = 16448
Dec 14 13:45:17 mail postfix/cleanup[5523]: send attr key = test2@mydomain.com
Dec 14 13:45:17 mail postfix/cleanup[5523]: private/proxymap socket: wanted attribute: status
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute name: status
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute value: 0
Dec 14 13:45:17 mail postfix/cleanup[5523]: private/proxymap socket: wanted attribute: value
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute name: value
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute value: test2@mydomain.com
Dec 14 13:45:17 mail postfix/cleanup[5523]: private/proxymap socket: wanted attribute: (list terminator)
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute name: (end)
Dec 14 13:45:17 mail postfix/cleanup[5523]: dict_proxy_lookup: table=ldap:/etc/postfix/ldap/virtual_group_members_maps.cf flags=lock|fold_fix key=test2@mydomain.com -> status=0 result=test2@mydomain.com
Dec 14 13:45:17 mail postfix/cleanup[5523]: maps_find: virtual_alias_maps: proxy:ldap:/etc/postfix/ldap/virtual_group_members_maps.cf(0,lock|fold_fix): test2@mydomain.com = test2@mydomain.com
Dec 14 13:45:17 mail postfix/cleanup[5523]: mail_addr_find: test2@mydomain.com -> test2@mydomain.com
Dec 14 13:45:17 mail postfix/cleanup[5523]: rewrite_clnt: cached: local: test2@mydomain.com -> test2@mydomain.com
Dec 14 13:45:17 mail postfix/cleanup[5523]: mail_addr_map: test2@mydomain.com -> 0: test2@mydomain.com
Dec 14 13:45:17 mail postfix/cleanup[5523]: been_here: test2@mydomain.com: 0
Dec 14 13:45:17 mail postfix/cleanup[5523]: been_here_check: test2@mydomain.com: 1
Dec 14 13:45:17 mail postfix/cleanup[5523]: been_here: test2@mydomain.com: 0
Dec 14 13:45:17 mail postfix/cleanup[5523]: send attr request = lookup
Dec 14 13:45:17 mail postfix/cleanup[5523]: send attr table = ldap:/etc/postfix/ldap/recipient_bcc_maps_user.cf
Dec 14 13:45:17 mail postfix/cleanup[5523]: send attr flags = 16448
Dec 14 13:45:17 mail postfix/cleanup[5523]: send attr key = test2@mydomain.com
Dec 14 13:45:17 mail postfix/cleanup[5523]: private/proxymap socket: wanted attribute: status
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute name: status
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute value: 1
Dec 14 13:45:17 mail postfix/cleanup[5523]: private/proxymap socket: wanted attribute: value
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute name: value
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute value: (end)
Dec 14 13:45:17 mail postfix/cleanup[5523]: private/proxymap socket: wanted attribute: (list terminator)
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute name: (end)
Dec 14 13:45:17 mail postfix/cleanup[5523]: dict_proxy_lookup: table=ldap:/etc/postfix/ldap/recipient_bcc_maps_user.cf flags=lock|fold_fix key=test2@mydomain.com -> status=1 result=
Dec 14 13:45:17 mail postfix/cleanup[5523]: send attr request = lookup
Dec 14 13:45:17 mail postfix/cleanup[5523]: send attr table = ldap:/etc/postfix/ldap/recipient_bcc_maps_domain.cf
Dec 14 13:45:17 mail postfix/cleanup[5523]: send attr flags = 16448
Dec 14 13:45:17 mail postfix/cleanup[5523]: send attr key = test2@mydomain.com
Dec 14 13:45:17 mail postfix/cleanup[5523]: private/proxymap socket: wanted attribute: status
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute name: status
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute value: 0
Dec 14 13:45:17 mail postfix/cleanup[5523]: private/proxymap socket: wanted attribute: value
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute name: value
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute value: admin@mydomain.com
Dec 14 13:45:17 mail postfix/cleanup[5523]: private/proxymap socket: wanted attribute: (list terminator)
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute name: (end)
Dec 14 13:45:17 mail postfix/cleanup[5523]: dict_proxy_lookup: table=ldap:/etc/postfix/ldap/recipient_bcc_maps_domain.cf flags=lock|fold_fix key=test2@mydomain.com -> status=0 result=admin@mydomain.com
Dec 14 13:45:17 mail postfix/cleanup[5523]: maps_find: recipient_bcc_maps: proxy:ldap:/etc/postfix/ldap/recipient_bcc_maps_domain.cf(0,lock|fold_fix): test2@mydomain.com = admin@mydomain.com
Dec 14 13:45:17 mail postfix/cleanup[5523]: mail_addr_find: test2@mydomain.com -> admin@mydomain.com
Dec 14 13:45:17 mail postfix/cleanup[5523]: send attr request = rewrite
Dec 14 13:45:17 mail postfix/cleanup[5523]: send attr rule = local
Dec 14 13:45:17 mail postfix/cleanup[5523]: send attr address = admin@mydomain.com
Dec 14 13:45:17 mail postfix/cleanup[5523]: private/rewrite socket: wanted attribute: flags
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute name: flags
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute value: 0
Dec 14 13:45:17 mail postfix/cleanup[5523]: private/rewrite socket: wanted attribute: address
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute name: address
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute value: admin@mydomain.com
Dec 14 13:45:17 mail postfix/cleanup[5523]: private/rewrite socket: wanted attribute: (list terminator)
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute name: (end)
Dec 14 13:45:17 mail postfix/cleanup[5523]: rewrite_clnt: local: admin@mydomain.com -> admin@mydomain.com
Dec 14 13:45:17 mail postfix/cleanup[5523]: been_here_check: admin@mydomain.com: 0
Dec 14 13:45:17 mail postfix/cleanup[5523]: send attr request = lookup
Dec 14 13:45:17 mail postfix/cleanup[5523]: send attr table = ldap:/etc/postfix/ldap/virtual_alias_maps.cf
Dec 14 13:45:17 mail postfix/cleanup[5523]: send attr flags = 16448
Dec 14 13:45:17 mail postfix/cleanup[5523]: send attr key = admin@mydomain.com
Dec 14 13:45:17 mail postfix/cleanup[5523]: private/proxymap socket: wanted attribute: status
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute name: status
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute value: 1
Dec 14 13:45:17 mail postfix/cleanup[5523]: private/proxymap socket: wanted attribute: value
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute name: value
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute value: (end)
Dec 14 13:45:17 mail postfix/cleanup[5523]: private/proxymap socket: wanted attribute: (list terminator)
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute name: (end)
Dec 14 13:45:17 mail postfix/cleanup[5523]: dict_proxy_lookup: table=ldap:/etc/postfix/ldap/virtual_alias_maps.cf flags=lock|fold_fix key=admin@mydomain.com -> status=1 result=
Dec 14 13:45:17 mail postfix/cleanup[5523]: send attr request = lookup
Dec 14 13:45:17 mail postfix/cleanup[5523]: send attr table = ldap:/etc/postfix/ldap/virtual_group_maps.cf
Dec 14 13:45:17 mail postfix/cleanup[5523]: send attr flags = 16448
Dec 14 13:45:17 mail postfix/cleanup[5523]: send attr key = admin@mydomain.com
Dec 14 13:45:17 mail postfix/cleanup[5523]: private/proxymap socket: wanted attribute: status
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute name: status
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute value: 1
Dec 14 13:45:17 mail postfix/cleanup[5523]: private/proxymap socket: wanted attribute: value
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute name: value
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute value: (end)
Dec 14 13:45:17 mail postfix/cleanup[5523]: private/proxymap socket: wanted attribute: (list terminator)
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute name: (end)
Dec 14 13:45:17 mail postfix/cleanup[5523]: dict_proxy_lookup: table=ldap:/etc/postfix/ldap/virtual_group_maps.cf flags=lock|fold_fix key=admin@mydomain.com -> status=1 result=
Dec 14 13:45:17 mail postfix/cleanup[5523]: send attr request = lookup
Dec 14 13:45:17 mail postfix/cleanup[5523]: send attr table = ldap:/etc/postfix/ldap/virtual_group_members_maps.cf
Dec 14 13:45:17 mail postfix/cleanup[5523]: send attr flags = 16448
Dec 14 13:45:17 mail postfix/cleanup[5523]: send attr key = admin@mydomain.com
Dec 14 13:45:17 mail postfix/cleanup[5523]: private/proxymap socket: wanted attribute: status
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute name: status
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute value: 0
Dec 14 13:45:17 mail postfix/cleanup[5523]: private/proxymap socket: wanted attribute: value
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute name: value
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute value: admin@mydomain.com
Dec 14 13:45:17 mail postfix/cleanup[5523]: private/proxymap socket: wanted attribute: (list terminator)
Dec 14 13:45:17 mail postfix/cleanup[5523]: input attribute name: (end)
Dec 14 13:45:17 mail postfix/cleanup[5523]: dict_proxy_lookup: table=ldap:/etc/postfix/ldap/virtual_group_members_maps.cf flags=lock|fold_fix key=admin@mydomain.com -> status=0 result=admin@mydomain.com
Dec 14 13:45:17 mail postfix/cleanup[5523]: maps_find: virtual_alias_maps: proxy:ldap:/etc/postfix/ldap/virtual_group_members_maps.cf(0,lock|fold_fix): admin@mydomain.com = admin@mydomain.com
Dec 14 13:45:17 mail postfix/cleanup[5523]: mail_addr_find: admin@mydomain.com -> admin@mydomain.com
Dec 14 13:45:17 mail postfix/cleanup[5523]: rewrite_clnt: cached: local: admin@mydomain.com -> admin@mydomain.com
Dec 14 13:45:17 mail postfix/cleanup[5523]: mail_addr_map: admin@mydomain.com -> 0: admin@mydomain.com
Dec 14 13:45:17 mail postfix/cleanup[5523]: been_here: admin@mydomain.com: 0
Dec 14 13:45:17 mail postfix/cleanup[5523]: been_here_check: admin@mydomain.com: 1
Dec 14 13:45:17 mail postfix/cleanup[5523]: been_here: admin@mydomain.com: 0
Dec 14 13:45:17 mail postfix/smtpd[5516]: >>> START End-of-data RESTRICTIONS <<<
上面,實際的log 有2200多行, 在開始出現 admin@ 附近的log,我把其節錄出來.
dovecot 未有 log 訊息(dovceot.log ,lda.log ,imap.log , pop3.log), 倒是 iRedApd 有 log
2018-12-14 13:45:17 INFO [209.85.210.45] Client is whitelisted for greylisting service: (id=120867, sender=209.85.128.0/17, comment="AUTO-UPDATE: stackoverflow.com")
2018-12-14 13:45:17 INFO [209.85.210.45] RCPT, rain6966@gmail.com -> test2@mydomain.com, DUNNO [sasl_username=, sender=rain6966@gmail.com, client_name=mail-ot1-f45.google.com, reverse_client_name=mail-ot1-f45.google.com, helo=mail-ot1-f45.google.com, encryption_protocol=TLSv1.2, process_time=0.0138s]
2018-12-14 13:45:17 INFO [209.85.210.45] END-OF-MESSAGE, rain6966@gmail.com -> test2@mydomain.com, DUNNO [recipient_count=1, size=2291, process_time=0.0080s]
lda.log 應該有 ,為何在 13:45 期間沒有出現log? 其它時段進來的信件,在lda.log 是有訊息的.
下面為先前幾天的測試log:
Dec 12 22:06:27 mail dovecot: lda(admin@mydomain.com): sieve: from=rain6966@gmail.com, envelope_sender=rain6966@gmail.com, subject=test bcc, msgid=<947d2bd4-6ed9-d57c-7199-404d06bbec8b@gmail.com>, size=3870, stored mail into mailbox 'INBOX'
Dec 12 22:06:30 mail dovecot: lda(test@mydomain.com): sieve: from=rain6966@gmail.com, envelope_sender=rain6966@gmail.com, subject=test bcc, msgid=<947d2bd4-6ed9-d57c-7199-404d06bbec8b@gmail.com>, size=3843, stored mail into mailbox 'INBOX'
Dec 12 22:32:52 mail dovecot: lda(admin@mydomain.com): sieve: from=rain6966@gmail.com, envelope_sender=rain6966@gmail.com, subject=For test BCC 測試, msgid=<CAOAF3wkvS5vNeV7o2k=q8VH8VE7a__BM+Nchsm0TciMh_oXwzw@mail.gmail.com>, size=3289, stored mail into mailbox 'INBOX'
Dec 12 22:32:52 mail dovecot: lda(test@mydomain.com): sieve: from=rain6966@gmail.com, envelope_sender=rain6966@gmail.com, subject=For test BCC 測試, msgid=<CAOAF3wkvS5vNeV7o2k=q8VH8VE7a__BM+Nchsm0TciMh_oXwzw@mail.gmail.com>, size=3262, stored mail into mailbox 'INBOX'
Dec 12 23:22:18 mail dovecot: lda(admin@mydomain.com): sieve: from=rain6966@gmail.com, envelope_sender=rain6966@gmail.com, subject=test for BCC 測試2, msgid=<CAOAF3w=dw4gvk1DOqfgMBq5UV2MgA6++XpDAP+OUT0184aNWpA@mail.gmail.com>, size=3129, stored mail into mailbox 'INBOX'
Dec 12 23:22:18 mail dovecot: lda(test4@mydomain.com): sieve: from=rain6966@gmail.com, envelope_sender=rain6966@gmail.com, subject=test for BCC 測試2, msgid=<CAOAF3w=dw4gvk1DOqfgMBq5UV2MgA6++XpDAP+OUT0184aNWpA@mail.gmail.com>, size=3105, stored mail into mailbox 'INBOX'
以上為現所能提供的訊息 .
Hi 版主:
1),
查看 英文論壇 ,有人提問
"Duplicate emails in Outlook"
https://forum.iredmail.org/post66623.html#p66623
2),
和早先我提問的 "無法取消 BCC" (現已關閉)
那時我是發現Gateway 防火牆的問題 , 但我事後發現問題仍在 .
3),
系統CentOS7 , 目前已重新安裝2次了.
昨晚試著使用再早一版本 iRedAdmin-Pro-LDAP-3.0
a). BCC , 網域不啟動 , user 不啟動
無信件重複問題 (bcc 帳戶 admin@ 沒有收到另一份信件)
今早察看 user@ 收到幾封dovecot 論壇上的信, admin@ 則沒有
b).BCC , 網域啟動 , user 不啟動
信件重複 : (bcc 帳戶 admin@ 收到另一份不應收到的信件)
今試著 使用 Pro-3.0 或 Pro-3.1 皆一樣.
但有一點奇怪的 ,也許是自己搞混.
剛開始 Pro-3.0 是正常 ,admin@ 不會收到 ,
重覆幾次切換Pro版本後 ,admin@ 則會收到 ,變成不正常!
英文論壇提問的問題, 若把BCC 停用(若其有啟用) , 那就和我這的問題一樣了.
(但其是每個user 重複 , 那可就不一樣了)
BCC 啟用 , 造成信件重複 (只有BCC 帳號 admm@ , 收到不想收到的信) ,
停止網域使用 BCC , 那信件的備份目的則無法達成.
版主 , 可還有其它方法排除此問題?
感謝.
Hi , 版主:
iRedMail-0.9.8 里的 tools/create_mail_user_* 脚本没有同步更新,但是 iRedAdmin-Pro 则是更新了的。
是我不查 , 安裝的iRedAdmin-Pro版使用到 2018/04/09 的版本 , 正確應為2018/07/23 , 確實是有更新到. 對不起.
感謝.
現再重新安裝 iRedMail-0.9.8 一遍 , 發現
postmaster@ 此帳號也一樣缺少此參數.
但 在 iRedAdmin-0.9.1 (非PRO版) ,新建帳號 , 則無缺少此兩參數.
全新安裝 iRedMail-0.9.8 , 產生的比較結果.
Hi 版主:
很對不起, 經我重新安裝後, 測試還是一樣 , 不過最後我發現是我公司的防火牆造成的.
在防火牆 (公司的Gateway上)設定log訊息寄送,
不可設定為 網域內帳號 , 不然造成iRedMail 的BCC帳號皆會收到網域內所有收,發件者的一份信件(不管啟用或沒啟用的帳號).
防火牆上的收,發件帳號 只能設為 root@mail.mydomain.com (mail.mydomain.com 是郵件伺服器名稱)
感謝,
1).手動建立帳號:
/root/iRedMail-0.9.8/tools/create_mail_user_OpenLDAP.py
/root/iRedMail-0.9.8/tools/create_mail_user_OpenLDAP.sh
2).
iRedAdmin-Pro 創建的帳號
比較兩種方式, 產生的LDIF檔, 後者少了
enabledservice: pop3tls
enabledservice: imaptls
我上DNSBL查詢辦公室的上網IP,發現有被幾個網站給BLOCK起來,我也嘗試去申請解除,但是有些網站的回覆是需要透過ISP去解除...
而且公司用的又是動態IP上網....總不可能每次有問題我都要一個個去解(目前正在申請改為Static IP...)
rain6966 写道:jimmyfangtw 写道:Mail Server不在我們辦公室
那主機在哪? 是託管在ISP?
您公司對外使用動態IP? 改固定的可避免被ISP 擋住.請參考.
Mail Server使用的是固定IP沒錯
我是說 :
公司內部對外IP為動態IP(Gateway)? ,寄放在ISP的Mail Server,因 ISP針對Gateway IP做阻擋?
iRedMail 本身內建 DNSBL 機制 及 ISP 都有可能把您公司對外的IP 加入黑名單.
前文 "目前正在申請改為Static IP..." , 那就快快去申請 , 問題也許就解決了.
BCC incoming emails to other address
BCC outgoing emails to other address
其為空白, 我記的以前我曾反應, 當建立新帳號時 ,上面兩欄會直接套用網域的的設定值
現在的版本有改了?
請問版主:
有關BCC 的設定:
在Profile of domain : 有BCC欄位 ,及Advanced欄位,
在Profile of user: 有Advanced欄位,
在設定上,Profile of user 裡已告之, user 的權限大於 domain.這我是了解.
但在Profile of domain裡 , BCC 及Advanced 能整併成一欄位? BCC欄位 感覺重複.
再試著把 Forwarding ,取消掉時, 發現下面的問題:
Profile of user: > Forwarding >Enable mail forwarding 打勾無效
(iRedAdmin 預設值是打勾)下面 , Advance > 預設值是已打勾了.但在 Profile of user: >Advanced >Forwarding mails to other addresses ,取消打勾後 ,上面 Forwarding >Enable mail forwarding 直接跟著取消打勾 .
無法在 Forwarding 裡設定 , 需在 Advanced 裡設定.
請問舨主:
Forwarding 的設定 , 正確的設法是在 Advanced 裡設定?
iRedMail 开源邮件服务解决方案 » 由 rain6966 发表的文章
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2010 PunBB.
页面生成时间 0.023 秒, 共执行查询 51 条