Closed kryskool closed 6 years ago
From @stooj on September 27, 2017 10:0
It looks like I have two rows in my amavis policy table with the same policy_name
value.
Could this have been caused by the following actions?
example.com
user@example.com
user@example.com
user@example.com
, which exists on the old server?From @stooj on September 27, 2017 10:56
I've deleted the second record in the policy table, using a django shell.
from modoboa_amavis.models import Policy
offending = Policy.objects.filter(policy_name='@example.co.uk')[-1]
offending.delete()
Trying again, still get an error, but to do with users now. There is no user, which was presumably deleted during the policy deletion.
from modoboa_amavis.models import Users, Policy
policy = Policy.objects.get(policy_name='@example.co.uk)
me = Users(priority=7, policy=policy, email='@example.co.uk', fullname='@example.co.uk')
me.save()
I can now create and delete alias domains. 🎆
When setting up the server, I made one change directly to the database:
ALTER TABLE modoboa_imap_migration_migration ALTER COLUMN _password TYPE varchar(255);
Aside from that, this is a stock modoboa installation, so I must have done something through the interface that got me into this state.
From @stooj on September 27, 2017 9:44
Impacted versions
Steps to reproduce
Create a domain (
example.com
) After the domain has been created, edit it and add an alias (mail.example.com
)Current behavior
HTTP 500 - internal error
Expected behavior
A new alias should be created, or an error message explaining that subdomains are not permitted.
Traceback
Copied from original issue: modoboa/modoboa#1254