Problems found:
- On web setup, admin user for console password not accepting especial symbols like "!". It just loops asking the user admin for web console and password, until I just type a normal Up&Lower case password.

- After installing, on the web console, everything is turned off on postfix, mailscanner and msmilter.

Problems found:
- On web setup, admin user for console password not accepting especial symbols like "!". It just loops asking the user admin for web console and password, until I just type a normal Up&Lower case password.

- After installing, on the web console, everything is turned off on postfix, mailscanner and msmilter.

I installed again from the .ISO without the kickstarter - normal Centos install. Install GUI had a hard time detecting the Microsoft Virtual Disk, had to select it manually in the partitioning. Other than that the install looked like it complete normally and I ended up with the same screen after reboot.

Ive tried two installs on Hyper-V 2016. Install one was the "Building using github clone for development" script and the other was the "existing CentOS instance" script. The installs both seemed go just fine and I went through the CLI setup ok.

After install I rebooted but the root password did not work on either install so I reset it with the admin account.

After the setup cli EFA-Configure would not work is this expected? Where is this script located searching for EFA-Configure yields nothing? The web gui seems to be working working fine.

[edit]
BTW at login I am not directred to the efa-configure menue.
I found entering "eFa-Configure" worked.

Ive tried two installs on Hyper-V 2016. Install one was the "Building using github clone for development" script and the other was the "existing CentOS instance" script. The installs both seemed go just fine and I went through the CLI setup ok.

I was under the impression that you never even made it that far.

After install I rebooted but the root password did not work on either install so I reset it with the admin account.

This is normal. root is locked during setup. You have to log in with the console user you created during setup.

After the setup cli EFA-Configure would not work is this expected? Where is this script located searching for EFA-Configure yields nothing? The web gui seems to be working working fine.

[edit]
BTW at login I am not directred to the efa-configure menue.
I found entering "eFa-Configure" worked.

Again, you should be logging in as the console user, not root.

Version eFa 4.0.0 RC3 now available in testing repo. Come join us in advancing eFa!

Sorry, I think I hijacked this thread I though it was a pinned subject.

I was under the impression that you never even made it that far.

You may have mistaken me for @toddh. So I have not had any issues with Hypver-V 2016 and EFA v4 with the latest git pull.

Again, you should be logging in as the console user, not root.

Yes, this works with console admin but at login the script is not launching automatically like EFA 3 I must manually launch it. Also it has to be launched with sudo. I dont know if both of these are to expected.

The addition in .bashrc worked and eFa-Configure now launches at login!

The trusted networks option was part of the signature line links logic which have been removed in v4 and superseded with the use of MailWatch, such as the quarantine report auto release function.

You happen to have a link that provides some more details? I have a known public subnet that I need to accept all mail from and it would be considered spam. The mail is coming directly from software like MS SQL and others without any auth.

I added the additional public ip subnet that I want efa to receive mail from and Im getting back:

Client side

The mail could not be sent to the recipients because of the mail server failure. (Sending Mail using Account 1 (2019-02-11T05:31:16). Exception Message: Cannot send mails to mail server. (Error in processing. The server response was: 4.3.0 <unknown[27.xxx.xxx.xxx]>: Temporary lookup failure).
)

update: got it working. I had a "1" in the last octet of the ip on a subnet definition and it wanted a "0" example 45.45.45.1/28(bad) 45.45.45.0/28(good).

I just installed using the eFa v4 Release Candidate 2 build instructions. I couldn't get logged in. It went into a loop while asking me for the "Web Admin Username" and Password. Over and over and over.

I just installed using the eFa v4 Release Candidate 2 build instructions. I couldn't get logged in. It went into a loop while asking me for the "Web Admin Username" and Password. Over and over and over.

I had this issues too. I used "eFa-Configure" from command line notes above on .bashrc for the admin user you created. Also if if you cant log in with root you need to use the admin user you created and update the root password "sudo passwd root" but you need to use the admin userver for "eFa-Configure".

I tried the install several more times on Hyper-V 2016 but met with no success.

Today I ran the install on a standard 2016 server and it complete fine. In fact I installed 2 VMs using the kickstarter in Hyper-V 2016 and both have succeeded.

My earlier attempts were on a Hyper-V 2016 Cluster with clustered storage using Microsoft Storage Spaces Direct 2016. It appears that the clustered environment install is not working at this stage, where Windows Server 2016 Hyper-V works fine.

Once I knew that all is good.

Nice job on the kickstarter setup. Could not have asked for a smoother install process!

If you get prompt "boot:" hit enter and that should take you to the next screen.
At the startup screen(has aquamarine colored test) hit "Tab"
This brings up a string the install uses to configure the install