mailu / helm-charts

Development repo for helm charts

Mailu is a simple yet full-featured mail server as a set of Docker images. It is free software (both as in free beer and as in free speech), open to suggestions and external contributions. The project aims at providing people with an easily setup, easily maintained and full-featured mail server while not shipping proprietary software nor unrelated features often found in popular groupware.

Most of the documentation is available on our Website, you can also try our demo server before setting up your own, and come talk to us on Matrix.

Features

Main features include:

• Standard email server, IMAP and IMAP+, SMTP and Submission with auto-configuration profiles for clients
• Advanced email features, aliases, domain aliases, custom routing, full-text search of email attachments
• Web access, multiple Webmails and administration interface
• User features, aliases, auto-reply, auto-forward, fetched accounts, managesieve
• Admin features, global admins, announcements, per-domain delegation, quotas
• Security, enforced TLS, DANE, MTA-STS, Letsencrypt!, outgoing DKIM, anti-virus scanner, Snuffleupagus, block malicious attachments
• Antispam, auto-learn, greylisting, DMARC and SPF, anti-spoofing
• Freedom, all FOSS components, no tracker included

Contributing

Mailu is free software, open to suggestions and contributions. All components are free software and compatible with the MIT license. All specific configuration files, Dockerfiles and code are placed under the MIT license.

helm-charts's Issues

relay abuse through SRS

Hi all,

I had a strange case of thousand of mails being relayed by mailu for a user that does'nt exist, here are the logs from postfix:

