[SOLVED] Possible bug ISPC 3.3.1p1 Debian 13 Email Routing Error The Domain is already set as a E-Ma

Discussion in 'General' started by Ignacio Garcia, May 12, 2026.

  1. Hello everyone and thanks in advance for your help.

    I'm scratching my head here, this is something that does not happen in all my other installations with Debian 12 and ISPC < 3.3. Posting it here before I fill in a bug report to see if someone can confirm this.

    I just installed a multi server system on 3 machines with Debian 13 with ISPC 3.3.1p1 using the autoinstaller
    w0.example.com -> master with panel, web server, ftp server and dns server (--no-mail --interactive)
    m0.example.com -> slave with mail server and dns server (mx1) (--no-web --interactive --use-php=system)
    m1.example.com -> slave with mail server and dns server (mx2) (--no-web --interactive --use-php=system)

    Everything went fine at install, everything seems to be working fine, but this:

    1.- Go to Email -> Domain -> Add New Domain -> Server: m0.example.com , Client: empty , Domain: domain.tld , Spamfilter: - not enabled - , Active: yes , Local Delivery: yes -> SAVE
    2.- Go to Relay Recipients -> Add New Relay Recipient -> Server: m1.example.com, Relay Recipient: @domain.tld , Active: yes -> SAVE
    3.- Go to Email Routing -> Add New Transport -> Server: m1.example.com, Domain: domain.tld , Type: smtp , No MX lookup: no , Destination: m0.example.com , Sort by: 5, Active: yes -> SAVE

    Then, at this windows I get an error: The Domain is already set as a E-Mail Domain. and won't save

    This is the procedure I've always followed to have m1.example.com accept and later relay mails destined to m0.example.com in case m0.example.com is down. In all my previous severs this works, but on this last setup it won't.

    Am I doing something wrong? Am I missing something? Any help is truly appreciated.

    Thanks so so much for your help

    Regards,

    Ignacio
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    You can have a domain either as email routing or a local domain, but not both. So the error is correct; it informs you about that fact.

    Update:

    Ok, I see now that the routing and email domain are on different systems of your multiserver setup. This should indeed not happen and needs to be fixed. You just can not have the relay record and email domain on the same system.
     
    Ignacio Garcia likes this.
  3. That's what I thought. Should I fill in a bug report? Is there anything I can do in the meantime to make it work? Unfortunately to me I must deliver this server soon for production and I'm quite worried I won't be able to do it.
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    I'll add a issue request and will look into that today. I'm sure its just a single line change, you can easily patch that manually without a full update on your system. There must be just a " ... and server_id = X ... " missing somewhere in a sql query.
     
    Ignacio Garcia likes this.
  5. Oh, Till, you're the best. Thanks so much! Waiting for news from you. Thanks!!!!!!
     
    till likes this.
  6. till

    till Super Moderator Staff Member ISPConfig Developer

  7. till

    till Super Moderator Staff Member ISPConfig Developer

  8. Unfortunately I can't download it. Not sure why git kicks me out "You reached your rate limit. Retry later", but I've done nothing but get into that page. Could you please send it to me by email? yo at ignasi dot com . It might be necessary to put it in a zip file with a password.

    I'll test it the moment I receive it for sure.

    Thanks a lot!
     
    Last edited by a moderator: May 12, 2026
  9. till

    till Super Moderator Staff Member ISPConfig Developer

    Please find the file attached to this post. Just unzip it before uploading.
     

    Attached Files:

  10. Hello Till. Thanks a lot for your help

    Your modifications allowed me to save the Email Routing without problems... but:

    After that, I've done the basic test: shutting down the m0.example.com server, send a message to an account in this server, and hope that message will be accepted by m1.example.com (step 2 in my first message, Relay Recipients, is done and active). However, message is not accepted by m1.example.com. Here's the error:


    This is the mail system at host mail.anotherdomain.com.

    I'm sorry to have to inform you that your message could not
    be delivered to one or more recipients. It's attached below.

    For further assistance, please send mail to postmaster.

    If you do so, please include this problem report. You can
    delete your own text from the attached returned message.

    The mail system

    <[email protected]>: host m1.example.com[11.22.33.44] said: 554 5.7.1
    <[email protected]>: Relay access denied (in reply to RCPT TO command)

    This same config works in all my other servers with ISPC < 3.3 . Is there any chance something's not working here?

    Thanks so much for your help

    Ignacio
     
  11. UPDATE: This morning I have deleted all email relaying rules, mailboxes and domain, redid everything and now it works. Not sure why

    I've done some digging in Relay Recipients and something does not look good IMHO:


    If I configure it as the ispc manual says, that is
    Server m1.example.com
    Recipient address @domain.tld

    and I do queries using postconf in m1.example.com:
    postmap -q @domain.tld mysql:/etc/postfix/mysql-virtual_relayrecipientmaps.cf
    result empty (not good)
    postmap -q [email protected] mysql:/etc/postfix/mysql-virtual_relayrecipientmaps.cf
    result empty (expected)

    If I configure as this:
    Server m1.example.com
    Recipient address [email protected]

    and I do a query using postconf in m1.example.com:
    postmap -q [email protected] mysql:/etc/postfix/mysql-virtual_relayrecipientmaps.cf
    result again empty (WTF!, this is the email address only, no good at all)

    However, if I configure it as this (not what the manual recommends)
    Server m1.example.com
    Recipient address domain.tld (without the @)

    and I do queries like these:
    postmap -q [email protected] mysql:/etc/postfix/mysql-virtual_relayrecipientmaps.cf
    postmap -q @domain.tld mysql:/etc/postfix/mysql-virtual_relayrecipientmaps.cf
    results are both empty as expected,
    but if I do this query:
    postmap -q domain.tld mysql:/etc/postfix/mysql-virtual_relayrecipientmaps.cf
    then I get an OK

    Maybe I'm missing something else here, but could it be that somewhere, something does not interpret the @ correctly?

    Thanks so much in advance for your help
    Ignacio
     
    Last edited: May 13, 2026

Share This Page