Posts by Phinous

    Because it's a long time problem with VHCS, and later iscpCP Omega and finaly i-MSCP, I will try to explain very clearly my purpose.


    On my i-MSCP server, I generaly don't use local mail server.
    Instead, I'm using an external webserver.
    In my experience, it's very boring to manage problem on a mail server (or migrate mailbox), so I prefer externalize this service to a trust compagny :)


    The problem, with i-MSCP, is when the server has to sent a mail to a domain hosted by itself (for example, after a form validation or when you ask a password reset).


    You can easily reproduce the problem by sending manually an email from ssh console :


    Code
    1. echo "Test message" | mail -s "Test message" [email protected]


    ... where mydomain.com is hosted by i-MSCP, but the mailbox [email protected] doesn't exist on this server, but elsewhere, at an external provider.


    On the log, you will have :

    Code
    1. Sep 29 14:14:43 myserver postfix/smtp[13583]: A8B8EA7BED: to=<[email protected]>, relay=none, delay=0.04, delays=0.04/0/0/0, dsn=5.4.6, status=bounced (mail for mydomain.com loops back to myself)


    I dream (from long time ago) of a fonctionnality to set an option like this to a domain : "Don't use local MX for this domain. Send the mails outside, to the Internet"


    I try to use the option "external mail server" without success because my external smtp server need an authentification (Nuxwin said he will help me to test this option with a hook ;) )
    But in my opinion, it could be more simple to just say "lest go the mail outside with local smtp server, and trust the internet to find the good MX".


    I really need a solution to do this king of stuff.
    For now, I have found a durty roundabout : if I need to send a mail to [email protected] from the server (where mydomain.com is hosted by i-MSCP), I create a mail redirection elsewhere from [email protected] to [email protected] (where otherdomain.com IS NOT on the i-MSCP server)
    But is not easy to ask your customer to use this durty tip :)

    Nuxwin : I sent you an email :)


    I read this : Seperated Web and Mail Server - Cant send mails


    In my case, the external mail server is Gandi.net
    The point is Gandi.net's SMTP server need authentification.
    I tried to put "mail.gandi.net" on the "External email server host" field but now, I have this :

    Code
    1. Sep 28 21:07:32 servername postfix/pickup[17393]: F11A517407: uid=0 from=<root>
    2. Sep 28 21:07:32 servername postfix/cleanup[17428]: F11A517407: message-id=<[email protected]>
    3. Sep 28 21:07:32 servername postfix/qmgr[16663]: F11A517407: from=<[email protected]>, size=463, nrcpt=1 (queue active)
    4. Sep 28 21:07:33 servername postfix/smtp[17430]: F11A517407: to=<[email protected]>, relay=agent.mail.gandi.net[217.70.182.5]:25, delay=0.04, delays=0.01/0/0/0.03, dsn=5.7.1, status=bounced (host agent.mail.gandi.net[217.70.182.5] said: 554 5.7.1 <myserver.com[92.24.123.7]>: Client host rejected: Access denied (in reply to RCPT TO command))
    5. Sep 28 21:07:33 servername postfix/cleanup[17428]: 0772E17408: message-id=<[email protected]>
    6. Sep 28 21:07:33 servername postfix/bounce[17431]: F11A517407: sender non-delivery notification: 0772E17408
    7. Sep 28 21:07:33 servername postfix/qmgr[16663]: 0772E17408: from=<>, size=2471, nrcpt=1 (queue active)
    8. Sep 28 21:07:33 servername postfix/qmgr[16663]: F11A517407: removed
    9. Sep 28 21:07:33 servername postfix/local[17432]: 0772E17408: to=<[email protected]>, relay=local, delay=0.03, delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (delivered to command: procmail -a "$EXTENSION")
    10. Sep 28 21:07:33 servername postfix/qmgr[16663]: 0772E17408: removed

    Hi,


    I using i-MSCP 1.1.14, but I generaly don't use mail service.
    Example :
    - the domain.com is hosted by the server which running i-MSCP
    - the mails like [email protected] are hosted by another server


    From ssh on the i-MSCP server, the command :

    Code
    1. echo "test message" | mail -s "test message" [email protected]


    ... make an error :

    Code
    1. postfix/smtp[15528]: BD32117406: to=<[email protected]>, relay=none, delay=0.01, delays=0.01/0/0/0, dsn=5.4.6, status=bounced (mail for domain.com loops back to myself)


    I read than i-MSCP 1.1.14 have an option to set external mx server, but I didn't find the way to use it correctly to solve my problem.
    I don't understand what I should indicate as "External email server host"


    For information, my external mail provider is Gandi.net

    Very nice usefull tips MichaelSchinzel !
    We are confronted to the same problems :)
    In my case, I hopefully generaly use external mail server, so I don't have to much mailbox to move.


    I have started the migration one by one... 65 customers left... a lovely week is annouced :)


    By the way, I was really enjoyed by the upgrade process from Squeeze/i-MSCP 1.0.3 to Wheezy/i-MSCP 1.1.14 on one of my server


    The legacy of i-MSCP (VHCS and after ispCP Omega) made the upgrade process not so easy (and clearly dangerous in my case), but I'm happy now to see Nuxwin manage this wonderfull Control Panel


    It was confort my choice to use i-MSCP for now and for the future :)

    thanks Nuxwin :)


    I have this error during the upgrade to 1.0.7 :

    Code
    1. Starting ispCP update * Stopping services: .......... [ Done ] ispCP main configuration file * Loading old ispCP configuration file: [ Done ] * Update ispCP configuration file: [ Done ] * Check ispCP configuration file: [ Done ] Pre-installation tasks for Debian * Postgrey configuration (Updating listening port): [ Done ] ispCP database * Update ispCP database schema: [ Failed ] [FATAL] An error occurred during update process! Correct it and re-run this program. Log files are stored in /var/log/ispcp/setup You can also find help at http://isp-control.net/forum


    The the log file, I have this :

    Hummm I have a lot of customer on this server (60) so its a little bit boring to move them manually...


    I will try to find an old documentation to make the upgrade to 1.0.7 (not so easy)


    I have another question : what is the best to make upgrade of i-mscp (ou ispcp) : start with a debian upgrade and after make panel upgrade or vice et versa ?