Virtual Server creation writes code in the wrong .conf

Until some time ago (3 months I guess, in which I did each and every update), when ever I created a new Virtual Server it created a conf file in /etc/apache2/sites-enabled/.conf

which contained among others the following lines:

RewriteCond %{HTTP_HOST} =webmail. RewriteRule ^(.) https://:20000/ [R] RewriteCond %{HTTP_HOST} =admin. RewriteRule ^(.) https://:10000/ [R]

While these rules, especially the second one were not really useful to me, they are no written to a different file.

I defined a template which automatically include a second conf by inserting 'Include /…/…/Someconf.conf' (shared for all Virtual Server) in to each Virtual Server conf.

It always worked, but recently instead of writing the 4 above mentioned lines of code in to the Virtual Server's own conf, it inserts them into the shared conf.

The location where the line are written are directly behind a existing RewriteRule.

RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-f #existing rule in shared conf RewriteCond %{REQUEST_URI} /icons/(.).(gif|jpg|jpeg|png)$ #existing rule in shared conf RewriteRule ^(.) /icons/generic.png #last line of existing rule in shared conf RewriteCond %{HTTP_HOST} =webmail. RewriteRule ^(.) https://:20000/ [R] RewriteRule ^(.) /icons/generic.png #even more strange, as it does not write the admin. RewriteCond, but copies the last line of the existing rule in the shared conf RewriteRule ^(.*) https://:10000/ [R]

I was able to reproduce this on several Servers.