issues after 3.0.2.6 update

General eFa discussion
Post Reply
x-lr8
Posts: 8
Joined: 29 Nov 2018 05:25

issues after 3.0.2.6 update

Post by x-lr8 »

just installed vm image for 3.0.2.5 ran updates to 3.0.2.6 mail stopped flowing, fixed issues with clamav and vmwaretools, mail flowed again.
now i cannot login to webinterface i have reset password using EFA-Configure and i can login locally using my root and admin passwords, but still not via the web interface and now email has stopped flowing

/var/log/maillog:
Nov 28 21:36:52 mail postfix/smtpd[4488]: connect from mail-oln040092002023.outbound.protection.outlook.com[40.92.2.23]
Nov 28 21:36:52 mail postfix/smtpd[4488]: Anonymous TLS connection established from mail-oln040092002023.outbound.protection.outlook.com[40.92.2.23]: TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)
Nov 28 21:36:53 mail postfix/smtpd[4488]: NOQUEUE: reject: RCPT from mail-oln040092002023.outbound.protection.outlook.com[40.92.2.23]: 454 4.7.1 <rcastillo@cityofmontclair.org>: Relay access denied; from=<mastermind16@hotmail.com> to=<rcastillo@cityofmontclair.org> proto=ESMTP helo=<NAM01-SN1-obe.outbound.protection.outlook.com>
Nov 28 21:36:53 mail postfix/smtpd[4488]: disconnect from mail-oln040092002023.outbound.protection.outlook.com[40.92.2.23] ehlo=2 starttls=1 mail=1 rcpt=0/1 quit=1 commands=5/6
Nov 28 21:40:13 mail postfix/anvil[4490]: statistics: max connection rate 1/60s for (smtp:40.92.2.23) at Nov 28 21:36:52
Nov 28 21:40:13 mail postfix/anvil[4490]: statistics: max connection count 1 for (smtp:40.92.2.23) at Nov 28 21:36:52
Nov 28 21:40:13 mail postfix/anvil[4490]: statistics: max cache size 1 at Nov 28 21:36:52
Nov 28 21:41:20 mail postfix/postfix-script[6359]: stopping the Postfix mail system


any ideas? I have since switched back to my old email filter and will revisit this again tomorrow. Since this is a new install should i just start over again? Thanks for the help. :)
henk
Posts: 518
Joined: 14 Dec 2015 22:16
Location: Netherlands
Contact:

Re: issues after 3.0.2.6 update

Post by henk »

Did you check the update log for issues? and had a look at viewtopic.php?t=2892
“We are stuck with technology when what we really want is just stuff that works.” -Douglas Adams
x-lr8
Posts: 8
Joined: 29 Nov 2018 05:25

Re: issues after 3.0.2.6 update

Post by x-lr8 »

update logs show everything completeing successfully. since this VM was just installed yesterday i assume the patch to fix the mailscanner naming issue has been fixed, i added the symlink: ln -s /etc/init.d/mailscanner /etc/init.d/MailScanner restarted still cannot login to the web interface. i just get bad username/password.
x-lr8
Posts: 8
Joined: 29 Nov 2018 05:25

Re: issues after 3.0.2.6 update

Post by x-lr8 »

ok i can login to the webinterface now but only using the IP in the URL i get bad username/password when i use its FQDN.
going to check and see if mail flows properly now.
x-lr8
Posts: 8
Joined: 29 Nov 2018 05:25

Re: issues after 3.0.2.6 update

Post by x-lr8 »

mail is not flowing properly:
Nov 29 12:12:38 mail postfix/smtpd[21602]: connect from mail-oln040092002084.outbound.protection.outlook.com[40.92.2.84]
Nov 29 12:12:38 mail postfix/smtpd[21602]: Anonymous TLS connection established from mail-oln040092002084.outbound.protection.outlook.com[40.92.2.84]: TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)
Nov 29 12:12:39 mail postfix/smtpd[21602]: NOQUEUE: reject: RCPT from mail-oln040092002084.outbound.protection.outlook.com[40.92.2.84]: 454 4.7.1 <rcastillo@cityofmontclair.org>: Relay access denied; from=<mastermind16@hotmail.com> to=<rcastillo@cityofmontclair.org> proto=ESMTP helo=<NAM01-SN1-obe.outbound.protection.outlook.com>
Nov 29 12:12:39 mail postfix/smtpd[21602]: disconnect from mail-oln040092002084.outbound.protection.outlook.com[40.92.2.84] ehlo=2 starttls=1 mail=1 rcpt=0/1 quit=1 commands=5/6


not sure why im getting: Relay access denied
x-lr8
Posts: 8
Joined: 29 Nov 2018 05:25

Re: issues after 3.0.2.6 update

Post by x-lr8 »

fixed it: was missing my domain in the transport settings. everything appears to work now except for the ip in the URL issue but that is likely due to self-signed certificate being used, this will get updated to my wildcard soon.
Post Reply