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

sendmail rejected 550_5.1.8

Discussion in 'Plesk for Linux - 8.x and Older' started by Effektor, Jul 12, 2006.

  1. Effektor

    Effektor Guest

    0
     
    Hey folks,

    the following problem keeped me up last nights.

    If we send a mail by using php mail() to several freemail hosts like web.de gmx.de any of our messages got rejected with following message in the logs:

    qmail: 1152716523.739746 delivery 789: failure: Connected_to_213.165.64.100_but_sender_was_rejected./Remote_host_said:_550_5.1.8_{mx054}_Cannot_resolve_your_domain/

    usualy there are Reverse-entrys for each of the 126 IPs

    so why does the gmx Server reject the Mails?

    Any ideas?
     
  2. DCNet_James

    DCNet_James Guest

    0
     
    It might be trying to resolve forward and reverse.

    For example:
    64.27.136.5 resolves to stan.digitalchicago.net and forward stan.digitalchicago.net resolves to 64.27.136.5.

    Maybe check your reverse mapping against public dns root servers, use the tool at www.dnsstuff.com to check it out, or do an nslookup using an external dns server from your workstation.

    Either way, many smtp servers simply will not accept mail if they can't at least resolve your ptr record.

    Another thing, maybe the host info passed in the HELO command isn't resolvable so the remote SMTP server kills the smtp conversation. Check your qmail control file called "me" thats what your smtp server passes to the remote. Make sure thats a resolvable host.

    One last thing, maybe the domain you're sending from is a BS domain thats not publicly resolvable and when passing the "mail from:" parameter the sender info isn't accepted, so the remote hangs up. Make sure the sender of the email is a real account, especially if the remote decides to do a call back check.

    Thx
    James
     
  3. Effektor

    Effektor Guest

    0
     
    Prob is fixed, the reverse record was wrong so the different ISPs could not resolve the correct Reverse Entrys and they rejected the mails.

    There is still one more Problem, now the IPSs accept the mails but they mails get marked as spam:

    I found this in the Header

    X-Priority: 3
    X-MSMail-Priority: Normal
    X-Mailer: Microsoft Outlook Express 6.00.2900.2149
    X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2149
    X-GMX-Antivirus: -1 (not scanned, may not use virus scanner)
    X-GMX-Antispam: 4 (From SPF protected domain over unauthorized server)
    X-GMX-UID: SBKCfMtoYW0+0UxOAmdpbDR0amthc1u0ob

    it seems that our SPF records for each domain aren't correct.

    The Prob is we got a Server:
    The Server is Housed by company X this company serves us with the primary DNS for our own domain.

    Each Domain of the clients are served by Company Y where we can change the Records for each domain.

    Our Server is just hosting each vhost for the clients.

    How do we have to config each SPF Record?
     
Loading...