Apr 21 08:45:13 mail postfix/qmgr[120]: E769AAA02A0: from=<[email protected]>, size=9611, nrcpt=1 (queue active)
Apr 21 08:45:13 mail postfix/qmgr[120]: EEEA9AA0070: from=<[email protected]>, size=9633, nrcpt=1 (queue active)
Apr 21 08:45:13 mail postfix/qmgr[120]: 237ACAA0066: from=<[email protected]>, size=9629, nrcpt=1 (queue active)
Apr 21 08:45:13 mail postfix/qmgr[120]: 2FB79AA029F: from=<[email protected]>, size=9625, nrcpt=1 (queue active)
Apr 21 08:45:14 mail postfix/qmgr[120]: 2EC47AA0067: from=<[email protected]>, size=9649, nrcpt=1 (queue active)
Apr 21 08:45:14 mail postfix/qmgr[120]: 237BAAA0519: from=<[email protected]>, size=9685, nrcpt=1 (queue active)
Apr 21 08:45:14 mail postfix/qmgr[120]: 192BFAA02A2: from=<[email protected]>, size=9641, nrcpt=1 (queue active)
Apr 21 08:45:14 mail postfix/qmgr[120]: 13BCDAA006D: from=<[email protected]>, size=9625, nrcpt=1 (queue active)
Apr 21 08:45:14 mail postfix/qmgr[120]: 17EEFAA029E: from=<[email protected]>, size=9633, nrcpt=1 (queue active)
Apr 21 08:45:14 mail postfix/qmgr[120]: DD82BAA03D8: from=<[email protected]>, size=9639, nrcpt=1 (queue active)
Apr 21 08:45:14 mail postfix/qmgr[120]: D7F57AA0522: from=<[email protected]>, size=9625, nrcpt=1 (queue active)
Apr 21 08:45:14 mail postfix/qmgr[120]: D8EA3AA03E3: from=<[email protected]>, size=9625, nrcpt=1 (queue active)
Apr 21 08:45:14 mail postfix/qmgr[120]: D96C8AA03DE: from=<[email protected]>, size=9664, nrcpt=1 (queue active)
Apr 21 08:45:14 mail postfix/qmgr[120]: D4CFBAA0061: from=<[email protected]>, size=9635, nrcpt=1 (queue active)
Apr 21 08:45:14 mail postfix/smtp[1267]: E7F53AA03D9: to=<[email protected]>, relay=smtp.distamex.com.mx[149.56.16.214]:25, delay=55009, delays=55008/0.13/0.8/0.21, dsn=4.0.0, status=deferred (host smtp.distamex.com.mx[149.56.16.214] said: 451 http://www.barracudanetworks.com/reputation/?pr=1&ip=78.225.183.108 (in reply to RCPT TO command))
Apr 21 08:45:14 mail postfix/qmgr[120]: D85D1AA02B5: from=<[email protected]>, size=9663, nrcpt=1 (queue active)
Apr 21 08:45:14 mail postfix/smtp[1278]: 13BCDAA006D: host mx2.sap.c3s2.iphmx.com[68.232.156.178] refused to talk to me: 554-esa9.sap.c3s2.iphmx.com 554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.
Apr 21 08:45:14 mail postfix/smtp[1277]: 192BFAA02A2: host mail2.gan.com.mx[207.248.158.23] refused to talk to me: 554 ironport2.ahmsa.com
Apr 21 08:45:14 mail postfix/qmgr[120]: 9375AAA03E1: from=<[email protected]>, size=9649, nrcpt=1 (queue active)
Apr 21 08:45:14 mail postfix/smtp[1269]: EC1BFAA0063: host mta6.am0.yahoodns.net[98.136.96.74] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:14 mail postfix/smtp[1269]: EC1BFAA0063: lost connection with mta6.am0.yahoodns.net[98.136.96.74] while sending RCPT TO
Apr 21 08:45:14 mail postfix/smtp[1271]: E769AAA02A0: host mta6.am0.yahoodns.net[67.195.204.77] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:14 mail postfix/smtp[1271]: E769AAA02A0: lost connection with mta6.am0.yahoodns.net[67.195.204.77] while sending RCPT TO
Apr 21 08:45:14 mail postfix/qmgr[120]: 9625EAA05A8: from=<[email protected]>, size=9649, nrcpt=1 (queue active)
Apr 21 08:45:14 mail postfix/smtp[1278]: 13BCDAA006D: host mx1.sap.c3s2.iphmx.com[68.232.151.193] refused to talk to me: 554-esa6.sap.c3s2.iphmx.com 554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.
Apr 21 08:45:14 mail postfix/qmgr[120]: 9A931AA050D: from=<[email protected]>, size=9645, nrcpt=1 (queue active)
Apr 21 08:45:14 mail postfix/smtp[1278]: 13BCDAA006D: host mx2.sap.c3s2.iphmx.com[68.232.156.216] refused to talk to me: 554-esa17.sap.c3s2.iphmx.com 554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.
Apr 21 08:45:14 mail postfix/qmgr[120]: 9BD0AAA02A3: from=<[email protected]>, size=9607, nrcpt=1 (queue active)
Apr 21 08:45:14 mail postfix/qmgr[120]: 9AC40AA03D7: from=<[email protected]>, size=9635, nrcpt=1 (queue active)
Apr 21 08:45:15 mail postfix/smtp[1278]: 13BCDAA006D: host mx1.sap.c3s2.iphmx.com[68.232.159.191] refused to talk to me: 554-esa3.sap.c3s2.iphmx.com 554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.
Apr 21 08:45:15 mail postfix/smtp[1268]: E3FE9AA02A7: to=<[email protected]>, relay=asurisamex2.asur.com.mx[187.141.67.52]:25, delay=59157, delays=59155/0.12/1.4/0, dsn=4.0.0, status=deferred (host asurisamex2.asur.com.mx[187.141.67.52] refused to talk to me: 554-cunitesapr01.asur.com 554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.)
Apr 21 08:45:15 mail postfix/qmgr[120]: 980E0AA03D2: from=<[email protected]>, size=9621, nrcpt=1 (queue active)
Apr 21 08:45:15 mail postfix/smtp[1281]: connect to hotmail.com.mx[200.94.181.11]:25: Connection refused
Apr 21 08:45:15 mail postfix/smtp[1266]: E583AAA03CC: host mta5.am0.yahoodns.net[67.195.228.110] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:15 mail postfix/smtp[1266]: E583AAA03CC: lost connection with mta5.am0.yahoodns.net[67.195.228.110] while sending RCPT TO
Apr 21 08:45:15 mail postfix/smtp[1277]: 192BFAA02A2: to=<[email protected]>, relay=mail.gan.com.mx[207.248.158.22]:25, delay=59189, delays=59188/0.11/0.85/0, dsn=4.0.0, status=deferred (host mail.gan.com.mx[207.248.158.22] refused to talk to me: 554 ironport.ahmsa.com)
Apr 21 08:45:15 mail postfix/smtp[1272]: EEEA9AA0070: host mx08-00096701.pphosted.com[91.207.212.1] refused to talk to me: 554 Blocked - see https://ipcheck.proofpoint.com/?ip=78.225.183.108
Apr 21 08:45:15 mail postfix/smtp[1282]: D8EA3AA03E3: host maila.correoexchange.mx[200.57.129.1] refused to talk to me: 554-maila.triara.com 554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.
Apr 21 08:45:15 mail postfix/qmgr[120]: 88823AA0514: from=<[email protected]>, size=9661, nrcpt=1 (queue active)
Apr 21 08:45:15 mail postfix/qmgr[120]: 811E4AA02B2: from=<[email protected]>, size=9643, nrcpt=1 (queue active)
Apr 21 08:45:15 mail postfix/smtp[1281]: connect to hotmail.com.mx[200.94.181.10]:25: Connection refused
Apr 21 08:45:15 mail postfix/smtp[1276]: 237BAAA0519: to=<[email protected]>, relay=mail.mail219.atl101.mcdlv.net[198.2.130.219]:25, delay=46439, delays=46437/0.1/0.97/0.13, dsn=4.7.1, status=deferred (host mail.mail219.atl101.mcdlv.net[198.2.130.219] said: 454 4.7.1 <[email protected]>: Relay access denied (in reply to RCPT TO command))
Apr 21 08:45:15 mail postfix/smtp[1274]: 2FB79AA029F: host correo5.televisa.com.mx[200.13.34.23] refused to talk to me: 554 correo5.televisa.com.mx
Apr 21 08:45:15 mail postfix/qmgr[120]: 81B7BAA03E9: from=<[email protected]>, size=9631, nrcpt=1 (queue active)
Apr 21 08:45:15 mail postfix/smtp[1270]: E7B0CAA03D5: to=<[email protected]>, relay=mailrelay5.vw.com.mx[148.203.151.248]:25, delay=54948, delays=54946/0.16/1.5/0, dsn=4.0.0, status=deferred (host mailrelay5.vw.com.mx[148.203.151.248] refused to talk to me: 554-mailrelay3.vw.com.mx 554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means. 78.225.183.108)
Apr 21 08:45:15 mail postfix/smtp[1286]: D85D1AA02B5: host smtp.secureserver.net[68.178.213.203] refused to talk to me: 554 p3plibsmtp03-10.prod.phx3.secureserver.net CMGW IB103. Connection refused. 78.225.183.108 has a poor reputation on Cloudmark Sender Intelligence (CSI). Please visit http://csi.cloudmark.com/reset-request/?ip=78.225.183.108 to request a delisting.
Apr 21 08:45:15 mail postfix/smtp[1272]: EEEA9AA0070: to=<[email protected]>, relay=mx07-00096701.pphosted.com[62.209.51.1]:25, delay=63240, delays=63238/0.11/1.4/0, dsn=4.0.0, status=deferred (host mx07-00096701.pphosted.com[62.209.51.1] refused to talk to me: 554 Blocked - see https://ipcheck.proofpoint.com/?ip=78.225.183.108)
Apr 21 08:45:15 mail postfix/qmgr[120]: 8D10DAA03DC: from=<[email protected]>, size=9619, nrcpt=1 (queue active)
Apr 21 08:45:15 mail postfix/smtp[1281]: connect to hotmail.com.mx[200.94.181.9]:25: Connection refused
Apr 21 08:45:15 mail postfix/smtp[1281]: D7F57AA0522: to=<[email protected]>, relay=none, delay=46376, delays=46375/0.12/0.98/0, dsn=4.4.1, status=deferred (connect to hotmail.com.mx[200.94.181.9]:25: Connection refused)
Apr 21 08:45:15 mail postfix/qmgr[120]: 86863AA02AA: from=<[email protected]>, size=9605, nrcpt=1 (queue active)
Apr 21 08:45:15 mail postfix/smtp[1278]: 13BCDAA006D: to=<[email protected]>, relay=mx1.sap.c3s2.iphmx.com[68.232.159.172]:25, delay=63211, delays=63210/0.12/1.2/0, dsn=4.0.0, status=deferred (host mx1.sap.c3s2.iphmx.com[68.232.159.172] refused to talk to me: 554-esa1.sap.c3s2.iphmx.com 554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.)
Apr 21 08:45:15 mail postfix/smtp[1282]: D8EA3AA03E3: to=<[email protected]>, relay=mailb.correoexchange.mx[200.57.129.2]:25, delay=54871, delays=54870/0.12/1/0, dsn=4.0.0, status=deferred (host mailb.correoexchange.mx[200.57.129.2] refused to talk to me: 554-maila.triara.com 554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.)
Apr 21 08:45:15 mail postfix/smtp[1273]: 237ACAA0066: host mx-aol.mail.gm0.yahoodns.net[67.195.228.84] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:15 mail postfix/smtp[1273]: 237ACAA0066: lost connection with mx-aol.mail.gm0.yahoodns.net[67.195.228.84] while sending RCPT TO
Apr 21 08:45:15 mail postfix/qmgr[120]: 84388AA0343: from=<[email protected]>, size=9619, nrcpt=1 (queue active)
Apr 21 08:45:15 mail postfix/smtp[1283]: D96C8AA03DE: host mta7.am0.yahoodns.net[98.136.96.75] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:15 mail postfix/smtp[1283]: D96C8AA03DE: lost connection with mta7.am0.yahoodns.net[98.136.96.75] while sending RCPT TO
Apr 21 08:45:15 mail postfix/smtp[1274]: 2FB79AA029F: host correo2.televisa.com.mx[201.175.2.28] refused to talk to me: 554 correo2.televisa.com.mx
Apr 21 08:45:15 mail postfix/qmgr[120]: 84E88AA029C: from=<[email protected]>, size=9627, nrcpt=1 (queue active)
Apr 21 08:45:15 mail postfix/smtp[1286]: D85D1AA02B5: host smtp.secureserver.net[72.167.238.29] refused to talk to me: 554 p3plibsmtp01-14.prod.phx3.secureserver.net CMGW IB103. Connection refused. 78.225.183.108 has a poor reputation on Cloudmark Sender Intelligence (CSI). Please visit http://csi.cloudmark.com/reset-request/?ip=78.225.183.108 to request a delisting.
Apr 21 08:45:15 mail postfix/qmgr[120]: 8DD71AA0515: from=<[email protected]>, size=9651, nrcpt=1 (queue active)
Apr 21 08:45:15 mail postfix/qmgr[120]: 85272AA02B8: from=<[email protected]>, size=9643, nrcpt=1 (queue active)
Apr 21 08:45:15 mail postfix/smtp[1269]: EC1BFAA0063: to=<[email protected]>, relay=mta7.am0.yahoodns.net[98.136.96.77]:25, delay=63395, delays=63393/0.13/1.9/0.14, dsn=4.7.0, status=deferred (host mta7.am0.yahoodns.net[98.136.96.77] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:15 mail postfix/smtp[1268]: 980E0AA03D2: host mailb.exchangeadministrado.com[200.57.129.68] refused to talk to me: 554-maila.triara.com 554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.
Apr 21 08:45:15 mail postfix/qmgr[120]: 8BA2CAA0319: from=<>, size=6005, nrcpt=1 (queue active)
Apr 21 08:45:15 mail postfix/qmgr[120]: 6B69FAA03E6: from=<[email protected]>, size=9637, nrcpt=1 (queue active)
Apr 21 08:45:16 mail postfix/smtp[1274]: 2FB79AA029F: host correo3.televisa.com.mx[201.175.2.27] refused to talk to me: 554 correo3.televisa.com.mx
Apr 21 08:45:16 mail postfix/qmgr[120]: 64952AA051D: from=<[email protected]>, size=9599, nrcpt=1 (queue active)
Apr 21 08:45:16 mail postfix/smtp[1286]: D85D1AA02B5: host smtp.secureserver.net[68.178.213.37] refused to talk to me: 554 p3plibsmtp02-12.prod.phx3.secureserver.net CMGW IB103. Connection refused. 78.225.183.108 has a poor reputation on Cloudmark Sender Intelligence (CSI). Please visit http://csi.cloudmark.com/reset-request/?ip=78.225.183.108 to request a delisting.
Apr 21 08:45:16 mail postfix/smtp[1271]: E769AAA02A0: to=<[email protected]>, relay=mta7.am0.yahoodns.net[67.195.228.109]:25, delay=59227, delays=59224/0.14/2/0.17, dsn=4.7.0, status=deferred (host mta7.am0.yahoodns.net[67.195.228.109] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:16 mail postfix/smtp[1266]: E583AAA03CC: to=<[email protected]>, relay=mta7.am0.yahoodns.net[98.136.96.74]:25, delay=55055, delays=55052/0.15/2.4/0.13, dsn=4.7.0, status=deferred (host mta7.am0.yahoodns.net[98.136.96.74] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:16 mail postfix/qmgr[120]: 686BEAA0068: from=<[email protected]>, size=9679, nrcpt=1 (queue active)
Apr 21 08:45:16 mail postfix/smtp[1268]: 980E0AA03D2: to=<[email protected]>, relay=maila.exchangeadministrado.com[200.57.129.67]:25, delay=55037, delays=55036/0.13/1/0, dsn=4.0.0, status=deferred (host maila.exchangeadministrado.com[200.57.129.67] refused to talk to me: 554-maila.triara.com 554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.)
Apr 21 08:45:16 mail postfix/smtp[1291]: 811E4AA02B2: host mta6.am0.yahoodns.net[67.195.204.77] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:16 mail postfix/smtp[1291]: 811E4AA02B2: lost connection with mta6.am0.yahoodns.net[67.195.204.77] while sending RCPT TO
Apr 21 08:45:16 mail postfix/qmgr[120]: 670E6AA0517: from=<[email protected]>, size=9657, nrcpt=1 (queue active)
Apr 21 08:45:16 mail postfix/smtp[1288]: 9A931AA050D: host mta6.am0.yahoodns.net[67.195.228.109] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:16 mail postfix/smtp[1288]: 9A931AA050D: lost connection with mta6.am0.yahoodns.net[67.195.228.109] while sending RCPT TO
Apr 21 08:45:16 mail postfix/smtp[1274]: 2FB79AA029F: to=<[email protected]>, relay=correo4.televisa.com.mx[200.10.200.210]:25, delay=59235, delays=59232/0.12/2.2/0, dsn=4.0.0, status=deferred (host correo4.televisa.com.mx[200.10.200.210] refused to talk to me: 554 correo4.televisa.com.mx)
Apr 21 08:45:16 mail postfix/qmgr[120]: 69683AA0518: from=<[email protected]>, size=9647, nrcpt=1 (queue active)
Apr 21 08:45:16 mail postfix/smtp[1286]: D85D1AA02B5: host mailstore1.secureserver.net[68.178.213.243] refused to talk to me: 554 p3plibsmtp02-14.prod.phx3.secureserver.net CMGW IB103. Connection refused. 78.225.183.108 has a poor reputation on Cloudmark Sender Intelligence (CSI). Please visit http://csi.cloudmark.com/reset-request/?ip=78.225.183.108 to request a delisting.
Apr 21 08:45:16 mail postfix/qmgr[120]: 6C6E3AA0072: from=<[email protected]>, size=9629, nrcpt=1 (queue active)
Apr 21 08:45:16 mail postfix/qmgr[120]: 6C391AA02AB: from=<[email protected]>, size=9605, nrcpt=1 (queue active)
Apr 21 08:45:16 mail postfix/smtp[1283]: D96C8AA03DE: to=<[email protected]>, relay=mta6.am0.yahoodns.net[67.195.204.72]:25, delay=54959, delays=54957/0.14/1.8/0.1, dsn=4.7.0, status=deferred (host mta6.am0.yahoodns.net[67.195.204.72] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:16 mail postfix/qmgr[120]: 641CBAA051A: from=<[email protected]>, size=9647, nrcpt=1 (queue active)
Apr 21 08:45:16 mail postfix/qmgr[120]: 6DB83AA0073: from=<[email protected]>, size=9597, nrcpt=1 (queue active)
Apr 21 08:45:16 mail postfix/qmgr[120]: 6DDA7AA051B: from=<[email protected]>, size=9645, nrcpt=1 (queue active)
Apr 21 08:45:16 mail postfix/qmgr[120]: 05743AA02AC: from=<[email protected]>, size=9629, nrcpt=1 (queue active)
Apr 21 08:45:16 mail postfix/smtp[1286]: D85D1AA02B5: to=<[email protected]>, relay=mailstore1.secureserver.net[68.178.213.244]:25, delay=58985, delays=58983/0.15/2/0, dsn=4.0.0, status=deferred (host mailstore1.secureserver.net[68.178.213.244] refused to talk to me: 554 p3plibsmtp03-08.prod.phx3.secureserver.net CMGW IB103. Connection refused. 78.225.183.108 has a poor reputation on Cloudmark Sender Intelligence (CSI). Please visit http://csi.cloudmark.com/reset-request/?ip=78.225.183.108 to request a delisting.)
Apr 21 08:45:16 mail postfix/smtp[1273]: 237ACAA0066: to=<[email protected]>, relay=mx-aol.mail.gm0.yahoodns.net[67.195.228.86]:25, delay=63400, delays=63397/0.12/2.7/0.17, dsn=4.7.0, status=deferred (host mx-aol.mail.gm0.yahoodns.net[67.195.228.86] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:17 mail postfix/qmgr[120]: 02746AA02A8: from=<[email protected]>, size=9643, nrcpt=1 (queue active)
Apr 21 08:45:17 mail postfix/smtp[1282]: 84E88AA029C: host mta7.am0.yahoodns.net[67.195.228.110] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:17 mail postfix/smtp[1282]: 84E88AA029C: lost connection with mta7.am0.yahoodns.net[67.195.228.110] while sending RCPT TO
Apr 21 08:45:17 mail postfix/smtp[1266]: 64952AA051D: host mx02.mail.icloud.com[17.57.154.7] refused to talk to me: 550 5.7.0 Blocked - see https://support.proofpoint.com/dnsbl-lookup.cgi?ip=78.225.183.108
Apr 21 08:45:17 mail postfix/qmgr[120]: 0DDCFAA03ED: from=<[email protected]>, size=9639, nrcpt=1 (queue active)
Apr 21 08:45:17 mail postfix/smtp[1291]: 811E4AA02B2: to=<[email protected]>, relay=mta6.am0.yahoodns.net[67.195.204.73]:25, delay=59018, delays=59016/0.18/1.5/0.1, dsn=4.7.0, status=deferred (host mta6.am0.yahoodns.net[67.195.204.73] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:17 mail postfix/smtp[1278]: 85272AA02B8: host mxa-00145802.gslb.pphosted.com[67.231.156.189] refused to talk to me: 554 Blocked - see https://ipcheck.proofpoint.com/?ip=78.225.183.108
Apr 21 08:45:17 mail postfix/smtp[1276]: 86863AA02AA: to=<[email protected]>, relay=mail.adosa.com.mx[200.76.134.130]:25, delay=59104, delays=59103/0.08/1.6/0, dsn=4.4.2, status=deferred (lost connection with mail.adosa.com.mx[200.76.134.130] while performing the HELO handshake)
Apr 21 08:45:17 mail postfix/qmgr[120]: 3CE3CAA051C: from=<[email protected]>, size=9659, nrcpt=1 (queue active)
Apr 21 08:45:17 mail postfix/smtp[1269]: 8BA2CAA0319: host mta6.am0.yahoodns.net[67.195.228.109] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:17 mail postfix/smtp[1269]: 8BA2CAA0319: lost connection with mta6.am0.yahoodns.net[67.195.228.109] while sending RCPT TO
Apr 21 08:45:17 mail postfix/qmgr[120]: 3815CAA03E8: from=<[email protected]>, size=9667, nrcpt=1 (queue active)
Apr 21 08:45:17 mail postfix/qmgr[120]: 390A6AA0071: from=<[email protected]>, size=9643, nrcpt=1 (queue active)
Apr 21 08:45:17 mail postfix/smtp[1278]: 85272AA02B8: to=<[email protected]>, relay=mxb-00145802.gslb.pphosted.com[67.231.156.189]:25, delay=58978, delays=58977/0.15/1.5/0, dsn=4.0.0, status=deferred (host mxb-00145802.gslb.pphosted.com[67.231.156.189] refused to talk to me: 554 Blocked - see https://ipcheck.proofpoint.com/?ip=78.225.183.108)
Apr 21 08:45:17 mail postfix/smtp[1266]: 64952AA051D: host mx01.mail.icloud.com[17.56.9.17] refused to talk to me: 550 5.7.0 Blocked - see https://support.proofpoint.com/dnsbl-lookup.cgi?ip=78.225.183.108
Apr 21 08:45:17 mail postfix/smtp[1283]: 6C6E3AA0072: host mta6.am0.yahoodns.net[67.195.204.77] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:17 mail postfix/smtp[1283]: 6C6E3AA0072: lost connection with mta6.am0.yahoodns.net[67.195.204.77] while sending RCPT TO
Apr 21 08:45:17 mail postfix/qmgr[120]: 5C9EEAA03DD: from=<[email protected]>, size=9639, nrcpt=1 (queue active)
Apr 21 08:45:17 mail postfix/smtp[1297]: 6DB83AA0073: host mx0b-00191d01.pphosted.com[67.231.157.136] refused to talk to me: 554 Blocked - see https://ipcheck.proofpoint.com/?ip=78.225.183.108
Apr 21 08:45:17 mail postfix/smtp[1295]: 6C391AA02AB: host mx-aol.mail.gm0.yahoodns.net[67.195.204.80] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:17 mail postfix/smtp[1295]: 6C391AA02AB: lost connection with mx-aol.mail.gm0.yahoodns.net[67.195.204.80] while sending RCPT TO
Apr 21 08:45:17 mail postfix/smtpd[187]: connect from localhost[127.0.0.1]
Apr 21 08:45:17 mail postfix/smtpd[187]: disconnect from localhost[127.0.0.1] quit=1 commands=1
Apr 21 08:45:17 mail postfix/qmgr[120]: 57FBFAA0512: from=<[email protected]>, size=9641, nrcpt=1 (queue active)
Apr 21 08:45:17 mail postfix/qmgr[120]: 5C75FAA03E2: from=<[email protected]>, size=9635, nrcpt=1 (queue active)
Apr 21 08:45:17 mail postfix/qmgr[120]: 532F0AA03DB: from=<[email protected]>, size=9639, nrcpt=1 (queue active)
Apr 21 08:45:17 mail postfix/smtp[1271]: 8DD71AA0515: host mta5.am0.yahoodns.net[67.195.228.106] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:17 mail postfix/smtp[1271]: 8DD71AA0515: lost connection with mta5.am0.yahoodns.net[67.195.228.106] while sending RCPT TO
Apr 21 08:45:17 mail postfix/smtp[1288]: 9A931AA050D: to=<[email protected]>, relay=mta5.am0.yahoodns.net[67.195.228.110]:25, delay=46658, delays=46655/0.11/2.5/0.17, dsn=4.7.0, status=deferred (host mta5.am0.yahoodns.net[67.195.228.110] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:17 mail postfix/qmgr[120]: 5028AAA0203: from=<[email protected]>, size=9625, nrcpt=1 (queue active)
Apr 21 08:45:17 mail postfix/smtp[1294]: 69683AA0518: host mta6.am0.yahoodns.net[67.195.228.109] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:17 mail postfix/smtp[1294]: 69683AA0518: lost connection with mta6.am0.yahoodns.net[67.195.228.109] while sending RCPT TO
Apr 21 08:45:17 mail postfix/smtp[1266]: 64952AA051D: host mx01.mail.icloud.com[17.57.152.9] refused to talk to me: 550 5.7.0 Blocked - see https://support.proofpoint.com/dnsbl-lookup.cgi?ip=78.225.183.108
Apr 21 08:45:17 mail postfix/smtp[1282]: 84E88AA029C: to=<[email protected]>, relay=mta7.am0.yahoodns.net[67.195.204.73]:25, delay=59250, delays=59248/0.05/2.1/0.11, dsn=4.7.0, status=deferred (host mta7.am0.yahoodns.net[67.195.204.73] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:17 mail postfix/qmgr[120]: 5BE37AA0204: from=<[email protected]>, size=9635, nrcpt=1 (queue active)
Apr 21 08:45:17 mail postfix/smtpd[318]: connect from localhost[127.0.0.1]
Apr 21 08:45:17 mail postfix/smtpd[318]: disconnect from localhost[127.0.0.1] quit=1 commands=1
Apr 21 08:45:17 mail postfix/smtp[1299]: 3815CAA03E8: host correo2.televisa.com.mx[201.175.2.28] refused to talk to me: 554 correo2.televisa.com.mx
Apr 21 08:45:17 mail postfix/smtp[1276]: 3CE3CAA051C: host mailb.exchangeadministrado.com[200.57.129.68] refused to talk to me: 554-maila.triara.com 554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.
Apr 21 08:45:18 mail postfix/error[1311]: 5028AAA0203: to=<[email protected]>, relay=none, delay=61344, delays=61344/0.26/0/0.01, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to pep.pemex.com[200.23.91.68]:25: Operation timed out)
Apr 21 08:45:18 mail postfix/qmgr[120]: 48B65AA03E0: from=<[email protected]>, size=9631, nrcpt=1 (queue active)
Apr 21 08:45:18 mail postfix/smtp[1297]: 6DB83AA0073: to=<[email protected]>, relay=mx0a-00191d01.pphosted.com[67.231.149.140]:25, delay=63227, delays=63226/0.17/1.3/0, dsn=4.0.0, status=deferred (host mx0a-00191d01.pphosted.com[67.231.149.140] refused to talk to me: 554 Blocked - see https://ipcheck.proofpoint.com/?ip=78.225.183.108)
Apr 21 08:45:18 mail postfix/qmgr[120]: 4F5ECAA02B0: from=<[email protected]>, size=9621, nrcpt=1 (queue active)
Apr 21 08:45:18 mail postfix/smtp[1266]: 64952AA051D: host mx02.mail.icloud.com[17.56.9.19] refused to talk to me: 550 5.7.0 Blocked - see https://support.proofpoint.com/dnsbl-lookup.cgi?ip=78.225.183.108
Apr 21 08:45:18 mail postfix/smtp[1291]: 0DDCFAA03ED: host mta7.am0.yahoodns.net[98.136.96.74] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:18 mail postfix/smtp[1291]: 0DDCFAA03ED: lost connection with mta7.am0.yahoodns.net[98.136.96.74] while sending RCPT TO
Apr 21 08:45:18 mail postfix/qmgr[120]: 414FDAA01E8: from=<[email protected]>, size=9619, nrcpt=1 (queue active)
Apr 21 08:45:18 mail postfix/qmgr[120]: 4A354AA02A6: from=<[email protected]>, size=9637, nrcpt=1 (queue active)
Apr 21 08:45:18 mail postfix/smtp[1299]: 3815CAA03E8: host correo4.televisa.com.mx[200.10.200.210] refused to talk to me: 554 correo4.televisa.com.mx
Apr 21 08:45:18 mail postfix/smtp[1283]: 6C6E3AA0072: to=<[email protected]>, relay=mta6.am0.yahoodns.net[67.195.204.72]:25, delay=63256, delays=63255/0.11/1.7/0.12, dsn=4.7.0, status=deferred (host mta6.am0.yahoodns.net[67.195.204.72] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:18 mail postfix/smtp[1276]: 3CE3CAA051C: to=<[email protected]>, relay=maila.exchangeadministrado.com[200.57.129.67]:25, delay=46412, delays=46410/0.12/1.1/0, dsn=4.0.0, status=deferred (host maila.exchangeadministrado.com[200.57.129.67] refused to talk to me: 554-maila.triara.com 554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.)
Apr 21 08:45:18 mail postfix/qmgr[120]: 4D6B8AA0350: from=<[email protected]>, size=9685, nrcpt=1 (queue active)
Apr 21 08:45:18 mail postfix/smtp[1265]: E2D92AA0290: host barracuda.elsiglodetorreon.com.mx[201.134.39.157] said: 450 4.1.1 <[email protected]>: Recipient address rejected: unverified address: host 192.168.7.60[192.168.7.60] said: 550 5.1.1 <[email protected]>: Recipient address rejected: User unknown in virtual mailbox table (in reply to RCPT TO command) (in reply to RCPT TO command)
Apr 21 08:45:18 mail postfix/smtp[1274]: 670E6AA0517: host smtpinipmch21.panalpina.com[194.11.79.120] refused to talk to me: 554-smtpinipmch21.panalpina.com 554 As a measure to protect our email infrastructure, this connection is being blocked. More information on your sending IP address can be found here: http://www.senderbase.org/search?searchBy=ipaddress&searchString=78.225.183.108
Apr 21 08:45:18 mail postfix/smtp[1308]: 5C9EEAA03DD: host mta7.am0.yahoodns.net[67.195.204.73] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:18 mail postfix/smtp[1308]: 5C9EEAA03DD: lost connection with mta7.am0.yahoodns.net[67.195.204.73] while sending RCPT TO
Apr 21 08:45:18 mail postfix/qmgr[120]: 4B68CAA03EC: from=<[email protected]>, size=9629, nrcpt=1 (queue active)
Apr 21 08:45:18 mail postfix/smtp[1266]: 64952AA051D: to=<[email protected]>, relay=mx02.mail.icloud.com[17.57.152.14]:25, delay=46408, delays=46405/0.26/2.3/0, dsn=4.7.0, status=deferred (host mx02.mail.icloud.com[17.57.152.14] refused to talk to me: 550 5.7.0 Blocked - see https://support.proofpoint.com/dnsbl-lookup.cgi?ip=78.225.183.108)
Apr 21 08:45:18 mail postfix/smtp[1298]: 6DDA7AA051B: host mx-biz.mail.am0.yahoodns.net[67.195.228.75] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:18 mail postfix/smtp[1298]: 6DDA7AA051B: lost connection with mx-biz.mail.am0.yahoodns.net[67.195.228.75] while sending RCPT TO
Apr 21 08:45:18 mail postfix/smtp[1269]: 8BA2CAA0319: to=<[email protected]>, orig_to=<[email protected]>, relay=mta7.am0.yahoodns.net[67.195.228.110]:25, delay=371578, delays=371575/0.05/2.5/0.16, dsn=4.7.0, status=deferred (host mta7.am0.yahoodns.net[67.195.228.110] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:18 mail postfix/smtp[1274]: 670E6AA0517: host smtpinipmch20.panalpina.com[194.11.79.116] refused to talk to me: 554-smtpinipmch20.panalpina.com 554 As a measure to protect our email infrastructure, this connection is being blocked. More information on your sending IP address can be found here: http://www.senderbase.org/search?searchBy=ipaddress&searchString=78.225.183.108
Apr 21 08:45:18 mail postfix/smtp[1299]: 3815CAA03E8: host correo3.televisa.com.mx[201.175.2.27] refused to talk to me: 554 correo3.televisa.com.mx
Apr 21 08:45:18 mail postfix/qmgr[120]: 418ACAA0510: from=<[email protected]>, size=9641, nrcpt=1 (queue active)
Apr 21 08:45:18 mail postfix/smtp[1286]: 05743AA02AC: host smtp.afirme.com.mx[200.23.76.22] refused to talk to me: 554 Blocked - see https://ipcheck.proofpoint.com/?ip=78.225.183.108
Apr 21 08:45:18 mail postfix/smtp[1309]: 57FBFAA0512: host mxb-001f1301.gslb.pphosted.com[148.163.157.204] refused to talk to me: 554 Blocked - see https://ipcheck.proofpoint.com/?ip=78.225.183.108
Apr 21 08:45:18 mail postfix/smtp[1278]: 390A6AA0071: host mta6.am0.yahoodns.net[67.195.228.110] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:18 mail postfix/smtp[1278]: 390A6AA0071: lost connection with mta6.am0.yahoodns.net[67.195.228.110] while sending RCPT TO
Apr 21 08:45:18 mail postfix/qmgr[120]: 4FAD8AA006F: from=<[email protected]>, size=9619, nrcpt=1 (queue active)
Apr 21 08:45:18 mail postfix/smtp[1288]: 532F0AA03DB: host mta7.am0.yahoodns.net[98.136.96.74] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:18 mail postfix/smtp[1288]: 532F0AA03DB: lost connection with mta7.am0.yahoodns.net[98.136.96.74] while sending RCPT TO
Apr 21 08:45:18 mail postfix/smtp[1295]: 6C391AA02AB: to=<[email protected]>, relay=mx-aol.mail.gm0.yahoodns.net[67.195.228.86]:25, delay=59104, delays=59102/0.11/2.1/0.17, dsn=4.7.0, status=deferred (host mx-aol.mail.gm0.yahoodns.net[67.195.228.86] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:18 mail postfix/qmgr[120]: A5CF2AA006C: from=<[email protected]>, size=9629, nrcpt=1 (queue active)
Apr 21 08:45:18 mail postfix/smtp[1283]: 4A354AA02A6: host correo3.televisa.com.mx[201.175.2.27] refused to talk to me: 554 correo3.televisa.com.mx
Apr 21 08:45:18 mail postfix/qmgr[120]: AB519AA03E7: from=<[email protected]>, size=9671, nrcpt=1 (queue active)
Apr 21 08:45:19 mail postfix/smtp[1299]: 3815CAA03E8: to=<[email protected]>, relay=correo5.televisa.com.mx[200.13.34.23]:25, delay=54858, delays=54857/0.15/1.5/0, dsn=4.0.0, status=deferred (host correo5.televisa.com.mx[200.13.34.23] refused to talk to me: 554 correo5.televisa.com.mx)
Apr 21 08:45:19 mail postfix/smtp[1271]: 8DD71AA0515: to=<[email protected]>, relay=mta7.am0.yahoodns.net[67.195.228.109]:25, delay=46463, delays=46460/0.59/2.5/0.17, dsn=4.7.0, status=deferred (host mta7.am0.yahoodns.net[67.195.228.109] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:19 mail postfix/qmgr[120]: A0C1FAA0459: from=<[email protected]>, size=9645, nrcpt=1 (queue active)
Apr 21 08:45:19 mail postfix/smtp[1309]: 57FBFAA0512: to=<[email protected]>, relay=mxa-001f1301.gslb.pphosted.com[148.163.157.204]:25, delay=46491, delays=46490/0.11/1.4/0, dsn=4.0.0, status=deferred (host mxa-001f1301.gslb.pphosted.com[148.163.157.204] refused to talk to me: 554 Blocked - see https://ipcheck.proofpoint.com/?ip=78.225.183.108)
Apr 21 08:45:19 mail postfix/smtp[1286]: 05743AA02AC: host smtp2.afirme.com.mx[200.23.76.24] refused to talk to me: 554 Blocked - see https://ipcheck.proofpoint.com/?ip=78.225.183.108
Apr 21 08:45:19 mail postfix/qmgr[120]: ADA9FAA0317: from=<[email protected]>, size=9607, nrcpt=1 (queue active)
Apr 21 08:45:19 mail postfix/smtp[1274]: 670E6AA0517: host smtpinipmus21.panalpina.com[199.103.111.84] refused to talk to me: 554-smtpinipmus21.panalpina.com 554 As a measure to protect our email infrastructure, this connection is being blocked. More information on your sending IP address can be found here: http://www.senderbase.org/search?searchBy=ipaddress&searchString=78.225.183.108
Apr 21 08:45:19 mail postfix/smtp[1294]: 69683AA0518: to=<[email protected]>, relay=mta5.am0.yahoodns.net[67.195.228.110]:25, delay=46485, delays=46482/0.07/2.5/0.17, dsn=4.7.0, status=deferred (host mta5.am0.yahoodns.net[67.195.228.110] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:19 mail postfix/qmgr[120]: A8091AA02A5: from=<[email protected]>, size=9679, nrcpt=1 (queue active)
Apr 21 08:45:19 mail postfix/smtp[1283]: 4A354AA02A6: host correo2.televisa.com.mx[201.175.2.28] refused to talk to me: 554 correo2.televisa.com.mx
Apr 21 08:45:19 mail postfix/qmgr[120]: 72BA3AA02B1: from=<[email protected]>, size=9623, nrcpt=1 (queue active)
Apr 21 08:45:19 mail postfix/smtp[1274]: 670E6AA0517: to=<[email protected]>, relay=smtpinipmus20.panalpina.com[199.103.111.80]:25, delay=46540, delays=46537/0.06/3/0, dsn=4.0.0, status=deferred (host smtpinipmus20.panalpina.com[199.103.111.80] refused to talk to me: 554-smtpinipmus20.panalpina.com 554 As a measure to protect our email infrastructure, this connection is being blocked. More information on your sending IP address can be found here: http://www.senderbase.org/search?searchBy=ipaddress&searchString=78.225.183.108)
Apr 21 08:45:19 mail postfix/qmgr[120]: 7C692AA0513: from=<[email protected]>, size=9679, nrcpt=1 (queue active)
Apr 21 08:45:19 mail postfix/smtp[1280]: DD82BAA03D8: to=<[email protected]>, relay=none, delay=55026, delays=55021/0.12/5/0, dsn=4.4.3, status=deferred (Name service error for name=wyndhammerida.com type=MX: Malformed or unexpected name server reply)
Apr 21 08:45:19 mail postfix/smtp[1286]: 05743AA02AC: to=<[email protected]>, relay=smtp3.afirme.com.mx[200.23.76.25]:25, delay=59037, delays=59034/0.21/2.5/0, dsn=4.0.0, status=deferred (host smtp3.afirme.com.mx[200.23.76.25] refused to talk to me: 554 Blocked - see https://ipcheck.proofpoint.com/?ip=78.225.183.108)
Apr 21 08:45:19 mail postfix/smtp[1298]: 6DDA7AA051B: to=<[email protected]>, relay=mx-biz.mail.am0.yahoodns.net[67.195.204.83]:25, delay=46437, delays=46434/0.27/2.4/0.1, dsn=4.7.0, status=deferred (host mx-biz.mail.am0.yahoodns.net[67.195.204.83] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:19 mail postfix/qmgr[120]: 7441CAA03EA: from=<[email protected]>, size=9623, nrcpt=1 (queue active)
Apr 21 08:45:19 mail postfix/qmgr[120]: 7D34DAA051E: from=<[email protected]>, size=9631, nrcpt=1 (queue active)
Apr 21 08:45:19 mail postfix/smtp[1283]: 4A354AA02A6: host correo5.televisa.com.mx[200.13.34.23] refused to talk to me: 554 correo5.televisa.com.mx
Apr 21 08:45:19 mail postfix/smtp[1291]: 0DDCFAA03ED: to=<[email protected]>, relay=mta6.am0.yahoodns.net[67.195.228.94]:25, delay=50586, delays=50584/0.12/2.2/0.17, dsn=4.7.0, status=deferred (host mta6.am0.yahoodns.net[67.195.228.94] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:19 mail postfix/smtp[1309]: ADA9FAA0317: host smtp.secureserver.net[68.178.213.37] refused to talk to me: 554 p3plibsmtp02-08.prod.phx3.secureserver.net CMGW IB103. Connection refused. 78.225.183.108 has a poor reputation on Cloudmark Sender Intelligence (CSI). Please visit http://csi.cloudmark.com/reset-request/?ip=78.225.183.108 to request a delisting.
Apr 21 08:45:19 mail postfix/qmgr[120]: 706A6AA03A2: from=<[email protected]>, size=9603, nrcpt=1 (queue active)
Apr 21 08:45:19 mail postfix/qmgr[120]: 7589FAA0052: from=<[email protected]>, size=9645, nrcpt=1 (queue active)
Apr 21 08:45:19 mail postfix/qmgr[120]: 71575AA03E5: from=<[email protected]>, size=9659, nrcpt=1 (queue active)
Apr 21 08:45:19 mail postfix/smtp[1267]: 9375AAA03E1: to=<[email protected]>, relay=none, delay=54902, delays=54897/0.07/5/0, dsn=4.4.3, status=deferred (Name service error for name=cjf.gob.mx type=MX: Malformed or unexpected name server reply)
Apr 21 08:45:19 mail postfix/smtp[1278]: 390A6AA0071: to=<[email protected]>, relay=mta5.am0.yahoodns.net[98.136.96.75]:25, delay=63270, delays=63268/0.09/2.2/0.13, dsn=4.7.0, status=deferred (host mta5.am0.yahoodns.net[98.136.96.75] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:19 mail postfix/smtp[1308]: 5C9EEAA03DD: to=<[email protected]>, relay=mta6.am0.yahoodns.net[67.195.228.110]:25, delay=54991, delays=54989/0.14/2.1/0.16, dsn=4.7.0, status=deferred (host mta6.am0.yahoodns.net[67.195.228.110] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:19 mail postfix/smtp[1269]: 418ACAA0510: host mta5.am0.yahoodns.net[98.136.96.75] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:19 mail postfix/smtp[1269]: 418ACAA0510: lost connection with mta5.am0.yahoodns.net[98.136.96.75] while sending RCPT TO
Apr 21 08:45:19 mail postfix/smtp[1295]: 4FAD8AA006F: host mta7.am0.yahoodns.net[98.136.96.77] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:19 mail postfix/smtp[1295]: 4FAD8AA006F: lost connection with mta7.am0.yahoodns.net[98.136.96.77] while sending RCPT TO
Apr 21 08:45:19 mail postfix/qmgr[120]: 72EC2AA006A: from=<[email protected]>, size=9619, nrcpt=1 (queue active)
Apr 21 08:45:19 mail postfix/smtp[1283]: 4A354AA02A6: to=<[email protected]>, relay=correo4.televisa.com.mx[200.10.200.210]:25, delay=59205, delays=59204/0.24/1.4/0, dsn=4.0.0, status=deferred (host correo4.televisa.com.mx[200.10.200.210] refused to talk to me: 554 correo4.televisa.com.mx)
Apr 21 08:45:19 mail postfix/smtp[1280]: 7C692AA0513: host mailstore1.secureserver.net[68.178.213.243] refused to talk to me: 554 p3plibsmtp02-11.prod.phx3.secureserver.net CMGW IB103. Connection refused. 78.225.183.108 has a poor reputation on Cloudmark Sender Intelligence (CSI). Please visit http://csi.cloudmark.com/reset-request/?ip=78.225.183.108 to request a delisting.
Apr 21 08:45:19 mail postfix/smtp[1309]: ADA9FAA0317: host smtp.secureserver.net[72.167.238.29] refused to talk to me: 554 p3plibsmtp01-07.prod.phx3.secureserver.net CMGW IB103. Connection refused. 78.225.183.108 has a poor reputation on Cloudmark Sender Intelligence (CSI). Please visit http://csi.cloudmark.com/reset-request/?ip=78.225.183.108 to request a delisting.
Apr 21 08:45:19 mail postfix/qmgr[120]: F024DAA029B: from=<[email protected]>, size=9595, nrcpt=1 (queue active)
Apr 21 08:45:20 mail postfix/smtp[1265]: E2D92AA0290: to=<[email protected]>, relay=smtp.elsiglodetorreon.com.mx[201.134.39.156]:25, delay=59125, delays=59118/0.19/6.4/0.17, dsn=4.1.1, status=deferred (host smtp.elsiglodetorreon.com.mx[201.134.39.156] said: 450 4.1.1 <[email protected]>: Recipient address rejected: unverified address: host 192.168.7.60[192.168.7.60] said: 550 5.1.1 <[email protected]>: Recipient address rejected: User unknown in virtual mailbox table (in reply to RCPT TO command) (in reply to RCPT TO command))
Apr 21 08:45:20 mail postfix/qmgr[120]: CF9D2AA02B9: from=<[email protected]>, size=9679, nrcpt=1 (queue active)
Apr 21 08:45:20 mail postfix/smtp[1266]: 4B68CAA03EC: host mta5.am0.yahoodns.net[67.195.228.110] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:20 mail postfix/smtp[1266]: 4B68CAA03EC: lost connection with mta5.am0.yahoodns.net[67.195.228.110] while sending RCPT TO
Apr 21 08:45:20 mail postfix/smtp[1288]: 532F0AA03DB: to=<[email protected]>, relay=mta6.am0.yahoodns.net[67.195.228.109]:25, delay=55005, delays=55003/0.09/2.2/0.16, dsn=4.7.0, status=deferred (host mta6.am0.yahoodns.net[67.195.228.109] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:20 mail postfix/qmgr[120]: CFFE9AA03D6: from=<[email protected]>, size=9657, nrcpt=1 (queue active)
Apr 21 08:45:20 mail postfix/smtp[1290]: 9AC40AA03D7: to=<[email protected]>, relay=none, delay=55037, delays=55032/0.2/5/0, dsn=4.4.3, status=deferred (Name service error for name=gmail.com.mx type=MX: Malformed or unexpected name server reply)
Apr 21 08:45:20 mail postfix/qmgr[120]: C9BF2AA02AE: from=<[email protected]>, size=9633, nrcpt=1 (queue active)
Apr 21 08:45:20 mail postfix/smtp[1277]: 88823AA0514: to=<[email protected]>, relay=none, delay=46535, delays=46530/0.05/5/0, dsn=4.4.3, status=deferred (Name service error for name=cjf.gob.mx type=MX: Malformed or unexpected name server reply)
Apr 21 08:45:20 mail postfix/qmgr[120]: C93CDAA04AF: from=<[email protected]>, size=9627, nrcpt=1 (queue active)
Apr 21 08:45:20 mail postfix/error[1311]: C9BF2AA02AE: to=<[email protected]>, relay=none, delay=58993, delays=58993/0.1/0/0, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to pep.pemex.com[200.23.91.68]:25: Operation timed out)
Apr 21 08:45:20 mail postfix/smtp[1280]: 7C692AA0513: host mailstore1.secureserver.net[72.167.238.32] refused to talk to me: 554 p3plibsmtp01-05.prod.phx3.secureserver.net CMGW IB103. Connection refused. 78.225.183.108 has a poor reputation on Cloudmark Sender Intelligence (CSI). Please visit http://csi.cloudmark.com/reset-request/?ip=78.225.183.108 to request a delisting.
Apr 21 08:45:20 mail postfix/smtp[1309]: ADA9FAA0317: host smtp.secureserver.net[68.178.213.203] refused to talk to me: 554 p3plibsmtp03-04.prod.phx3.secureserver.net CMGW IB103. Connection refused. 78.225.183.108 has a poor reputation on Cloudmark Sender Intelligence (CSI). Please visit http://csi.cloudmark.com/reset-request/?ip=78.225.183.108 to request a delisting.
Apr 21 08:45:20 mail postfix/qmgr[120]: C027CAA02B6: from=<[email protected]>, size=9623, nrcpt=1 (queue active)
Apr 21 08:45:20 mail postfix/smtp[1322]: A5CF2AA006C: host mta6.am0.yahoodns.net[67.195.228.109] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:20 mail postfix/smtp[1322]: A5CF2AA006C: lost connection with mta6.am0.yahoodns.net[67.195.228.109] while sending RCPT TO
Apr 21 08:45:20 mail postfix/qmgr[120]: C660CAA03EB: from=<[email protected]>, size=9649, nrcpt=1 (queue active)
Apr 21 08:45:20 mail postfix/qmgr[120]: C705FAA051F: from=<[email protected]>, size=9639, nrcpt=1 (queue active)
Apr 21 08:45:20 mail postfix/smtp[1298]: 7D34DAA051E: host mta6.am0.yahoodns.net[67.195.204.73] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:20 mail postfix/smtp[1298]: 7D34DAA051E: lost connection with mta6.am0.yahoodns.net[67.195.204.73] while sending RCPT TO
Apr 21 08:45:20 mail postfix/smtp[1308]: CF9D2AA02B9: host correo2.televisa.com.mx[201.175.2.28] refused to talk to me: 554 correo2.televisa.com.mx
Apr 21 08:45:20 mail postfix/qmgr[120]: C6A71AA050F: from=<[email protected]>, size=9699, nrcpt=1 (queue active)
Apr 21 08:45:20 mail postfix/qmgr[120]: BC6BCAA0511: from=<[email protected]>, size=9708, nrcpt=1 (queue active)
Apr 21 08:45:20 mail postfix/qmgr[120]: B9BFEAA03CB: from=<[email protected]>, size=9643, nrcpt=1 (queue active)
Apr 21 08:45:20 mail postfix/smtp[1280]: 7C692AA0513: host mailstore1.secureserver.net[68.178.213.244] refused to talk to me: 554 p3plibsmtp03-10.prod.phx3.secureserver.net CMGW IB103. Connection refused. 78.225.183.108 has a poor reputation on Cloudmark Sender Intelligence (CSI). Please visit http://csi.cloudmark.com/reset-request/?ip=78.225.183.108 to request a delisting.
Apr 21 08:45:20 mail postfix/smtp[1309]: ADA9FAA0317: host mailstore1.secureserver.net[72.167.238.32] refused to talk to me: 554 p3plibsmtp01-12.prod.phx3.secureserver.net CMGW IB103. Connection refused. 78.225.183.108 has a poor reputation on Cloudmark Sender Intelligence (CSI). Please visit http://csi.cloudmark.com/reset-request/?ip=78.225.183.108 to request a delisting.
Apr 21 08:45:20 mail postfix/qmgr[120]: BFBCAAA050E: from=<[email protected]>, size=9639, nrcpt=1 (queue active)
Apr 21 08:45:20 mail postfix/smtp[1274]: 72BA3AA02B1: host mta6.am0.yahoodns.net[67.195.228.94] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:20 mail postfix/smtp[1274]: 72BA3AA02B1: lost connection with mta6.am0.yahoodns.net[67.195.228.94] while sending RCPT TO
Apr 21 08:45:20 mail postfix/qmgr[120]: B0035AA02B4: from=<[email protected]>, size=9623, nrcpt=1 (queue active)
Apr 21 08:45:20 mail postfix/smtp[1308]: CF9D2AA02B9: host correo4.televisa.com.mx[200.10.200.210] refused to talk to me: 554 correo4.televisa.com.mx
Apr 21 08:45:20 mail postfix/smtp[1278]: 72EC2AA006A: host mx1.dhl.iphmx.com[68.232.129.199] refused to talk to me: 554-esa5.dhl.iphmx.com 554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.
Apr 21 08:45:20 mail postfix/smtp[1295]: 4FAD8AA006F: to=<[email protected]>, relay=mta5.am0.yahoodns.net[98.136.96.75]:25, delay=63263, delays=63261/0.08/1.9/0.12, dsn=4.7.0, status=deferred (host mta5.am0.yahoodns.net[98.136.96.75] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:20 mail postfix/qmgr[120]: BC495AA0516: from=<[email protected]>, size=9647, nrcpt=1 (queue active)
Apr 21 08:45:20 mail postfix/smtp[1291]: 706A6AA03A2: host mxa-00033b02.gslb.pphosted.com[148.163.143.103] refused to talk to me: 554 Blocked - see https://ipcheck.proofpoint.com/?ip=78.225.183.108
Apr 21 08:45:20 mail postfix/smtp[1286]: 7441CAA03EA: host mta5.am0.yahoodns.net[67.195.228.110] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:20 mail postfix/smtp[1286]: 7441CAA03EA: lost connection with mta5.am0.yahoodns.net[67.195.228.110] while sending RCPT TO
Apr 21 08:45:20 mail postfix/smtp[1324]: 7589FAA0052: host mta7.am0.yahoodns.net[98.136.96.74] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:20 mail postfix/smtp[1324]: 7589FAA0052: lost connection with mta7.am0.yahoodns.net[98.136.96.74] while sending RCPT TO
Apr 21 08:45:20 mail postfix/smtp[1266]: 4B68CAA03EC: to=<[email protected]>, relay=mta7.am0.yahoodns.net[67.195.204.77]:25, delay=54782, delays=54780/0.23/2.1/0.11, dsn=4.7.0, status=deferred (host mta7.am0.yahoodns.net[67.195.204.77] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:21 mail postfix/smtp[1309]: ADA9FAA0317: to=<[email protected]>, relay=mailstore1.secureserver.net[68.178.213.244]:25, delay=46635, delays=46633/0.13/1.8/0, dsn=4.0.0, status=deferred (host mailstore1.secureserver.net[68.178.213.244] refused to talk to me: 554 p3plibsmtp03-15.prod.phx3.secureserver.net CMGW IB103. Connection refused. 78.225.183.108 has a poor reputation on Cloudmark Sender Intelligence (CSI). Please visit http://csi.cloudmark.com/reset-request/?ip=78.225.183.108 to request a delisting.)
Apr 21 08:45:21 mail postfix/smtp[1280]: 7C692AA0513: host smtp.secureserver.net[72.167.238.29] refused to talk to me: 554 p3plibsmtp01-06.prod.phx3.secureserver.net CMGW IB103. Connection refused. 78.225.183.108 has a poor reputation on Cloudmark Sender Intelligence (CSI). Please visit http://csi.cloudmark.com/reset-request/?ip=78.225.183.108 to request a delisting.
Apr 21 08:45:21 mail postfix/qmgr[120]: BFD82AA03E4: from=<[email protected]>, size=9623, nrcpt=1 (queue active)
Apr 21 08:45:21 mail postfix/smtp[1308]: CF9D2AA02B9: host correo3.televisa.com.mx[201.175.2.27] refused to talk to me: 554 correo3.televisa.com.mx
Apr 21 08:45:21 mail postfix/smtp[1278]: 72EC2AA006A: host mx1.dhl.iphmx.com[68.232.129.11] refused to talk to me: 554-esa1.dhl.iphmx.com 554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.
Apr 21 08:45:21 mail postfix/smtp[1267]: 71575AA03E5: host mta7.am0.yahoodns.net[67.195.228.109] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:21 mail postfix/smtp[1267]: 71575AA03E5: lost connection with mta7.am0.yahoodns.net[67.195.228.109] while sending RCPT TO
Apr 21 08:45:21 mail postfix/smtp[1328]: BFBCAAA050E: host mxb-001f1301.gslb.pphosted.com[148.163.157.204] refused to talk to me: 554 Blocked - see https://ipcheck.proofpoint.com/?ip=78.225.183.108
Apr 21 08:45:21 mail postfix/smtp[1269]: 418ACAA0510: to=<[email protected]>, relay=mta7.am0.yahoodns.net[67.195.228.109]:25, delay=46477, delays=46475/0.07/2.2/0.21, dsn=4.7.0, status=deferred (host mta7.am0.yahoodns.net[67.195.228.109] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:21 mail postfix/smtp[1291]: 706A6AA03A2: to=<[email protected]>, relay=mxb-00033b02.gslb.pphosted.com[148.163.147.154]:25, delay=50631, delays=50630/0.05/1.5/0, dsn=4.0.0, status=deferred (host mxb-00033b02.gslb.pphosted.com[148.163.147.154] refused to talk to me: 554 Blocked - see https://ipcheck.proofpoint.com/?ip=78.225.183.108)
Apr 21 08:45:21 mail postfix/smtp[1322]: A5CF2AA006C: to=<[email protected]>, relay=mta6.am0.yahoodns.net[67.195.204.77]:25, delay=63314, delays=63312/0.16/2.1/0.1, dsn=4.7.0, status=deferred (host mta6.am0.yahoodns.net[67.195.204.77] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:21 mail postfix/smtp[1290]: C93CDAA04AF: host mx2.comcast.net[68.87.20.5] refused to talk to me: 554 resimta-ch2-26v.sys.comcast.net resimta-ch2-26v.sys.comcast.net 78.225.183.108 found on one or more DNSBLs, see http://postmaster.comcast.net/smtp-error-codes.php#BL000010
Apr 21 08:45:21 mail postfix/smtp[1290]: connect to mx2.comcast.net[2001:558:fe21:2a::6]:25: Address not available
Apr 21 08:45:21 mail postfix/smtp[1290]: connect to mx1.comcast.net[2001:558:fe16:1b::15]:25: Address not available
Apr 21 08:45:21 mail postfix/qmgr[120]: BFD35AA04E7: from=<[email protected]>, size=9619, nrcpt=1 (queue active)
Apr 21 08:45:21 mail postfix/smtp[1326]: connect to tycovalves.com[103.224.182.245]:25: Connection refused
Apr 21 08:45:21 mail postfix/smtp[1277]: C660CAA03EB: host mx2.ka-group.iphmx.com[68.232.142.79] refused to talk to me: 554-esa1.ka-group.iphmx.com 554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.
Apr 21 08:45:21 mail postfix/smtp[1280]: 7C692AA0513: to=<[email protected]>, relay=smtp.secureserver.net[68.178.213.203]:25, delay=46554, delays=46552/0.18/1.8/0, dsn=4.0.0, status=deferred (host smtp.secureserver.net[68.178.213.203] refused to talk to me: 554 p3plibsmtp03-01.prod.phx3.secureserver.net CMGW IB103. Connection refused. 78.225.183.108 has a poor reputation on Cloudmark Sender Intelligence (CSI). Please visit http://csi.cloudmark.com/reset-request/?ip=78.225.183.108 to request a delisting.)
Apr 21 08:45:21 mail postfix/smtp[1268]: 686BEAA0068: to=<[email protected]>, relay=none, delay=63381, delays=63376/0.13/5/0, dsn=4.4.3, status=deferred (Name service error for name=correo.cjf.gob.mx type=MX: Malformed or unexpected name server reply)
Apr 21 08:45:21 mail postfix/smtp[1326]: BC6BCAA0511: to=<[email protected]>, relay=none, delay=46595, delays=46594/0.11/0.67/0, dsn=4.4.1, status=deferred (connect to tycovalves.com[103.224.182.245]:25: Connection refused)
Apr 21 08:45:21 mail postfix/smtp[1283]: F024DAA029B: host mx-aol.mail.gm0.yahoodns.net[67.195.228.84] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:21 mail postfix/smtp[1283]: F024DAA029B: lost connection with mx-aol.mail.gm0.yahoodns.net[67.195.228.84] while sending RCPT TO
Apr 21 08:45:21 mail postfix/qmgr[120]: B18F5AA02B3: from=<[email protected]>, size=9635, nrcpt=1 (queue active)
Apr 21 08:45:21 mail postfix/smtp[1288]: CFFE9AA03D6: host mx1.emailsrvr.com[146.20.161.1] said: 451 4.7.1 Received too many messages from a new or untrusted IP: 78.225.183.108 (Z27/38C6517) (G28) (in reply to RCPT TO command)
Apr 21 08:45:21 mail postfix/smtp[1308]: CF9D2AA02B9: to=<[email protected]>, relay=correo5.televisa.com.mx[200.13.34.23]:25, delay=58981, delays=58979/0.08/1.4/0, dsn=4.0.0, status=deferred (host correo5.televisa.com.mx[200.13.34.23] refused to talk to me: 554 correo5.televisa.com.mx)
Apr 21 08:45:21 mail postfix/smtp[1328]: BFBCAAA050E: to=<[email protected]>, relay=mxa-001f1301.gslb.pphosted.com[148.163.157.204]:25, delay=46623, delays=46622/0.17/0.66/0, dsn=4.0.0, status=deferred (host mxa-001f1301.gslb.pphosted.com[148.163.157.204] refused to talk to me: 554 Blocked - see https://ipcheck.proofpoint.com/?ip=78.225.183.108)
Apr 21 08:45:21 mail postfix/smtp[1325]: C705FAA051F: host mta6.am0.yahoodns.net[98.136.96.75] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:21 mail postfix/smtp[1325]: C705FAA051F: lost connection with mta6.am0.yahoodns.net[98.136.96.75] while sending RCPT TO
Apr 21 08:45:21 mail postfix/smtp[1278]: 72EC2AA006A: host mx1.dhl.iphmx.com[68.232.141.220] refused to talk to me: 554-esa11.dhl.iphmx.com 554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.
Apr 21 08:45:21 mail postfix/smtp[1274]: 72BA3AA02B1: to=<[email protected]>, relay=mta6.am0.yahoodns.net[67.195.204.77]:25, delay=59009, delays=59006/0.06/2.1/0.11, dsn=4.7.0, status=deferred (host mta6.am0.yahoodns.net[67.195.204.77] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:21 mail postfix/qmgr[120]: BD825AA04F8: from=<[email protected]>, size=9631, nrcpt=1 (queue active)
Apr 21 08:45:21 mail postfix/smtp[1277]: C660CAA03EB: host mx2.ka-group.iphmx.com[68.232.143.168] refused to talk to me: 554-esa2.ka-group.iphmx.com 554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.
Apr 21 08:45:21 mail postfix/smtp[1286]: 7441CAA03EA: to=<[email protected]>, relay=mta5.am0.yahoodns.net[67.195.204.79]:25, delay=50636, delays=50634/0.09/2.1/0.1, dsn=4.7.0, status=deferred (host mta5.am0.yahoodns.net[67.195.204.79] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:21 mail postfix/qmgr[120]: BF1EAAA03EE: from=<[email protected]>, size=9605, nrcpt=1 (queue active)
Apr 21 08:45:21 mail postfix/smtp[1298]: 7D34DAA051E: to=<[email protected]>, relay=mta5.am0.yahoodns.net[67.195.228.111]:25, delay=46407, delays=46405/0.07/2.1/0.17, dsn=4.7.0, status=deferred (host mta5.am0.yahoodns.net[67.195.228.111] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:21 mail postfix/smtp[1278]: 72EC2AA006A: host mx1.dhl.iphmx.com[68.232.148.170] refused to talk to me: 554-esa20.dhl.iphmx.com 554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.
Apr 21 08:45:22 mail postfix/smtp[1324]: 7589FAA0052: to=<[email protected]>, relay=mta6.am0.yahoodns.net[98.136.96.74]:25, delay=63309, delays=63307/0.13/2/0.12, dsn=4.7.0, status=deferred (host mta6.am0.yahoodns.net[98.136.96.74] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:22 mail postfix/smtp[1290]: C93CDAA04AF: to=<[email protected]>, relay=mx1.comcast.net[96.114.157.80]:25, delay=47554, delays=47552/0.06/1.6/0, dsn=4.0.0, status=deferred (host mx1.comcast.net[96.114.157.80] refused to talk to me: 554 resimta-po-15v.sys.comcast.net resimta-po-15v.sys.comcast.net 78.225.183.108 found on one or more DNSBLs, see http://postmaster.comcast.net/smtp-error-codes.php#BL000010)
Apr 21 08:45:22 mail postfix/smtp[1277]: C660CAA03EB: host mx1.ka-group.iphmx.com[68.232.142.79] refused to talk to me: 554-esa1.ka-group.iphmx.com 554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.
Apr 21 08:45:22 mail postfix/smtp[1273]: 02746AA02A8: to=<[email protected]>, relay=none, delay=59139, delays=59134/0.06/5/0, dsn=4.4.3, status=deferred (Name service error for name=correo.cjf.gob.mx type=MX: Malformed or unexpected name server reply)
Apr 21 08:45:22 mail postfix/smtp[1278]: 72EC2AA006A: to=<[email protected]>, relay=mx1.dhl.iphmx.com[68.232.129.198]:25, delay=63349, delays=63347/0.11/2.3/0, dsn=4.0.0, status=deferred (host mx1.dhl.iphmx.com[68.232.129.198] refused to talk to me: 554-esa4.dhl.iphmx.com 554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.)
Apr 21 08:45:22 mail postfix/smtp[1277]: C660CAA03EB: to=<[email protected]>, relay=mx1.ka-group.iphmx.com[68.232.143.168]:25, delay=54829, delays=54827/0.05/1.8/0, dsn=4.0.0, status=deferred (host mx1.ka-group.iphmx.com[68.232.143.168] refused to talk to me: 554-esa2.ka-group.iphmx.com 554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.)
Apr 21 08:45:22 mail postfix/smtp[1329]: B0035AA02B4: host mx1.emailsrvr.com[146.20.161.1] said: 451 4.7.1 Received too many messages from a new or untrusted IP: 78.225.183.108 (Z27/38C6517) (G28) (in reply to RCPT TO command)
Apr 21 08:45:22 mail postfix/smtp[1283]: F024DAA029B: to=<[email protected]>, relay=mx-aol.mail.gm0.yahoodns.net[98.136.96.92]:25, delay=59235, delays=59232/0.06/2.3/0.13, dsn=4.7.0, status=deferred (host mx-aol.mail.gm0.yahoodns.net[98.136.96.92] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:22 mail postfix/smtp[1295]: BC495AA0516: host mta7.am0.yahoodns.net[67.195.228.110] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:22 mail postfix/smtp[1295]: BC495AA0516: lost connection with mta7.am0.yahoodns.net[67.195.228.110] while sending RCPT TO
Apr 21 08:45:22 mail postfix/smtp[1267]: 71575AA03E5: to=<[email protected]>, relay=mta5.am0.yahoodns.net[67.195.228.106]:25, delay=54790, delays=54787/0.09/2.5/0.17, dsn=4.7.0, status=deferred (host mta5.am0.yahoodns.net[67.195.228.106] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:22 mail postfix/smtp[1327]: B9BFEAA03CB: host mxb-00176a02.gslb.pphosted.com[67.231.149.43] refused to talk to me: 554 Blocked - see https://ipcheck.proofpoint.com/?ip=78.225.183.108
Apr 21 08:45:22 mail postfix/smtp[1297]: connect to gw1.corefusion.net[208.94.165.66]:25: Host is unreachable
Apr 21 08:45:22 mail postfix/smtp[1269]: BFD35AA04E7: host mta5.am0.yahoodns.net[98.136.96.75] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:22 mail postfix/smtp[1269]: BFD35AA04E7: lost connection with mta5.am0.yahoodns.net[98.136.96.75] while sending RCPT TO
Apr 21 08:45:22 mail postfix/smtp[1327]: B9BFEAA03CB: host mxa-00176a02.gslb.pphosted.com[67.231.149.43] refused to talk to me: 554 Blocked - see https://ipcheck.proofpoint.com/?ip=78.225.183.108
Apr 21 08:45:22 mail postfix/smtp[1325]: C705FAA051F: to=<[email protected]>, relay=mta6.am0.yahoodns.net[67.195.228.94]:25, delay=46402, delays=46399/0.13/2.2/0.17, dsn=4.7.0, status=deferred (host mta6.am0.yahoodns.net[67.195.228.94] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:23 mail postfix/smtp[1288]: CFFE9AA03D6: to=<[email protected]>, relay=mx2.emailsrvr.com[108.166.43.2]:25, delay=55028, delays=55025/0.05/2.5/0.39, dsn=4.7.1, status=deferred (host mx2.emailsrvr.com[108.166.43.2] said: 451 4.7.1 Received too many messages from a new or untrusted IP: 78.225.183.108 (Z27/38C6517) (G28) (in reply to RCPT TO command))
Apr 21 08:45:23 mail postfix/smtp[1275]: 2EC47AA0067: host mxa-0036c501.gslb.pphosted.com[148.163.139.129] refused to talk to me: 554 Blocked - see https://ipcheck.proofpoint.com/?ip=78.225.183.108
Apr 21 08:45:23 mail postfix/smtp[1326]: BD825AA04F8: host mta5.am0.yahoodns.net[67.195.228.111] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command)
Apr 21 08:45:23 mail postfix/smtp[1326]: BD825AA04F8: lost connection with mta5.am0.yahoodns.net[67.195.228.111] while sending RCPT TO
Apr 21 08:45:23 mail postfix/smtp[1327]: B9BFEAA03CB: host mx0a-00176a02.pphosted.com[67.231.149.43] refused to talk to me: 554 Blocked - see https://ipcheck.proofpoint.com/?ip=78.225.183.108
Apr 21 08:45:23 mail postfix/smtp[1275]: 2EC47AA0067: to=<[email protected]>, relay=mxb-0036c501.gslb.pphosted.com[148.163.139.129]:25, delay=63415, delays=63405/0.11/9.3/0, dsn=4.0.0, status=deferred (host mxb-0036c501.gslb.pphosted.com[148.163.139.129] refused to talk to me: 554 Blocked - see https://ipcheck.proofpoint.com/?ip=78.225.183.108)
Apr 21 08:45:23 mail postfix/smtp[1327]: B9BFEAA03CB: to=<[email protected]>, relay=mx0b-00176a02.pphosted.com[67.231.157.41]:25, delay=54915, delays=54912/0.14/2.8/0, dsn=4.0.0, status=deferred (host mx0b-00176a02.pphosted.com[67.231.157.41] refused to talk to me: 554 Blocked - see https://ipcheck.proofpoint.com/?ip=78.225.183.108)
Apr 21 08:45:23 mail postfix/smtp[1295]: BC495AA0516: to=<[email protected]>, relay=mta7.am0.yahoodns.net[98.136.96.77]:25, delay=46465, delays=46463/0.23/2.3/0.12, dsn=4.7.0, status=deferred (host mta7.am0.yahoodns.net[98.136.96.77] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:23 mail postfix/smtp[1269]: BFD35AA04E7: to=<[email protected]>, relay=mta6.am0.yahoodns.net[98.136.96.74]:25, delay=46627, delays=46625/0.29/1.9/0.13, dsn=4.7.0, status=deferred (host mta6.am0.yahoodns.net[98.136.96.74] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:23 mail postfix/smtp[1329]: B0035AA02B4: to=<[email protected]>, relay=mx2.emailsrvr.com[108.166.43.2]:25, delay=58989, delays=58986/0.32/2.4/0.38, dsn=4.7.1, status=deferred (host mx2.emailsrvr.com[108.166.43.2] said: 451 4.7.1 Received too many messages from a new or untrusted IP: 78.225.183.108 (Z27/38C6517) (G28) (in reply to RCPT TO command))
Apr 21 08:45:23 mail postfix/smtp[1326]: BD825AA04F8: to=<[email protected]>, relay=mta7.am0.yahoodns.net[67.195.204.77]:25, delay=46606, delays=46603/0.15/2.1/0.1, dsn=4.7.0, status=deferred (host mta7.am0.yahoodns.net[67.195.204.77] said: 421 4.7.0 [TSS04] Messages from 78.225.183.108 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html (in reply to MAIL FROM command))
Apr 21 08:45:24 mail postfix/smtp[1299]: AB519AA03E7: to=<[email protected]>, relay=none, delay=54803, delays=54798/0.08/5/0, dsn=4.4.3, status=deferred (Name service error for name=correo.cjf.gob.mx type=MX: Malformed or unexpected name server reply)
Apr 21 08:45:24 mail postfix/error[1311]: C6A71AA050F: to=<[email protected]>, relay=none, delay=46604, delays=46600/3.5/0/0.01, dsn=4.4.3, status=deferred (delivery temporarily suspended: Name service error for name=correo.cjf.gob.mx type=MX: Malformed or unexpected name server reply)
Apr 21 08:45:24 mail postfix/error[1331]: B18F5AA02B3: to=<[email protected]>, relay=none, delay=59001, delays=58999/2.6/0/0, dsn=4.4.3, status=deferred (delivery temporarily suspended: Name service error for name=correo.cjf.gob.mx type=MX: Malformed or unexpected name server reply)
Apr 21 08:45:24 mail postfix/smtp[1294]: A8091AA02A5: to=<[email protected]>, relay=none, delay=59179, delays=59174/0.09/5/0, dsn=4.4.3, status=deferred (Name service error for name=sifinancia.michoacan.gob.mx type=MX: Malformed or unexpected name server reply)
Apr 21 08:45:24 mail postfix/smtp[1309]: BF1EAAA03EE: host mxb-00033b02.gslb.pphosted.com[148.163.147.154] refused to talk to me: 554 Blocked - see https://ipcheck.proofpoint.com/?ip=78.225.183.108
Apr 21 08:45:24 mail postfix/smtp[1309]: BF1EAAA03EE: to=<[email protected]>, relay=mxa-00033b02.gslb.pphosted.com[148.163.143.103]:25, delay=50577, delays=50575/2.3/0.63/0, dsn=4.0.0, status=deferred (host mxa-00033b02.gslb.pphosted.com[148.163.143.103] refused to talk to me: 554 Blocked - see https://ipcheck.proofpoint.com/?ip=78.225.183.108)
Apr 21 08:45:25 mail postfix/smtp[1265]: C027CAA02B6: to=<[email protected]>, relay=none, delay=58992, delays=58987/0.1/5/0, dsn=4.4.3, status=deferred (Name service error for name=doulton.com.mx type=MX: Malformed or unexpected name server reply)
Apr 21 08:45:27 mail postfix/smtpd[187]: connect from localhost[127.0.0.1]
Apr 21 08:45:27 mail postfix/smtpd[187]: disconnect from localhost[127.0.0.1] quit=1 commands=1
Apr 21 08:45:27 mail postfix/smtpd[318]: connect from localhost[127.0.0.1]
Apr 21 08:45:27 mail postfix/smtpd[318]: disconnect from localhost[127.0.0.1] quit=1 commands=1
Apr 21 08:45:37 mail postfix/smtpd[187]: connect from localhost[127.0.0.1]
Apr 21 08:45:37 mail postfix/smtpd[318]: connect from localhost[127.0.0.1]
Apr 21 08:45:38 mail postfix/smtpd[187]: disconnect from localhost[127.0.0.1] quit=1 commands=1
Apr 21 08:45:39 mail postfix/smtpd[318]: disconnect from localhost[127.0.0.1] quit=1 commands=1
Apr 21 08:45:39 mail postfix/smtp[1279]: 17EEFAA029E: to=<[email protected]>, relay=none, delay=59254, delays=59229/0.11/25/0, dsn=4.4.3, status=deferred (Name service error for name=sanpedro.gob.mx type=MX: Malformed or unexpected name server reply)
Apr 21 08:45:39 mail postfix/smtp[1285]: D4CFBAA0061: to=<[email protected]>, relay=none, delay=63472, delays=63447/0.16/25/0, dsn=4.4.3, status=deferred (Name service error for name=correo.cjf.gob.mx type=MX: Malformed or unexpected name server reply)
Apr 21 08:45:40 mail postfix/smtp[1289]: 9BD0AAA02A3: to=<[email protected]>, relay=none, delay=59241, delays=59216/0.13/25/0, dsn=4.4.3, status=deferred (Name service error for name=cjf.gob.mx type=MX: Malformed or unexpected name server reply)
Apr 21 08:45:41 mail postfix/smtp[1293]: 6B69FAA03E6: to=<[email protected]>, relay=none, delay=54874, delays=54849/0.3/25/0, dsn=4.4.3, status=deferred (Name service error for name=correo.cjf.gob.mx type=MX: Malformed or unexpected name server reply)
Apr 21 08:45:44 mail postfix/smtp[1287]: connect to mx1.televisatelecom.net[189.202.235.193]:25: Operation timed out
Apr 21 08:45:44 mail postfix/smtp[1287]: 9625EAA05A8: to=<[email protected]>, relay=none, delay=44534, delays=44504/0.12/30/0, dsn=4.4.1, status=deferred (connect to mx1.televisatelecom.net[189.202.235.193]:25: Operation timed out)
Apr 21 08:45:46 mail postfix/smtp[1272]: connect to wiredeck.us[69.64.147.243]:25: Operation timed out
Apr 21 08:45:46 mail postfix/smtp[1272]: 8D10DAA03DC: to=<[email protected]>, relay=none, delay=55015, delays=54985/0.08/31/0, dsn=4.4.1, status=deferred (connect to wiredeck.us[69.64.147.243]:25: Operation timed out)
Apr 21 08:45:46 mail postfix/smtp[1270]: connect to volcan.ucol.mx[148.213.1.2]:25: Operation timed out
Apr 21 08:45:46 mail postfix/smtp[1270]: 81B7BAA03E9: to=<[email protected]>, relay=none, delay=50693, delays=50662/0.1/31/0, dsn=4.4.1, status=deferred (connect to volcan.ucol.mx[148.213.1.2]:25: Operation timed out)
Apr 21 08:45:46 mail postfix/smtp[1296]: connect to mx1.televisatelecom.net[189.202.235.193]:25: Operation timed out
Apr 21 08:45:46 mail postfix/smtp[1296]: 641CBAA051A: to=<[email protected]>, relay=none, delay=46458, delays=46428/0.16/30/0, dsn=4.4.1, status=deferred (connect to mx1.televisatelecom.net[189.202.235.193]:25: Operation timed out)
Apr 21 08:45:47 mail postfix/smtp[1281]: 84388AA0343: host mx1.fuse.net[64.8.71.15] refused to talk to me: 550 5.7.1 [C17] RBL Restriction: - <78.225.183.108> - See http://csi.cloudmark.com/reset-request/?ip=78.225.183.108
Apr 21 08:45:47 mail postfix/smtpd[187]: connect from localhost[127.0.0.1]
Apr 21 08:45:47 mail postfix/smtpd[187]: disconnect from localhost[127.0.0.1] quit=1 commands=1
Apr 21 08:45:47 mail postfix/smtpd[318]: connect from localhost[127.0.0.1]
Apr 21 08:45:47 mail postfix/smtpd[318]: disconnect from localhost[127.0.0.1] quit=1 commands=1
Apr 21 08:45:48 mail postfix/smtp[1282]: connect to domino.ryder.com[168.218.95.3]:25: Operation timed out
Apr 21 08:45:48 mail postfix/smtp[1282]: 5BE37AA0204: to=<[email protected]>, relay=none, delay=61343, delays=61313/0.1/30/0, dsn=4.4.1, status=deferred (connect to domino.ryder.com[168.218.95.3]:25: Operation timed out)

User [email protected] does'nt exist, I don't know ow this manage to get through.

I'm running the helm deployment on a kubernetes 1.17.2 :
root@k8p1:~/helm_charts/mailu/mailu# cat Chart.yaml apiVersion: v1 appVersion: "1.8" description: Mailu mail system name: mailu version: 0.0.6
Cheers,

Is this GIT repository still maintained?

Hey there,

is this GIT repository still maintained?

I was thinking about creating pull requests here, but I don't want to waste my time if this GIT repo is not maintained anymore.
The reason why I'm asking is because there are some PRs that are already almost a year open.

If this is not maintained anymore I'll just continue to use my fork.

Thanks!

Rancher 2 and helm chart incompatibillity?

Describe the bug
Deploying a new app "mailu" version 0.1.0 from the rancher catalog.
After setting up all the variables and hitting deploy, I get the following error

Wait helm template failed. Error: template: mailu/templates/ingress.yaml:20:17: executing "mailu/templates/ingress.yaml" at <.Values.hostnames>: range can't iterate over [subdomain.domain.tld] Use --debug flag to render out invalid YAML : exit status 1

I am at a loss, as far as i can tell, it's a syntax error

Not an expert programmer, need help diving deeper into the problem

Environment

• Rancher 2.5.3

Additional context
Add any other context about the problem here.

postfix crashes

Describe the bug

After running some time (2-3 hours) postfix crashes abruptly. My PVC has been set up on NFS and I believe most probably it's issue with filesystem handing.

ay 21 11:30:18 mail3 postfix/smtpd[10793]: connect from localhost[127.0.0.1]
May 21 11:30:18 mail3 postfix/smtpd[10793]: disconnect from localhost[127.0.0.1] quit=1 commands=1
May 21 11:30:21 mail3 postfix/smtpd[10793]: connect from localhost[127.0.0.1]
May 21 11:30:21 mail3 postfix/smtpd[10793]: disconnect from localhost[127.0.0.1] quit=1 commands=1
May 21 11:30:28 mail3 postfix/smtpd[10793]: connect from localhost[127.0.0.1]
May 21 11:30:28 mail3 postfix/smtpd[10793]: disconnect from localhost[127.0.0.1] quit=1 commands=1
May 21 11:30:31 mail3 postfix/smtpd[10793]: connect from localhost[127.0.0.1]
May 21 11:30:31 mail3 postfix/smtpd[10793]: disconnect from localhost[127.0.0.1] quit=1 commands=1
May 21 11:30:38 mail3 postfix/smtpd[10793]: connect from localhost[127.0.0.1]
May 21 11:30:38 mail3 postfix/smtpd[10793]: disconnect from localhost[127.0.0.1] quit=1 commands=1
May 21 11:30:41 mail3 postfix/smtpd[10793]: connect from localhost[127.0.0.1]
May 21 11:30:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:30:41 mail3 postfix/smtpd[10793]: disconnect from localhost[127.0.0.1] quit=1 commands=1
May 21 11:30:48 mail3 postfix/smtpd[10793]: connect from localhost[127.0.0.1]
May 21 11:30:48 mail3 postfix/smtpd[10793]: disconnect from localhost[127.0.0.1] quit=1 commands=1
May 21 11:30:51 mail3 postfix/smtpd[10793]: connect from localhost[127.0.0.1]
May 21 11:30:51 mail3 postfix/smtpd[10793]: disconnect from localhost[127.0.0.1] quit=1 commands=1
May 21 11:30:58 mail3 postfix/smtpd[10793]: connect from 10-244-1-73.mail-ballancer.mail.svc.cluster.local[10.244.1.73]
May 21 11:30:58 mail3 postfix/smtpd[10793]: warning: connect #1 to subsystem private/rewrite: Invalid argument
May 21 11:31:08 mail3 postfix/smtpd[10793]: warning: connect #2 to subsystem private/rewrite: Invalid argument
May 21 11:31:18 mail3 postfix/smtpd[10793]: warning: connect #3 to subsystem private/rewrite: Invalid argument
May 21 11:31:28 mail3 postfix/smtpd[10793]: warning: connect #4 to subsystem private/rewrite: Invalid argument
May 21 11:31:38 mail3 postfix/smtpd[10793]: warning: connect #5 to subsystem private/rewrite: Invalid argument
May 21 11:31:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:31:48 mail3 postfix/smtpd[10793]: warning: connect #6 to subsystem private/rewrite: Invalid argument
May 21 11:31:58 mail3 postfix/smtpd[10793]: warning: connect #7 to subsystem private/rewrite: Invalid argument
May 21 11:32:08 mail3 postfix/smtpd[10793]: warning: connect #8 to subsystem private/rewrite: Invalid argument
May 21 11:32:18 mail3 postfix/smtpd[10793]: warning: connect #9 to subsystem private/rewrite: Invalid argument
May 21 11:32:28 mail3 postfix/smtpd[10793]: warning: connect #10 to subsystem private/rewrite: Invalid argument
May 21 11:32:38 mail3 postfix/smtpd[10793]: fatal: connect #11 to subsystem private/rewrite: Invalid argument
May 21 11:32:39 mail3 postfix/master[352]: warning: process /usr/libexec/postfix/smtpd pid 10793 exit status 1
May 21 11:32:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service qmgr(public/qmgr): Invalid argument
May 21 11:32:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:32:42 mail3 postfix/master[352]: warning: process /usr/libexec/postfix/smtpd pid 11029 exit status 1
May 21 11:32:42 mail3 postfix/master[352]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
May 21 11:33:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:34:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:35:23 mail3 postfix/master[352]: warning: process /usr/libexec/postfix/smtpd pid 11038 exit status 1
May 21 11:35:23 mail3 postfix/master[352]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
May 21 11:35:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:36:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:37:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service qmgr(public/qmgr): Invalid argument
May 21 11:37:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:38:04 mail3 postfix/master[352]: warning: process /usr/libexec/postfix/smtpd pid 11039 exit status 1
May 21 11:38:04 mail3 postfix/master[352]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
May 21 11:38:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:39:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:40:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:40:45 mail3 postfix/master[352]: warning: process /usr/libexec/postfix/smtpd pid 11040 exit status 1
May 21 11:40:45 mail3 postfix/master[352]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
May 21 11:41:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:42:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service qmgr(public/qmgr): Invalid argument
May 21 11:42:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:43:26 mail3 postfix/master[352]: warning: process /usr/libexec/postfix/smtpd pid 11041 exit status 1
May 21 11:43:26 mail3 postfix/master[352]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
May 21 11:43:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:44:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:45:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:46:07 mail3 postfix/master[352]: warning: process /usr/libexec/postfix/smtpd pid 11042 exit status 1
May 21 11:46:07 mail3 postfix/master[352]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
May 21 11:46:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:47:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service qmgr(public/qmgr): Invalid argument
May 21 11:47:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:48:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:48:48 mail3 postfix/master[352]: warning: process /usr/libexec/postfix/smtpd pid 11060 exit status 1
May 21 11:48:48 mail3 postfix/master[352]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
May 21 11:49:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:50:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:51:29 mail3 postfix/master[352]: warning: process /usr/libexec/postfix/smtpd pid 11061 exit status 1
May 21 11:51:29 mail3 postfix/master[352]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
May 21 11:51:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:52:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service qmgr(public/qmgr): Invalid argument
May 21 11:52:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:53:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:54:10 mail3 postfix/master[352]: warning: process /usr/libexec/postfix/smtpd pid 11062 exit status 1
May 21 11:54:10 mail3 postfix/master[352]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
May 21 11:54:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:55:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:56:42 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:56:51 mail3 postfix/master[352]: warning: process /usr/libexec/postfix/smtpd pid 11063 exit status 1
May 21 11:56:51 mail3 postfix/master[352]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
May 21 11:57:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service tlsmgr(private/tlsmgr): Invalid argument
May 21 11:57:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service qmgr(public/qmgr): Invalid argument
May 21 11:57:42 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:58:42 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 11:59:32 mail3 postfix/master[352]: warning: process /usr/libexec/postfix/smtpd pid 11064 exit status 1
May 21 11:59:32 mail3 postfix/master[352]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
May 21 11:59:42 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 12:00:42 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 12:01:42 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 12:02:13 mail3 postfix/master[352]: warning: process /usr/libexec/postfix/smtpd pid 11065 exit status 1
May 21 12:02:13 mail3 postfix/master[352]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
May 21 12:02:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service qmgr(public/qmgr): Invalid argument
May 21 12:02:42 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 12:03:42 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 12:04:41 mail3 postfix/master[352]: warning: process /usr/libexec/postfix/smtpd pid 11083 exit status 1
May 21 12:04:41 mail3 postfix/master[352]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
May 21 12:04:42 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 12:04:54 mail3 postfix/master[352]: warning: process /usr/libexec/postfix/smtpd pid 11084 exit status 1
May 21 12:04:54 mail3 postfix/master[352]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
May 21 12:05:42 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 12:06:42 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 12:07:22 mail3 postfix/master[352]: warning: process /usr/libexec/postfix/smtpd pid 11085 exit status 1
May 21 12:07:22 mail3 postfix/master[352]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
May 21 12:07:35 mail3 postfix/master[352]: warning: process /usr/libexec/postfix/smtpd pid 11086 exit status 1
May 21 12:07:35 mail3 postfix/master[352]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
May 21 12:07:41 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service qmgr(public/qmgr): Invalid argument
May 21 12:07:42 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argument
May 21 12:08:42 mail3 postfix/master[352]: warning: master_wakeup_timer_event: service pickup(public/pickup): Invalid argumen

Environment
Digital Ocean
ReadWriteMany PVC on NFS

Additional context
Add any other context about the problem here.

Add ability to disable non essentials components like roundcube and clamav

I'm using an external webmail client and I don't need an antivirus for my emails.

Is it possible to give the ability to disable these two components just like it's already possible with the webdav component?

Allow choosing between separate env vars or a single ConfigMap

Is your feature request related to a problem? Please describe.

For reasons which would be off-topic and TL;DR here, I prefer a single ConfigMap instead of environment variables specified individually in each containers.

Describe the solution you'd like

I would like to have the ability to generate a configuration employing a single ConfigMap.

Describe alternatives you've considered

Generate a template .yaml, editing by hand and saving it in a safe place for regular use in my platform. This is not really an option, since I would not easily capture upstream improvements.

Additional context

The ability to restart containers when a ConfigMap changes ... or not having this ability at all... is not a concern to me, since from my experience, the more resilient approach at this point would be restarting the entire thing anyway.

I admit that in future I may eventually change my opinion on that. In this case, the thread below provides some ideas:

• https://stackoverflow.com/questions/37317003/restart-pods-when-configmap-updates-in-kubernetes

Also, this matter is expected to be better addressed at some point in future:

• kubernetes/kubernetes#22368

Switch to github actions

travis-ci.org stopped their free service. We need to switch to something else. Github actions should do the job.

Allow overrides for dovecot

Overrides can customize config of mailu's services. E.g. for NFS, the following is required:
https://mailu.io/1.7/kubernetes/mailu/index.html#adaptations

Overrides should also be supported by the helm chart. I think the best way is to use values and configmaps here.

Authentication failure with Roundcube

I am deploying Mailu v1.7 on a GKE cluster. The deployment went well but when it comes to login on portal I can notice 2 behaviors :

• when credentials is wrong it says so
• when it's corrects auth just fails with 401 error without any further details.
  I even set the log level to debug, it did not help.

Failure to install mailu using helm chart

I am trying to install the latest mailu chart into a minikube cluster. I have used the default values.yaml and and added extra config values required for my setup. But the templating itself fails for the current chart.

On doing helm lint on the current chart (after cloning) i get the following error

==> Linting .
[INFO] Chart.yaml: icon is recommended
[ERROR] templates/: template: mailu/templates/rspamd.yaml:26:25: executing "mailu/templates/rspamd.yaml" at <.Values.rspamd.image.repository>: nil pointer evaluating interface {}.image

Error: 1 chart(s) linted, 1 chart(s) failed

I am using helm version

version.BuildInfo{Version:"v3.0.2", GitCommit:"19e47ee3283ae98139d98460de796c1be1e3975f", GitTreeState:"clean", GoVersion:"go1.13.5"}

I suspected if it was a helm version issue, so tried this against v3.0.1 and v2.16.0. Still getting the same error. Wanted to if i am missing anything here.

[BUG] Documentation about sample load balancer

Currently this helm chart does not include load balancer. In such environments as Digital Ocean this setup is unusable.

Even more important, documentation must provide information to apply externalTrafficPolicy: Local otherwise newly set up cluster will be open relay. It is documented Mailu/Mailu#1370 however I believe it should be solved in helm chart as well.

Support for custom livenessProbe and readynessProbe values

Hi,

as I was running in some issues with a slowly starting rspamd pod, I added the possibility to configure the livenessProbe and readynessProbe values to my fork.
Perhaps this is of interest for others, too.
I will create a pull request and you can decide to merge it - suggestions are welcome.

Best regards
Jochen

Enable the use of an existing secret for postfix relay if provided

Use existing secret for postfix relay if provided

The list of supported Mailu versions is missing in the README.md

Is this helm chart only compatible with the master branch or all versions? If it is only compatible with master or specific versions it should be mentioned in the Prerequisites, thanks!

Existing Ingress api version has been deprecated

Describe the bug
With kubernetes v1.22.* 'networking.k8s.io/v1beta1' is no longer available causing the helm install to fail.

Environment

$ kubectl version 
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.1", GitCommit:"632ed300f2c34f6d6d15ca4cef3d3c7073412212", GitTreeState:"clean", BuildDate:"2021-08-19T15:45:37Z", GoVersion:"go1.16.7", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.1", GitCommit:"632ed300f2c34f6d6d15ca4cef3d3c7073412212", GitTreeState:"clean", BuildDate:"2021-08-19T15:39:34Z", GoVersion:"go1.16.7", Compiler:"gc", Platform:"linux/amd64"}

Additional context

$ ./update-install.sh 
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "mailu" chart repository
...Successfully got an update from the "bitnami" chart repository
Update Complete. ⎈Happy Helming!⎈
Release "mailu" does not exist. Installing it now.
Error: unable to build kubernetes objects from release manifest: [unable to recognize "": no matches for kind "Ingress" in version "networking.k8s.io/v1beta1", unable to recognize "": no matches for kind "Certificate" in version "cert-manager.io/v1alpha2"]

[BUG] Default config creates a open relay on baremetal

Describe the bug
When I install mailu, and I check the logs of mailu-front all requests seems to come from cni0 ip address because of the use of hostPort. This ip is forwarded to postfix making it an open relay.
is there a specific raison for having an nginx inside k8s ? IMO, communication between pods should be done using service name (each deployment with its own service)

1. it would make it clear what depends on what, and what talks to what.
2. it would allow to use hostNetwork when we want to expose something (smtp, imap...) removing the need for hostPort and reducing the risk of intermediaries creating open relays (ex: mis-config of nginx).

Environment

• Kubespray
• flannel

Additional context
Add any other context about the problem here.

NodePorts cannot always be reached

Currently the method to access Mailu services in Kubernetes is using NodePort.

This does not work for all deployment types of Kubernetes, for instance Azure's AKS

Can the NodePort approach be converted to the use of TCP/UDP mappings using Nginx ingress controller?

https://kubernetes.github.io/ingress-nginx/user-guide/exposing-tcp-udp-services/

"Unable to attach or mount volumes" on Multi Host Cluster

Hello everyone,

Yesterday I tried to install the mailu Chart in my Cluster (currently 1 master, 2 nodes). The installation works just fine, but three pods are stuck in "ContainerCreating"-Status. The problem seems related to the mounting/binding of the storage pv. (For info, I use openebs as the storage provider).

I think the problem is that the chart only uses one pvc for all storage and all pods are mounting this one storage. But my pods are scheduled on different hosts so only the pods on one host can access the storage. All pods on the other host can not access it, because the other host is using the volume obviously..

Maybe a solution is to use multiple pvc's? or some sort of affinity to place them all on the same host? Or is there a more simple solution?

I'm barely new to the Kubernetes terminology, sorry for that :-)

[BUG] Multiattach Error

Describe the bug
Pods will not come good due to multi-attach errors

Environment
GKE

Additional context
Attempting to set this up on a dev cluster using this:

helm upgrade \
  --install --wait --atomic \
  --namespace mailu \
  mailu mailu/mailu \
   --set hostnames={mail.domain.net} \
   --set domain=domain.net \
   --set ingress.tlsFlavor=letsencrypt \
   --set initialAccount.username=admin \
   --set initialAccount.domain=domain.net \
   --set initialAccount.password=XXXXX \
   --set secretKey=XXXXX \
   --set subnet=172.16.0.0/12 \
   --set certmanager.issuerType=ClusterIssuer \
   --set certmanager.issuerName=letsencrypt-production

The chart installs, but timeout due to this:

Multi-Attach error for volume "pvc-01188ee8-96be-11ea-897a-42010a9a00e6" Volume is already used by pod(s) mailu-admin-76f5b54765-cs8kt, mailu-postfix-546cdf5ff7-5t89f

Those pods never come good, helm times out on the wait and purges the chart as it did not install successfully

Freshclam on K8S

Environment & Versions

Environment

• docker-compose
• kubernetes - any version
• docker swarm

Versions

Using v1.8.0, but this applied to any version.

Description

It seems that freshclam is run within the clamav container. While this often works fine, when an orchestrator is in play (K8S), it may (and does regularly for me) corrupt the downloaded DB and cause MailU to stop receiving emails.

Replication Steps

Run MailU on K8S and delete the Clamav pod while freshclam is downloading its DB.

Expected behaviour

One of the principles of using an orchestrator is that no container should ever run a Cron, because the orchestrator is the only one in charge of all the workloads. In the case of MailU, this means that Freshclam (or any other "container crons") should be run in a separate pod via a K8S CronJob object.

Logs

When the problem occurs, the Postfix logs show that the Clamav pod refused the connection and the Clamav logs show that the DB is corrupted.

[BUG] Default API version should be apps/v1

Describe the bug

When you generate a template .yaml file, the API version is extensions/v1beta1, whilst it should be apps/v1, I believe.

Environment

• DigitalOcean

Additional context

persistence config question

Hello,

I have a problem with the hostPath default config.
I'm probably missing something.

my pvc return the following error:
persistentvolume-controller Cannot bind to requested volume "mailu-1582356767-storage": storageClassName does not match
And it has the StorageClass: local-path

Thanks for your help.

values.yaml:

 persistence:
 size: 100Gi
 type: hostPath
 hostPath: /mnt/storage/mailu

pv:

Name:            mailu-1582356767-storage
Labels:          <none>
Annotations:     <none>
Finalizers:      [kubernetes.io/pv-protection]
StorageClass:
Status:          Available
Claim:
Reclaim Policy:  Retain
Access Modes:    RWX
VolumeMode:      Filesystem
Capacity:        100Gi
Node Affinity:   <none>
Message:
Source:
    Type:          HostPath (bare host directory volume)
    Path:          /mnt/storage/mailu
    HostPathType:  DirectoryOrCreate
Events:            <none>

pvc:

Name:          mailu-1582356767-storage
Namespace:     default
StorageClass:  local-path
Status:        Pending
Volume:        mailu-1582356767-storage
Labels:        <none>
Annotations:   <none>
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:      0
Access Modes:
VolumeMode:    Filesystem
Mounted By:    mailu-1582356767-admin-69b787b66d-44xn2
               mailu-1582356767-clamav-68d97df7b-l5h8b
               mailu-1582356767-dovecot-5c65786868-dt8ld
               mailu-1582356767-postfix-599f85f94b-gqvjj
               mailu-1582356767-redis-6f97c6778c-dwfd9
               mailu-1582356767-roundcube-66df597558-4w6wb
               mailu-1582356767-rspamd-f57d66498-65jjx
Events:
  Type     Reason          Age                From                         Message
  ----     ------          ----               ----                         -------
  Warning  VolumeMismatch  12s (x3 over 28s)  persistentvolume-controller  Cannot bind to requested volume "mailu-1582356767-storage": storageClassName does not match

mailu postfix cannot start and when it does, cannot send or receive email

Hello,
i use this chart to install mailuserver and installation seems to go well as every pods starts and proceeed installation at the beginning. Now i'm facing severals issues

• mailupostfix cannot start with an error Mar 24 10:06:29 mail postfix/postfix-script[55]: fatal: the Postfix mail system is already running
• when i log in roundcube, roundcube cannot send mail (error 220 authentication) and cannot retrieve mail for a user i got these kind of error

`imap([email protected])<41270><1v184pah3qgKKgtQ>: Error: chdir(/mail/[email protected]) failed: Stale file handle

Mar 24 10:05:00 imap([email protected])<41268>: Info: Logged out in=102 out=888 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0

Mar 24 10:05:00 imap([email protected])<41270><1v184pah3qgKKgtQ>: Error: stat(/mail/[email protected]/tmp) failed: Invalid argument

Mar 24 10:05:01 imap([email protected])<41270><1v184pah3qgKKgtQ>: Error: stat(/mail/[email protected]/tmp) failed: Invalid argument

Mar 24 10:05:01 imap([email protected])<41270><1v184pah3qgKKgtQ>: Error: stat(/mail/[email protected]) failed: Stale file handle

Mar 24 10:05:01 imap([email protected])<41270><1v184pah3qgKKgtQ>: Error: stat(/mail) failed: Stale file handle

Mar 24 10:05:01 imap([email protected])<41270><1v184pah3qgKKgtQ>: Error: opendir(/mail/[email protected]) failed: Stale file handle

Mar 24 10:05:01 imap([email protected])<41270><1v184pah3qgKKgtQ>: Error: Failed to get quota resource STORAGE: quota-count: Listing namespace '' failed: opendir(/mail/[email protected]) failed: Stale file handle

Mar 24 10:05:01 imap([email protected])<41270><1v184pah3qgKKgtQ>: Info: Logged out in=114 out=820 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0

Mar 24 10:05:06 auth: Debug: auth client connected (pid=41279)`

Is it normal that the volumemount are so different with the version of mailuserver that are in the kubernetes documentation here.

For example in the helm chart the volume for data is in the subpath "dovecotdata" while in the kubernetes docs the volume is mount at the same subpath with the other pods as mail-admin etc ...
the volumes for this chart are very different from documentation while it's seems to be the same images.

I think for example that these error on IMAP are caused by these mismatch on dovecot volumes, in chart the subpath for mail is dovecotmail while in mailu kubernetes doc is "mailstate". Please do someone have mailuserver working correctly with this chart. How to configure it? Thanks

Allow choose certmanager api version

in https://github.com/Mailu/helm-charts/blob/master/mailu/templates/certificate.yaml the apiVersion: cert-manager.io/v1alpha2 is used, that is depricated in newer k8s versions. E.g. in k8s v1.16.x using cert-manager v 0.9.x the new version certificates.k8s.io/v1beta1 is used.

Allow option to specify relay method via SMTPD/SMTPS port instead of straight SMTP

Is your feature request related to a problem? Please describe.
On Google Compute engine, Google blocks outbound port 25 traffic, but does allow SMTPD/SMTPS traffic. Postfix attempts to use port 25 to relay out, and cannot as a result. GKE runs on top of GCE so is subject to the same blocking.

Describe the solution you'd like
An option in the chart to tell mailu to relay out via SMTPD or SMTPS instead of straight SMTP.

Describe alternatives you've considered
None available

Additional context
Reference: https://cloud.google.com/compute/docs/tutorials/sending-mail/

Clean install has three pods not coming up

Describe the bug
Everything should be good to go yet installation is resulting in 3 pods not becoming READY.

Environment

$ k version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.1", GitCommit:"632ed300f2c34f6d6d15ca4cef3d3c7073412212", GitTreeState:"clean", BuildDate:"2021-08-19T15:45:37Z", GoVersion:"go1.16.7", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.1", GitCommit:"632ed300f2c34f6d6d15ca4cef3d3c7073412212", GitTreeState:"clean", BuildDate:"2021-08-19T15:39:34Z", GoVersion:"go1.16.7", Compiler:"gc", Platform:"linux/amd64"}

Additional context

$ k get pods
NAME                               READY   STATUS              RESTARTS         AGE
mailu-admin-574b9d8654-vdslt       1/1     Running             0                46m
mailu-clamav-65bb6fbc4-5k5d9       0/1     CrashLoopBackOff    7 (3m39s ago)    46m
mailu-dovecot-6b4794dcfb-wgrn4     1/1     Running             0                46m
mailu-front-74d69796cd-746nr       0/1     ContainerCreating   0                46m
mailu-postfix-74cd555f-ttw47       1/1     Running             0                46m
mailu-redis-bcb9bfbf6-8x6g2        1/1     Running             0                46m
mailu-roundcube-7546956c69-sw7cm   1/1     Running             0                46m
mailu-rspamd-588879d599-jndsl      0/1     CrashLoopBackOff    10 (2m47s ago)   46m

[BUG] Preserve antispam history on container restart

Describe the bug
See issue #561 in the mailu repo. On container recreating/restart the rspamd logs are lost. The reason for this is that rspamd stores the logs in redis with a key that contains the hostname.

On recreating/restart of the container the hostname changes of the antispam container and for this reason the old logs cannot be retrieved.

The solution is to configure a static hostname for the antispam container. I have no knowledge of kubernetes or helm-charts. Looking at the files I think in this file can be configured that the antispam (rspamd) container uses a static hostname:
https://github.com/Mailu/helm-charts/blob/master/mailu/templates/rspamd.yaml

For docker-compose you can use

antispam:
  hostname: rspamd
  image: mailu/rspamd:$VERSION
  restart: always

I reckon you can do something similar for helm-charts.

Typo in the resources configuration for front

There's a typo of 200Mi rather than 200m on the nginx cpu configuration.

(Discussion) Support external load balancers.

We have 3 PRs for adding external LB support. No doubt that this feature is wanted ;-)

• #74
• #77
• #84

I'd like to discuss which one we'd like to merge of if we can have the best of all.

[BUG] no mechanism to automatically clean up master.pid after postfix pod crash

Describe the bug
If pod crashes abruptly (i.e. some internal posfix error) or postfix is killed without clean shutdown, /queue/pid/master.pid blocks future startup of postfix in newly created pod. Shouldn't /queue/pid folder persistency be the same with container's lifetime ?

Environment
Digital Ocean + PVC on NFS

Expand nodeSelector to other components

Currently, nodeSelector is only applied on the front component.
It would be great to have the ability to force the others components on a specific node.

My use case is that when using longhorn I can't mount the mailu-storage pvc on every pod if they are spread on multiple nodes at the same time.

[feature] Support for handling multiple mail domains

Is your feature request related to a problem? Please describe.
Not an existing problem

Describe the solution you'd like
I think it would be worthwhile to have a mailu Helm installation be able to support multiple mail domains.

At the moment, it appears the helm chart only supports a single mail domain, which is fine for the majority of users, but I manage three domains, each with the possibility of having their own emails.

I would have to deploy three copies of mailu to cover this scenario and configure three installations and make sure they are in sync.

Having a single installation would allow anyone in a similar scenario to myself to only have to configure one installation.

Yes, there are inherent downsides and risk to this such as a single point of failure -- if the one installation goes down, all three mail domains go down, but there is also the easier management for things like security -- you only have to patch one installation or upgrade one installation rather than three and risk forgetting to do one.

Describe alternatives you've considered
Multiple installations of mailu, each configured for its own separate domain

Additional context
N/A

Replace front daemonset with hostport by a front deployment with a service

Hi,

In kubernetes, a daemonset is an object to deploy a specific pod on all nodes or a set of nodes. I think it's a cluster admin object. Here, the chart uses a daemonset to expose a pod outside the cluster. I think it's probably not the better way to achieve it.
I think that replace the daemonset by a deployment and use a service to expose what we need outside the cluster should be better. Actually it will probably be more secure too.
For instance, I'm not sure that theses ports need to be exposed on the WAN :

          - name: smtp-auth
            containerPort: 10025
            hostPort: 10025
            protocol: TCP
          - name: imap-auth
            containerPort: 10143
            hostPort: 10143
            protocol: TCP

I think a good example of what I mean can be found here here.

[BUG] executing "mailu/templates/mysql.yaml" at <eq .Values.database.type "mysql">: error calling eq: invalid type for comparison

Describe the bug
Can not deploy Mailu with the Helm Chart.

Environment

• Kubernetes Platform: Rancher2

Additional context
Values.yaml:

domain: mail.mydomain.com
hostnames:
- mail..mydomain.com
initialAccount:
  domain: mail..mydomain.com
  password: chang3m3!
  username: mailadmin
logLevel: INFO
mail:
  authRatelimit: 100/minute;3600/hour
  messageSizeLimitInMegabytes: 200
persistence:
  size: 100Gi
  existingClaim: mailu
secretKey: chang3m3!

Output:

helm install --namespace=mail --timeout=10m0s --values=/home/shell/helm/values-mailu-0.1.2.yaml --version=0.1.2 --wait=true mailu /home/shell/helm/mailu-0.1.2.tgz
Wed, Sep 29 2021 8:34:53 am | Error: template: mailu/templates/mysql.yaml:1:15: executing "mailu/templates/mysql.yaml" at <eq .Values.database.type "mysql">: error calling eq: invalid type for comparison

front not running: certs volume unavailable

Installing from scratch master (13ff9eb), secret certificate-mailu is still not created, so volume certs can't be mounted, and pod front can't start.

Note: I have to set certManagerPre011: true, since I have an old certmanager on that cluster.

SQLITE FAILURE/ CAUSED ADMIN, POSTFIX and ROUNDCUBE liveness Probe Failure - BUG 49 redux[BUG]

Describe the bug
deploying with latest helm chart shows that all components that use the SQLITE fail to start fully, each throwing errors about database, as a result K8s reports liveness probe failures as was reported in BUG 49 and then closed as a "integration issue with a stack"

Environment
Aks

Additional context
Hello

i have the same issue pulling from the latest chart today.

steps:
helm repo add
helm template -name mail-service mailu/mailu -f values.xml >> my manifest.yaml

updated the SUBNETs that are there from 10.42.0.0./16 to our values.

kubectl apply -f my_manifest.yaml

i get the same issue as the OP, we can see that admin is doing an liveness probe and then getting hung on setting up SQL DB.

here is the logs from Admin
[SQL: SELECT domain.created_at AS domain_created_at, domain.updated_at AS domain_updated_at, domain.comment AS domain_comment, domain.name AS domain_name, domain.max_users AS domain_max_users, domain.max_aliases AS domain_max_aliases, domain.max_quota_bytes AS domain_max_quota_bytes, domain.signup_enabled AS domain_signup_enabled
FROM domain
WHERE domain.signup_enabled = 1]
(Background on this error at: http://sqlalche.me/e/e3q8)
10.196.225.51 - - [14/May/2021:22:36:39 +0000] "GET /ui/login HTTP/1.1" 500 290 "-" "kube-probe/1.18"
[2021-05-14 22:36:44,897] ERROR in app: Exception on /ui/login [GET]
Traceback (most recent call last):
File "/usr/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1243, in _execute_context
self.dialect.do_execute(
File "/usr/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 552, in do_execute
cursor.execute(statement, parameters)
sqlite3.OperationalError: no such table: domain

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/lib/python3.8/site-packages/flask/app.py", line 2292, in wsgi_app
response = self.full_dispatch_request()
File "/usr/lib/python3.8/site-packages/flask/app.py", line 1815, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/usr/lib/python3.8/site-packages/flask/app.py", line 1718, in handle_user_exception
reraise(exc_type, exc_value, tb)
File "/usr/lib/python3.8/site-packages/flask/_compat.py", line 35, in reraise
raise value
File "/usr/lib/python3.8/site-packages/flask/app.py", line 1813, in full_dispatch_request
rv = self.dispatch_request()
File "/usr/lib/python3.8/site-packages/flask/app.py", line 1799, in dispatch_request
return self.view_functionsrule.endpoint
File "/app/mailu/ui/views/base.py", line 26, in login
return flask.render_template('login.html', form=form)
File "/usr/lib/python3.8/site-packages/flask/templating.py", line 133, in render_template
ctx.app.update_template_context(context)
File "/usr/lib/python3.8/site-packages/flask/app.py", line 792, in update_template_context
context.update(func())
File "/app/mailu/init.py", line 37, in inject_defaults
signup_domains = models.Domain.query.filter_by(signup_enabled=True).all()
File "/usr/lib/python3.8/site-packages/sqlalchemy/orm/query.py", line 3161, in all
return list(self)
File "/usr/lib/python3.8/site-packages/sqlalchemy/orm/query.py", line 3317, in iter
return self._execute_and_instances(context)
File "/usr/lib/python3.8/site-packages/sqlalchemy/orm/query.py", line 3342, in _execute_and_instances
result = conn.execute(querycontext.statement, self._params)
File "/usr/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 988, in execute
return meth(self, multiparams, params)
File "/usr/lib/python3.8/site-packages/sqlalchemy/sql/elements.py", line 287, in _execute_on_connection
return connection._execute_clauseelement(self, multiparams, params)
File "/usr/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1101, in _execute_clauseelement
ret = self._execute_context(
File "/usr/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1247, in _execute_context
self._handle_dbapi_exception(
File "/usr/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1466, in _handle_dbapi_exception
util.raise_from_cause(sqlalchemy_exception, exc_info)
File "/usr/lib/python3.8/site-packages/sqlalchemy/util/compat.py", line 383, in raise_from_cause
reraise(type(exception), exception, tb=exc_tb, cause=cause)
File "/usr/lib/python3.8/site-packages/sqlalchemy/util/compat.py", line 128, in reraise
raise value.with_traceback(tb)
File "/usr/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1243, in _execute_context
self.dialect.do_execute(
File "/usr/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 552, in do_execute
cursor.execute(statement, parameters)
sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) no such table: domain

Since its the default - sql lite implementation, we then go over and see that from the deployment there are three services that "arent working"

[dasm@tiserv-ci-00 part2]$ kubectl get pods -n secops-system
NAME READY STATUS RESTARTS AGE
secops-mail-server-mailu-admin-868487c86d-wvtfz 0/1 Running 1 5m59s
secops-mail-server-mailu-admin-d9947d758-mbsbf 0/1 Running 0 3m39s
secops-mail-server-mailu-clamav-7975784689-gzkqs 1/1 Running 0 5m59s
secops-mail-server-mailu-dovecot-549f8fbb4-zr6fd 1/1 Running 0 5m59s
secops-mail-server-mailu-front-7c5dd96647-5r4pw 1/1 Running 0 5m59s
secops-mail-server-mailu-postfix-58f4575d8c-fxtpl 0/1 Running 1 5m59s
secops-mail-server-mailu-redis-5b84b5d987-sbsfd 1/1 Running 0 5m59s
secops-mail-server-mailu-roundcube-5d4685b7f8-7f72v 0/1 Running 3 5m58s
secops-mail-server-mailu-rspamd-6984749897-rt7w2 1/1 Running 0 5m58s
[dasm@tiserv-ci-00 part2]$

ADMIN, POSTFIX and ROUNDCUBE - the common element there is the implementation of sqlite using the shared PVC.

looking at ADMIN gives nothing more than above.
ROUNDCUBE doesnt emit any logs by default

POSTFIX gives us a clue however, in that we can see the PVC that is mounted doesnt have the correct permissions when writing to the shared PVC or at least is not he owner that it things.

[dasm@tiserv-ci-00 part2]$ kubectl logs -f secops-mail-server-mailu-postfix-58f4575d8c-fxtpl -n secops-system
May 14 22:37:21 mail postfix[51]: Postfix is running with backwards-compatible default settings
May 14 22:37:21 mail postfix[51]: See http://www.postfix.org/COMPATIBILITY_README.html for details
May 14 22:37:21 mail postfix[51]: To disable backwards compatibility use "postconf compatibility_level=2" and "postfix reload"
May 14 22:37:22 mail postfix[266]: Postfix is running with backwards-compatible default settings
May 14 22:37:22 mail postfix[266]: See http://www.postfix.org/COMPATIBILITY_README.html for details
May 14 22:37:22 mail postfix[266]: To disable backwards compatibility use "postconf compatibility_level=2" and "postfix reload"
May 14 22:37:22 mail postfix/postfix-script[316]: warning: group or other writable: /queue/.
May 14 22:37:22 mail postfix/postfix-script[317]: warning: group or other writable: /queue/pid
May 14 22:37:22 mail postfix/postfix-script[330]: warning: not owned by postfix: /queue/active
May 14 22:37:22 mail postfix/postfix-script[331]: warning: not owned by postfix: /queue/bounce
May 14 22:37:22 mail postfix/postfix-script[332]: warning: not owned by postfix: /queue/corrupt
May 14 22:37:22 mail postfix/postfix-script[333]: warning: not owned by postfix: /queue/defer
May 14 22:37:22 mail postfix/postfix-script[334]: warning: not owned by postfix: /queue/deferred
May 14 22:37:22 mail postfix/postfix-script[335]: warning: not owned by postfix: /queue/flush
May 14 22:37:22 mail postfix/postfix-script[336]: warning: not owned by postfix: /queue/hold
May 14 22:37:22 mail postfix/postfix-script[337]: warning: not owned by postfix: /queue/incoming
May 14 22:37:22 mail postfix/postfix-script[338]: warning: not owned by postfix: /queue/private
May 14 22:37:22 mail postfix/postfix-script[339]: warning: not owned by postfix: /queue/public
May 14 22:37:22 mail postfix/postfix-script[340]: warning: not owned by postfix: /queue/saved
May 14 22:37:22 mail postfix/postfix-script[341]: warning: not owned by postfix: /queue/trace
May 14 22:37:22 mail postfix/postfix-script[343]: warning: not owned by postfix: /queue/maildrop
May 14 22:37:23 mail postfix/postfix-script[345]: warning: not owned by group postdrop: /queue/public
May 14 22:37:23 mail postfix/postfix-script[346]: warning: not owned by group postdrop: /queue/maildrop
May 14 22:37:23 mail postfix/postfix-script[349]: starting the Postfix mail system

So, i think the chain is that ADMIN is not sending back Liveness probe (thus you dont see runnning) because admin is failing to start cause it cant get the SQLITE DB, POSTFIX starts, but then doesnt send back a liveness probe either.> Roundcube neither.. thus i suspect the SQLITE implementation (whcih ties these together) is impacted

Looking into RoundCube now, i see that same 10.46.0.0/16 SUBNET defined in there, so will try to fix that, but i suspect the liveness probe failure stil comes back to something on the disk with that sqlite coming up - since none of the three components taht use it are working now. the "network error in k8s describe pods" is not a networking issue, since until the component have their DB they cant return http 200

[dasm@tiserv-ci-00 part2]$ kubectl describe pod secops-mail-server-mailu-roundcube-5d4685b7f8-7f72v -n secops-system
Name: secops-mail-server-mailu-roundcube-5d4685b7f8-7f72v
Namespace: secops-system
Priority: 0
Node: aks-default2-25272590-vmss000001/10.196.225.51
Start Time: Fri, 14 May 2021 22:31:45 +0000
Labels: app=secops-mail-server-mailu
component=roundcube
pod-template-hash=5d4685b7f8
Annotations:
Status: Running
IP: 10.196.225.105
IPs:
IP: 10.196.225.105
Controlled By: ReplicaSet/secops-mail-server-mailu-roundcube-5d4685b7f8
Containers:
roundcube:
Container ID: docker://82fb6a599f6d905e6877df94a3b5157655bed3e86f52e062c55fa33fcb9f4bb0
Image: mailu/roundcube:1.8
Image ID: docker-pullable://mailu/roundcube@sha256:2f8ef3466fae7445c60ba35f72cf8535fd768490a7ede819f69f18d27ec08010
Port: 80/TCP
Host Port: 0/TCP
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 1
Started: Fri, 14 May 2021 22:38:22 +0000
Finished: Fri, 14 May 2021 22:40:23 +0000
Ready: False
Restart Count: 4
Limits:
cpu: 200m
memory: 200Mi
Requests:
cpu: 100m
memory: 100Mi
Liveness: http-get http://:http/ delay=0s timeout=5s period=5s #success=1 #failure=30
Readiness: http-get http://:http/ delay=0s timeout=5s period=10s #success=1 #failure=1
Environment:
MESSAGE_SIZE_LIMIT: 20971520
IMAP_ADDRESS: secops-mail-server-mailu-dovecot
FRONT_ADDRESS: secops-mail-server-mailu-front
SECRET_KEY: S0m3th!ngGr38t
SUBNET: 10.42.0.0/16
ROUNDCUBE_DB_FLAVOR: sqlite
Mounts:
/data from data (rw,path="roundcube")
/var/run/secrets/kubernetes.io/serviceaccount from default-token-9lsgv (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
data:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: secops-mail-server-mailu-storage
ReadOnly: false
default-token-9lsgv:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-9lsgv
Optional: false
QoS Class: Burstable
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message

Normal Scheduled 9m15s default-scheduler Successfully assigned secops-system/secops-mail-server-mailu-roundcube-5d4685b7f8-7f72v to aks-default2-25272590-vmss000001
Normal Pulling 9m9s kubelet Pulling image "mailu/roundcube:1.8"
Normal Pulled 9m9s kubelet Successfully pulled image "mailu/roundcube:1.8"
Normal Created 9m9s kubelet Created container roundcube
Normal Started 9m8s kubelet Started container roundcube
Warning Unhealthy 8m (x14 over 9m2s) kubelet Liveness probe failed: Get http://10.196.225.105:80/: dial tcp 10.196.225.105:80: connect: connection refused
Warning Unhealthy 8m (x7 over 9m) kubelet Readiness probe failed: Get http://10.196.225.105:80/: dial tcp 10.196.225.105:80: connect: connection refused
Warning BackOff 4m8s kubelet Back-off restarting failed container
[dasm@tiserv-ci-00 part2]$

Unable to mount volumes for pod

Deploying this to GKE with standard storage class users might face an issue with volumes like the following:

Unable to mount volumes for pod "mailu-postfix-7779bbcb88-4rvzm_mailu(b7dab7b3-42b1-4fb0-8e87-539ca7b04539)"

RollingUpdate will also fail because of that.

Probably this worth being mentioned in the readme as a warning or a solution could be provided.

Rainloop OOTB support

It seems like Mailu already supports Rainloop, it would be great to be able to enable it using helm instead of cube which looks more primitive. Thanks in advance :)

Feature request: allow individual PVCs for each pod

Google Cloud persistent disk, AWS EBS, Longhorn and probably more other storage class don't allow a single PVC to be shared between pods in multiple nodes.

This disallows the ability to have each component of Mailu spread on multiple nodes on those platforms due to the one shared PVC.

I would like to know what's the reason behind having one big PVC shared with all the components? Is it really required to have for example the redis component in the same PVC as the admin component? Why can't it be in its own PVC?

That's my thoughts, let me know if I'm wrong about that. If not would it be feasible to have a PVC for each component?

Setting up Ingress or Service with loadBalancerIp for front service

It's not very clear how to best set up an ingress for the Helm chart. The main site documents how to use Kubernetes, but these generated manifests are different enough that those instructions aren't usable. It is tricky because loadBalancerIps need to be configured and those IPs may overlap with the service. Services furthermore may not be able to share an IP address with nginx, adding another wrinkle.

[BUG]

Describe the bug
Readiness & liveness probes failed. Connection refused in admin. Services unavailable.

Environment

• Kubernetes Platform

values.yaml file content:
`domain: xxx.com
hostnames:

• mail.xxx.com
  clusterDomain: xxx.com
  initialAccount:
  domain: mail.xxx.com
  password: xxx
  username: xxx
  logLevel: INFO
  mail:
  authRatelimit: 100/minute;3600/hour
  messageSizeLimitInMegabytes: 200
  secretKey: xxx
  ingress:
  tlsFlavor: letsencrypt
  persistence:
  existingClaim: mailu-volume-claim
  storageClass: standart
  certmanager:
  issuerType: ClusterIssuer
  issuerName: letsencrypt-prod
  subnet: 10.1.34.0/16`

Additional context
mail system is not reachable at hostname and at hostname, admin, postfix, . Tried with diferent subnets but with no results.

admin pod warnings:
Readiness probe failed: Get http://10.1.34.224:80/ui/login: dial tcp 10.1.34.224:80: connect: connection refused
Liveness probe failed: Get http://10.1.34.235:80/ui/login: dial tcp 10.1.34.235:80: connect: connection refused

clamav pod warnings:
Readiness probe failed: ping failed
Liveness probe failed: ping failed

postfix warnings without messages

With Certmanager 0.12 deployment fails

given:

• rancher kubernetes cluster
• working traefik with certmanager 0.12

At certificate.yaml an acme-part is set.

helm fails with

Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(Certificate.spec): 
unknown field "acme" in io.cert-manager.v1alpha2.Certificate.spec

Imho an acme-part is not defined within certificates.cert-manager.io.

Expose non-HTTP services via NodePorts

Is your feature request related to a problem? Please describe.

Currently, non-HTTP services like SMTP (25) and SMTPS (465) are exposed via hostPort definitions on the Kubernetes node (host) that runs the "front" pod. By default there is 1 replica of the "front" pod.

The administrator needs to know which node/host runs the "front" pod and set the MX/DNS record(s) to that node directly.

This is inherently problematic and results in low availability. The node can die unexpectedly, and as a Kubernetes best-practice, there shouldn't be any assumption for a service running on a specific node. When the "front" pod is moved to another node (after the crash of the og node), the mail services stop immediately since the "front" pod will open the ports on an other IP address and traffic will not come to that until the DNS records are updated and refreshed to clients (TTL).

Currently, the administrator needs to lock the deployment's pod scheduling to a specific node with a nodeSelector.

Describe the solution you'd like

Add the option to expose non-HTTP services on NodePorts.

NodePorts are in a range (e.g.: 30000-32600) but the administrator knows this beforehand (attribute of the cluster) and it can assign a specific nodeport to each service (e.g.: 30025 to SMTP) via the Helm chart variables.

The administrator then sets up local port-forwards on all cluster nodes as needed (e.g.: 25 >> 30025). Cluster nodes are typically automatically provisioned, so this shouldn't be a problem.

Kubernetes will automatically accept mail-related traffic on any of the nodes and internally route it to the "front" container.

From this point the MX/DNS record can be assigned to something like a simple Floating IP which moves automatically to another node when its owner node crashes (I use Hetzner and their fip-controller).

Describe alternatives you've considered

Deploy "front" as DaemonSet (#46)

#46 would result in the "front" container running on all of the cluster nodes which feels like an overkill, even if the "front" container is lightweight.

Additional context

Help with rancher

Hi, I'm using Rancher 2.3.5 and I still haven't been able to make mailu 1.7 work completely.
The following Workloads is not Healthy: front, admin, dovecot, postfix, rspamd
Try searching for existing problems with the certificate, but it was successfully generated.

At what level should I set the logLevel to get the most detail, I can't see any error output in the services that I describe before?

I would appreciate any help. Thanks.

[BUG] mysql database schema and user for MailU don´t be created at startup

Describtion
At first startup no user or database for MailU would be created. So startup without existing database is not working.

Environment

• Kubernetes 1.16.3 with Rancher

values.yaml like this:

database:
  type: mysql
  roundcubeType: mysql
  mysql:
    rootPassword: my-secret-secret
    database: mailu
    user: mailu
    password: my-secret-secret
    roundcubeDatabase: roundcube
    roundcubeUser: roundcube
    roundcubePassword: my-secret-secret

Additional context
For Roundcube i can see database user and schema.

[RSPAMD] make configs in /etc/rspamd/local.d/ configurable

Use case: I wan to make custom entries in

• history_redis.conf, eg increase the history size according to https://rspamd.com/doc/modules/history_redis.html
• whitelists as described in https://gist.github.com/ThomasLeister/f41adad98bb46d0c8418de50b5efb4a0

Possible solution:

in https://github.com/Mailu/helm-charts/blob/master/mailu/templates/rspamd.yaml it could be easy to implement the possibility to mount extra drives in order to overwrite config files via configMap. As the start.py does use templates the right folder to mount the configMap files would be /conf/

• The configMap copuld look like:

{{- if .Values.rspamd.customConfig }}
apiVersion: v1
kind: ConfigMap
metadata:
  name: {{ template "app.name" . }}-rspamd-customConfigMap
data:
# /etc/local.d/
{{- range $cfgName, $cfgContent := .Values.rspamd.customConfig.localD }}
  {{ $cfgName }} : |-
{{ $cfgContent | indent 4 }}
{{- end }}
{{- end }}

• accordingly the rspamd.yaml like:

          volumeMounts:
{{- range $cfgName, $cfgContent := .Values.rspamd.customConfig.localD }}
            - name: customConfig
              mountPath: "/conf/{{ $cfgName }}"
              subPath: {{ $cfgName }}
{{- end }}
...
      volumes:
...
{{- if .Values.rspamd.customConfig.localD }}
        - name: customConfig
          configMap:
            name: {{ template "app.name" . }}-rspamd-customConfigMap
            items:
{{- range $cfgName, $cfgContent := .Values.rspamd.customConfig.localD }}
              - key: {{ $cfgName }}
                path: {{ $cfgName }}
{{- end }}
{{- end }}

• and the values.yml:

rspamd:
  customConfig:
    localD:
      history_redis.conf: |-
        servers = "\{{ REDIS_ADDRESS \}}";
        nrows = 2000;
        compress = true;
        subject_privacy = false;

Deploy "front" as DaemonSet

Is your feature request related to a problem? Please describe.
Currently the front pod will be placed on some node as a deployment with replicas=1. Sure, it is possible to tune the node on which the nginx will be places, but nevertheless, it will be one node. If this node dies, nothing works anymore. Or maybe the pod is rescheduled (when using affinity), but it has no value, as the records are not set correctly.

Describe the solution you'd like
When offering the ability to deploy the front nginx as DaemonSet, the nginx will be placed on every node. Even though some things in regards to mail may not work as expected. But at least the web/admin frontend and maybe some limited mail function would work.

One example where the same approach is followed, is the nginx-ingress controller. See the helm chart where the option controller.kind offers the ability to deploy as a DaemonSet. Together with the options controller.daemonset.useHostPort and controller.hostNetwork the controller binds to the host port and therefore enables defacto LoadBalacner features.

Describe alternatives you've considered
We could of course keep it the current way, but as the nginx is stateless, I also don't see any downturns of this approach. We could also keep the default value to the current deployment way.

Additional context
I would be happy to submit a PR, but let us discuss this approach at first, before I put work into this and it is out of scope or sth like that.

Deployment Specs Missing Selector

I'm a helm newbie, however when I tried to deploy this chart it wouldn't install and intellij seems to agree, that there needs to be a selector in the spec portions of the deployment yamls.
If that's not the case let me know. Otherwise here's a pull request.

Helm documentation

first, its been days ive been "fighting" to deploy mailu on k8s ... i see the kubernetes ymls are broken, and now i find a helm chart with literally 0 documentation or a values.yml "example" ... so again, while mailu is great, i ran it for a very long time on docker. I am getting literally nowhere running it on k8s.

[BUG] Incorrect mailer daemon for more domains

Describe the bug
I deployed this chart with main domain example.com and added new domain myexample.com. Then created mailbox [email protected] and test sending mails to fake/incorrect email address. I quickly get reply from [email protected] with error message. It should reply from same domain as user domain.

Environment

• k3s

Additional context
I think this is caused by single postfix pod with my domain setting. It may be needed to deploy more those pods just to send correct mailer-daemon address. I could not find any information about that in docs. Just need to isolate two groups of users.