can't receive mail posted to main domain

Discussion in 'Installation/Configuration' started by ottojan, Apr 19, 2008.

  1. ottojan

    ottojan New Member

    Hi,

    I have a problem with receiving mail dat is posted to de domain the server is part of.

    I can receive mail sent to other domains that are hosted on the server.
    The server domain is domein-direct.nl (server1.domein-direct.nl)
    I have added a site for domein-direct.nl in ispconfig, with a user that has the emailaddress [email protected]
    I can sent mail from another hosted domain on the server to [email protected] (via roundcube)

    But mail sent from my local PC is not received.
    A check with DNS stuff looks okay.

    Can someone help me out?
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Which lines apper in the mail log file when you send a email to this domain?
     
  3. ottojan

    ottojan New Member

    I don't see anything appear in the log file.
    But if I do a check with DNS Stuff then I see mail for abuse and postmaster in the log file

    Apr 19 19:56:18 server1 postfix/smtpd[15298]: connect from purple.dnsstuff.com[74.53.59.137]
    Apr 19 19:56:19 server1 postfix/smtpd[15298]: 1D21CF88284: client=purple.dnsstuff.com[74.53.59.137]
    Apr 19 19:56:19 server1 postfix/smtpd[15298]: 1D21CF88284: reject: RCPT from purple.dnsstuff.com[74.53.59.137]: 554 5.7.1 <Not.abuse.see.www.DNSreport.com.from.IP.83.98.248.138@DNSreport.com>: Relay access denied; from=<> to=<Not.abuse.see.www.DNSreport.com.from.IP.83.98.248.138@DNSreport.com> proto=SMTP helo=<test.DNSreport.com>
    Apr 19 19:56:19 server1 postfix/smtpd[15298]: disconnect from purple.dnsstuff.com[74.53.59.137]
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    If no lines appear in the mail log, then the email is not delivered to your server. If you just changed your dns records, you should wait some time, up to 48 hours.
     
  5. ottojan

    ottojan New Member

    Well I didn't change the dns recently.
    But I fixed the problem.
    I recreated the site, and now it's working.

    Thanks for the help anyway.
     

Share This Page