new per-ip postfix logic problems

Submitted by q7joey on Fri, 12/05/2014 - 16:48

add site 1 on shared ip, enable ssl

add site 2 on private ip, enable ssl

add site 3 on shared ip, enable ssl (this is ok with sni ssl extension)

disable ssl on site 3

this will cause virtualmin to remove the postfix master.cf config for the shared ip

delete site 2

postfix master.cf info for private ip will not be removed, so postfix won't start because it can't bind to that ip.

i haven't tested enough to know if the second problem only happens after the first one has already been done.

this also occurred with a debian based system.

Status: 
Closed (fixed)

Comments

Submitted by q7joey on Fri, 12/05/2014 - 17:01

it does look like the second issue is only triggered after hitting the first problem.

Submitted by JamieCameron on Sat, 12/06/2014 - 16:44

Thanks for pointing this out - this is a Virtualmin bug which will be fixed in the next release.

Submitted by Issues on Sat, 12/20/2014 - 16:46

Automatically closed -- issue fixed for 2 weeks with no activity.

Submitted by q7joey on Tue, 01/06/2015 - 16:05

i'm not sure if the latest webmin update mades things worse or i missed something with my initial report.

if i repeat the steps in the main report, i find that immediately after step 3 (2nd ssl site on shared ip), the postfix config is messed up. no need to disable ssl to break things.

any idea when a virtualmin release will be coming?

Submitted by JamieCameron on Tue, 01/06/2015 - 20:49

We are creating the new 4.13 release right now.

Submitted by q7joey on Wed, 01/07/2015 - 17:37

new version does not fix the problem. i'm investigating more.

Submitted by q7joey on Thu, 01/08/2015 - 15:52

same problem there. but it looks like i misdiagnosed it the first time. the steps necessary for a completely new install are:

  1. create server1 with ssl
  2. copy ssl cert to postfix
  3. create server2 with ssl and private ip
  4. create server3 with ssl on shared ip

at this point, the postfix config for the shared ip will be gone and mail stops flowing.

Submitted by JamieCameron on Thu, 01/08/2015 - 19:58

In step 4, is the "shared IP" the primary IP address of the system, or a different shared IP?

Submitted by q7joey on Thu, 01/08/2015 - 21:49

the primary ip of the system.

Submitted by JamieCameron on Fri, 01/09/2015 - 19:21

Ok, I see another cause of this bug - it can happen if a domain on the shared IP wasn't setup first. I'll fix that up..

Submitted by q7joey on Wed, 02/04/2015 - 12:08

it looks like this problem is now fixed.

but, i just found a related issue. the smtps (ssl always) port does not seem to be getting split into separate listeners for each ip. just smtp and submission get that treatment.

new ticket? or just continue to use this one?

Submitted by JamieCameron on Thu, 02/05/2015 - 11:37

That sounds like a bug - could you open a new ticket with before & after config files for the smtps issue?