1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

SMTP Headers revealing domain names?

Discussion in 'Plesk for Linux - 8.x and Older' started by chroniton, Apr 19, 2005.

  1. chroniton

    chroniton Guest

    0
     
    All mail received on the Plesk server has an SMTP header which looks like the following:

    Received: from other.smtp.server.com (11.22.33.44)
    by my.domain.com with SMTP; 20 Apr 2005 02:06:34 -0000

    Where "my.domain.com" is a random domain name hosted on my Plesk server.

    For example, if somebody sends email to "user@thedomain.com" the header should say "Received... by mail.thedomain.com" but it does not.

    Each mail receieved will contain the name of a different random domain hosted by my server, revealing this private information to other users.

    Can anybody else confirm this issue?
     
  2. jprince

    jprince Guest

    0
     
    Hello,
    To correct this, you need to assign only
    1 host in your reverse zone. This host should contain a
    record for each ip address. Do not duplicate this accross
    all domains. Take a look at your default DNS in plesk.
    You will probably find an entry that adds the host record to the
    in-addr.arpa zone for that specific IP. Since this is in the
    default, all domains receive it.

    You will need to correct this for each domains dns.

    Cheers.
     
  3. chroniton

    chroniton Guest

    0
     
    You're right

    You're right, I just figured this out and cleaned up my reverse zone.

    But... since the default configuration of Plesk triggers this issue, I would still classify this as a bug. Once the server has been setup, and the first reverse entry added to that zone, plesk shouldn't add any more.
     
  4. jprince

    jprince Guest

    0
     
    Hello,
    Actually, is probably more of an education issue than
    a bug. If you are using IP based. the entry is
    legitimate.
    AFAIK, the most recent full installation, not upgrade
    does not have the in-addr.arpa defined in the default
    zone template. You have to manually add it to the
    zones/domains as needed.

    Glad its working for you.

    Cheers.
     
Loading...