".forward has bad owner uid 110" and "Suspicious rcfile" in mail.log

Discussion in 'Installation/Configuration' started by gauthier, Jun 9, 2011.

  1. gauthier

    gauthier New Member

    Hi all,

    I am using ISPConfig 2.2.39 on debian 5.0 (perfect setup followed about one year ago).

    I am now having some trouble sending or receiving emails. My mail.log shows:

    .forward has -rwxr-xr-x permissions and owner/group is admispconfig

    This is not just a forwarding problem as emails are not being received on server.

    Can anybody help me?

    Thankyou very much.
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Seems as if a wrong path to the mail or web directory is set in the server settings. The directory must be /var/www and not /home/admispconfig/ispconfig/web
     
  3. gauthier

    gauthier New Member

    Thanks. I'll try to be clear, forgive my bad english.

    My webs, users, Maildir... are actually located in

    /home/admispconfig/ispconfig/web/multidoc/edit

    I did not configure this. By somehow it came by default (maybe something I have done wrong during installation). I had to create a symbolic link in /var, named www and pointing to /home/admispconfig/ispconfig/web/multidoc/edit. All ran ok (webs, users...). Until last upgrade it seems.

    Now, in server settings, "Document Root" is /home/admispconfig/ispconfig/web/multidoc/edit. I am unsure I can change this value as it can be a change difficult to undone if I loose access to ISPConfig control panel.

    What I am planning to do is:

    - backup ISPConfig database,
    - Change Document Root to /var/www in server settings
    - remove www symbolic link in /var
    - move www directory from /home/adm... to /var

    Any suggestion?

    Thanks
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    Maildirs on a ISPConfig System are never located in /home/admispconfig/ispconfig/web/multidoc/edit so there must have been gone something wrong during update.

    Yes, that might be the best solution. The document root setting does not affect the ispconfig controlpanel interface, so changing this can not cause the panel to become unavailable.
     

Share This Page