View Single Post
  #1  
Old 16th April 2012, 12:15
andyb2000 andyb2000 is offline
Junior Member
 
Join Date: Feb 2012
Posts: 4
Thanks: 0
Thanked 0 Times in 0 Posts
Talking Emails causing Unable to create a dot-lock file

Hi folks,

This may just be a logical error that I've done, if so please point me in the right direction!

I've got quite a few domains attached to my Email setup, so my setup is:

Under Email Accounts > Domain I have the primary domain setup "example.com"
I then setup an Email mailbox "andy@example.com".
I then setup a Domain Alias for "@example.co.uk" forwarding to "@example.com".

So emails work if sent to andy@example.com or andy@example.co.uk. The problem comes if somebody sends an email to "fred@example.co.uk", the alias works and it tries to forward it to the example.com, but because fred@example.com doesn't exist (and I don't want it to exist!) it causes maildrop to get angry:

Code:
E29691036B1     2732 Sun Apr 15 18:14:59  fred@example.co.uk
(temporary failure. Command output: ERR: authdaemon: s_connect() failed: Permission denied /usr/bin/maildrop: Unable to create a dot-lock at /var/vmail/example.com/fred/10677.0.vhost.)
                                         fred@example.com
Is there a simple solution to this, should I be creating a dummy catch-all to drop the mail or something, ideally I want these emails bounced with invalid recipient.

Thanks in advance.
Reply With Quote
Sponsored Links