How to disallow a clients to make changes on codomains

Discussion in 'Feature Requests' started by JGrewe, May 17, 2007.

  1. JGrewe

    JGrewe Guest

    Hello,

    a client have two co-domains.
    But he can delete them an make others. How can i disallow that?

    Janko
     
    Last edited by a moderator: May 17, 2007
  2. Hans

    Hans Moderator Moderator

    You can not overcome that the client deletes his domain and/or co-domain.
    The only thing you can do is set the amount of domains to a maximum, to avoid to much domains/co-domains.
     
  3. JGrewe

    JGrewe Guest

    Hello!

    OK, my question:

    My client deletes one Co-Domain and takes instead a popular domain as Co-Domain. Now he can get every eMail from my other clients to that popular domain... because Postfix will deliver these eMails to that Co-Domain?

    Is it right, or make I a mistake?


    Thanks,
    Janko

    PS: I am sorry about my bad english :eek:
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    He can not do that because if the domain is assigned already to another account on your server, he can not it as co-domain to his account.
     
  5. JGrewe

    JGrewe Guest

    Hello,

    when this popular Domain is not hostet on my server, so he can use that domain. My other client are using my postfix to send eMails. Now if they want to send an email to that popular domain, the email instead is deliverd to the co-domain on my server....


    Janko
     
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    ISPConfig includes a check that tests if the mx and A records of a domain are pointing to your server and sets a co-domain to external mailserver in this case. So the client is not able to receive any emails, even if he aggs gmail.com as co-domain.

    This has been integrated some time ago, I'am not sure in which ISPConfig version.
     
  7. JGrewe

    JGrewe Guest

    Hello!

    Thank you....
    Now i can use ISPConfig!

    Perfect Program :)


    Janko
     
  8. JGrewe

    JGrewe Guest

    Hello!

    I have add gmail.com as Co-Domain. And now I can retrieve all eMails sent on my postfix to gmail.com. ISPConfig have allow to set Mailserver to "Lokal Mailserver".

    I use ISPConfig 2.2.12 on Debian 4.0.....

    My Bind9 is disabled, but dig shows me the right MX- and A-Record for gmail.com!

    Code:
    [15:59:13][root]/var/www/web1/user/web1_jgrewe/Maildir/new # dig mx gmail.com
    
    ; <<>> DiG 9.3.4 <<>> mx gmail.com
    ;; global options:  printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21261
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 4, ADDITIONAL: 11
    
    ;; QUESTION SECTION:
    ;gmail.com.                     IN      MX
    
    ;; ANSWER SECTION:
    gmail.com.              474     IN      MX      50 gsmtp163.google.com.
    gmail.com.              474     IN      MX      50 gsmtp183.google.com.
    gmail.com.              474     IN      MX      5 gmail-smtp-in.l.google.com.
    gmail.com.              474     IN      MX      10 alt1.gmail-smtp-in.l.google.com.
    gmail.com.              474     IN      MX      10 alt2.gmail-smtp-in.l.google.com.
    
    ;; AUTHORITY SECTION:
    gmail.com.              166114  IN      NS      ns4.google.com.
    gmail.com.              166114  IN      NS      ns1.google.com.
    gmail.com.              166114  IN      NS      ns2.google.com.
    gmail.com.              166114  IN      NS      ns3.google.com.
    
    ;; ADDITIONAL SECTION:
    gmail-smtp-in.l.google.com. 86  IN      A       66.249.93.27
    gmail-smtp-in.l.google.com. 86  IN      A       66.249.93.114
    alt1.gmail-smtp-in.l.google.com. 293 IN A       209.85.133.114
    alt1.gmail-smtp-in.l.google.com. 293 IN A       209.85.133.27
    alt2.gmail-smtp-in.l.google.com. 264 IN A       72.14.205.27
    gsmtp163.google.com.    741     IN      A       64.233.163.27
    gsmtp183.google.com.    6966    IN      A       64.233.183.27
    ns1.google.com.         167896  IN      A       216.239.32.10
    ns2.google.com.         167896  IN      A       216.239.34.10
    ns3.google.com.         167517  IN      A       216.239.36.10
    ns4.google.com.         167896  IN      A       216.239.38.10
    
    ;; Query time: 114 msec
    ;; SERVER: 192.168.255.1#53(192.168.255.1)
    ;; WHEN: Fri May 18 16:01:11 2007
    ;; MSG SIZE  rcvd: 406
    
    /etc/postfix/virtualusertable
    Code:
    [email protected]    web1_jgrewe
    [email protected]    web1_jgrewe
    [email protected]    web1_jgrewe
    [email protected]    web1_jgrewe
    [email protected]    web1_jgrewe
    [email protected]    web1_jgrewe
    telnet at port 25:
    Code:
    220 server1.example.com ESMTP Postfix (Debian/GNU)
    ehlo localhost
    250-server1.example.com
    250-PIPELINING
    250-SIZE 10240000
    250-VRFY
    250-ETRN
    250-STARTTLS
    250-AUTH LOGIN PLAIN
    250-AUTH=LOGIN PLAIN
    250-ENHANCEDSTATUSCODES
    250-8BITMIME
    250 DSN
    mail from: me@localhost
    250 2.1.0 Ok
    rcpt to: [email protected]
    250 2.1.5 Ok
    data
    354 End data with <CR><LF>.<CR><LF>
    Subject: This mail is a example
    
    .
    250 2.0.0 Ok: queued as 685D113788
    Comming eMail:
    Code:
    [15:59:03][root]/var/www/web1/user/web1_jgrewe/Maildir/new # more  1179496659.5623_0.home.grewe-server.de
    Return-Path: <me@localhost>
    X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on home.grewe-server.de
    X-Spam-Level: *
    X-Spam-Status: No, score=1.3 required=5.0 tests=ALL_TRUSTED,MISSING_SUBJECT,
            NO_REAL_NAME,UNDISC_RECIPS autolearn=no version=3.1.8
    X-Original-To: [email protected]
    Delivered-To: [email protected]
    Received: from localhost (BUERO.mshome.net [192.168.255.1])
            by server1.example.com (Postfix) with ESMTP id 685D113788
            for <[email protected]>; Fri, 18 May 2007 15:56:25 +0200 (CEST)
    Message-Id: <[email protected]>
    Date: Fri, 18 May 2007 15:56:25 +0200 (CEST)
    From: me@localhost
    To: undisclosed-recipients:;
    X-Virus-Status: No
    X-Virus-Checker-Version: clamassassin 1.2.3 with clamscan / ClamAV 0.90.2/3265/Thu May 17 16:19:47 2007
    
    Subject: This mail is a example
    
    [15:59:13][root]/var/www/web1/user/web1_jgrewe/Maildir/new #
    What have i done wrong?

    Janko
     
  9. till

    till Super Moderator Staff Member ISPConfig Developer

    It might be not included yet in the stable branch yet. It is definately part of the svn version. You will ahve to look at the svn log if you need to know this in detail.
     
  10. JGrewe

    JGrewe Guest

    Hello,

    where can i read the svn log (i don´t know what is it).

    I have modified the PHP-Code, now no client can add a Co-Domain... only the admin. Not fine but works well.

    Thanks,
    Janko
     
  11. till

    till Super Moderator Staff Member ISPConfig Developer

    You can read the SVN log with anym SVN (subversion) client. The URL of the ISPConfig svn repository is listed on the ISPConfig downloads page.
     

Share This Page