Posts by Nuxwin

  • How safe is to upgrade from 1.3.16 to latest current stable?

    Quote from innodapt

    Initially, I had planned to upgrade to 1.5.3 (the current stable release at this time), however this upgrade was stymied by a recently discovered issue with Composer. Thankfully, the current development release (1.5.x) addresses this issue, resulting in a trouble-free direct upgrade.

    The fix is also in latest released version ;) You should avoid using git version and update to i-MSCP 1.5.3 (build 2018120800) RELEASED ;)

  • Error in i-MSCP 1.5.3 - maintenance release (testing) on Ubuntu 18.04

    Quote from innodapt

    Laurent,


    Thank you so much for this fix! I was upgrading from 1.3.16 to 1.5.3 and my heart dropped when I got the “SHA384 is not supported by your openssl extension…” error. I found this thread searching for an explanation, and “VIOLA!” (as we say here—I am a composer and conductor.)


    I am happy to report that with this fix, I was able to upgrade directly from 1.3.16 to 1.5.x with ease. Hooray!

    You're welcome ;)

  • Multi E-Mail Addresses

    UncleSam


    I've just made a test with the following entries:


    Code
    1. root@bionic:/etc/postfix/imscp# cat domains
    2. # Postfix domains map - auto-generated by i-MSCP
    3. # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
    6. bbox.nuxwin.com OK


    Code
    1. # Postfix aliases map - auto-generated by i-MSCP
    2. # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
    5. alias@bbox.nuxwin.com whatever@bbox.nuxwin.com
    6. whatever@bbox.nuxwin.com whatever@bbox.nuxwin.com,alias@bbox.nuxwin.com


    This seem to work as expected (no loop).

    Below the SMTP session (sending mail to alias@bbox.nuxwin.com which is an alias of whatever@bbox.nuxwin.com :



    Note: Don't pay attention to the warning regarding TLS... (self-signed cert)...


    As you can see, the mail sent to alias@bbox.nuxwin.com (alias address) has been delivered into the whatever@bbox.nuxwin.com mailbox. This is what you expect. My thinking is that this would cause a loop but it seem that not the case... I need to do more tests to be sure but if that still OK, I'll improve the feature, automatically adding required entries for aliases (when those belong to a domain that is hosted locally).


    The received mail (source)

  • Multi E-Mail Addresses

    UncleSam


    Right now, when creating a normal + forward account, we end with something as follow (alias map):


    Code
    1. # Postfix aliases map - auto-generated by i-MSCP
    2. # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
    5. whatever@bbox.nuxwin.com whatever@bbox.nuxwin.com,alias@bbox.nuxwin.com


    Here, any mail sent to the whatever@bbox.nuxwin.com mail account would be:

    1. Delivered to the whatever@bbox.nuxwin.com mailbox
    2. Forwarded to the alias@bbox.nuxwin.com alias

    This is the current behavior but you, you want also be able to send mail to aliases:


    Code
    1. # Postfix aliases map - auto-generated by i-MSCP
    2. # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
    5. whatever@bbox.nuxwin.com whatever@bbox.nuxwin.com,alias@bbox.nuxwin.com
    6. alias@bbox.nuxwin.com whatever@bbox.nuxwin.com


    This is the same as above but with another alias entry. Mail sent to the alias@bbox.nuxwin.com would be:

    1. Forwarded to the alias@bbox.nuxwin.com

    You see the problem here? This create a loop and you would end with a "loopback to myself" error:


    Mail sent to alias => forwarded to whatever => forwarded to alias => forwarded to whatever... (LOOP)

  • Multi E-Mail Addresses

    Quote from UncleSam

    Ok I tried what you said:

    - Changed my mail account from mail to mail+forward

    - Added onw forward address to the list called "testaddress@domain.tld"

    - Send a mail to "testaddress@domain.tld"

    - Got error (User unknown in virtual mailbox table)

    Basically, what you want is ability to send mails to aliases in which case, the mails should be delivered into the mailbox of the mail account for which you have defined them. Problem is that aliases don't always belong to locally hosted domains.. You can have an alias address such as user@gmail.com ... But I'll check the behavior and see if we can add specific "rules" for aliases that belong to local domains. By local, I mean those for which domains are hosted locally. In reality, those are virtual domains...

  • Multi E-Mail Addresses

    Quote from kess

    What UncleSam needs is the exact opposite. e-mail incoming on multiple mailboxes or aliases on the server gets redirected to a single mailbox.

    This beahviour is possible at present, but you need to create a Forward mailbox for each single needed alias.

    If you create a normal + forward account as follows:


    mail account: l.declercq@nuxwin.com


    forward (aliases) : l.declercq1@nuxwin.com l.declercq2@nuxwin.com l.declercq3@nuxwin.com


    then send a message to one of the aliases, mail will be delivered into the l.declercq@nuxwin.com mailbox.


    That's what you want? If yes, what you want is to be able to create local mailboxes from provided aliases list... That's a bit tedious... Such feature isn't provided by other panels. You need first create the local mailboxes, then, list them in aliases list if needed. I don't know any panel which will create the local mailboxes using alias addresses list automatically. And here, I don't talk about possible "loopback to myself" problems...

  • Multi E-Mail Addresses

    Quote from kess

    Today it's possible with i-MSCP too, but you have to create a mail forward for each of these aliases that gets redirected to the "principal" mailbox.

    No true. You need only create a mail account + forward account (same form), then add your aliases (same form)... You do not have to create each mail forward account separately. Note that a forward mail account is nothing more than an alias.