Jump to content
Sign in to follow this  
dandy_76

Adding mailhost failed

Recommended Posts

Hello everyone,

I have been using mailhost setup for like 2 weeks now, and after few tries I still cannot add another chained account to it.

I have no debugging information, I know this relay uses sendmail, and I dont have any control over it (relay1). Another one (relay3) os constantly down.

I think adding more debugging information in the following page wont hurt, and will better indicate at which step of SMTP conversation the error comes. Here's the report page from spamcop add procedure:

----------------------------------------------------------

Sorry, all tests failed.

We cannot deliver mail to the address you provided: <username omitted>[at]farlep.net. Double check the address provided or try again later. Your mailhost appears to be offline.

Detailed errors:

Connecting to relay3.farlep.net.:

smtpSend:smtpOpen: connect to smtp server failed (Connection refused)

Connecting to relay1.farlep.net.:

smtpSend:smtpOpen: smtpsend connection error from smtp server (550 No expected reply from SMTP)

Sometimes, mailservers are temporarilly unavailable. If you believe you have entered your email address and other details correctly, you might just wait a few minutes (or 24 hours) and try again.

-----------------------------------------------------------

Thanks in advance.

Share this post


Link to post
Share on other sites
Connecting to relay3.farlep.net.:

smtpSend:smtpOpen: connect to smtp server failed (Connection refused)

Connecting to relay1.farlep.net.:

smtpSend:smtpOpen: smtpsend connection error from smtp server (550 No expected reply from SMTP)

38338[/snapback]

I just tried a manual connection and found that relay1 only offers replies after the QUIT command is issued, which I believe is against the RFC's (not an RFC expert).

IIUC, the server SHOULD be replying after each command. That is something for the admin of that server to deal with.

To fix your problem with mailhosts, you can try contacting deputies[at]spamcop.net, with mailhost in the subject and all this information included. They have told me they are swamped with mail (mostly virus generated) right now so it may take a whle, but keep trying every couple of days. They are the only ones who can touch the mailhost configs.

Share this post


Link to post
Share on other sites

According to the following quoted data, http://www.dnsreport.com/tools/dnsreport.c...main=farlep.net, and http://www.dnsstuff.com/tools/mail.ch?doma...45%40farlep.net, your domain has the following serious problems:

  1. Nameserver ns.farlepusa.com [216.54.212.22] is not responding on multiple ports, including DNS port 43.
  2. It has a missing (stealth) nameserver named ns.kiev.farlep.net.
  3. Two of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are ns.farlepusa.com and ns2.farlep.net.
  4. Your DNS servers leak stealth information in non-NS requests, specifically ns.kiev.farlep.net.
  5. relay1.farlep.net (sun.farlep.net [213.130.0.20]) accepts and then bounces email (evidence and parse). Also, when presented with "MAIL FROM:<myaddress[at]example.com>", it times out and then says "451 4.7.1 Please try again later". That is very antisocial behavior, in violation of Internet Standards and RFCs.
  6. DNSreport.com and DNSstuff.com could not complete a connection to your mailserver relay3.farlep.net (popa.farlep.net [213.130.1.239]): "Timed out [Last data sent: [Did not connect]]" and "Could not connect: Could not connect to mail server (connection refused by remote mailserver). NOTE: Per the RFCs, mailservers are allowed to continuously retry this server until it is back online, and not try other MX records (RFC2821 3.9).]". This may be because Sendmail is not working on that mailserver at present (relay1 runs Sendmail). That mailserver is responding to ping, traceroute, POP3 (TCP/110), and IMAP4 (TCP/143), but not to SMTP (25) or HTTP (80).

Report History follows:

Submitted: Monday 2005/12/19 17:04:10 -0500:

Returned mail: see transcript for details

1592146371 ( 213.130.0.20 ) To: spamcop[at]imaphost.com

1592146366 ( 213.130.0.20 ) To: abuse[at]farlep.net

1592146357 ( 213.130.0.20 ) To: abuse[at]sms.co.uk

1592146346 ( 213.130.0.20 ) To: postmaster[at]farlep.net

--------------------------------------------------------------------------------

Submitted: Thursday 2005/11/03 00:50:32 -0500:

Returned mail: see transcript for details

1546312252 ( 213.130.0.20 ) To: abuse[at]sms.co.uk

1546312250 ( 213.130.0.20 ) To: postmaster[at]farlep.net

1546312249 ( 213.130.0.20 ) To: abuse[at]farlep.net

--------------------------------------------------------------------------------

Submitted: Tuesday 2005/11/01 15:54:45 -0500:

Returned mail: see transcript for details

1545213116 ( 213.130.0.20 ) To: abuse[at]farlep.net

1545213115 ( 213.130.0.20 ) To: abuse[at]sms.co.uk

1545213114 ( 213.130.0.20 ) To: postmaster[at]farlep.net

--------------------------------------------------------------------------------

Submitted: Wednesday 2005/10/26 16:25:27 -0400:

Returned mail: see transcript for details

1540370853 ( 213.130.0.20 ) To: spamcop[at]imaphost.com

1540370851 ( 213.130.0.20 ) To: abuse[at]farlep.net

1540370847 ( 213.130.0.20 ) To: abuse[at]sms.co.uk

1540370842 ( 213.130.0.20 ) To: postmaster[at]farlep.net

--------------------------------------------------------------------------------

Submitted: Tuesday 2005/10/18 03:29:21 -0400:

Returned mail: see transcript for details

1533128108 ( 213.130.0.20 ) To: spamcop[at]imaphost.com

1533128093 ( 213.130.0.20 ) To: [concealed user-defined recipient]

1533128086 ( 213.130.0.20 ) To: abuse[at]farlep.net

1533128083 ( 213.130.0.20 ) To: abuse[at]sms.co.uk

1533128082 ( 213.130.0.20 ) To: postmaster[at]farlep.net

--------------------------------------------------------------------------------

Submitted: Tuesday 2005/10/18 03:29:18 -0400:

Returned mail: see transcript for details

1533128013 ( 213.130.0.20 ) To: spamcop[at]imaphost.com

1533128009 ( 213.130.0.20 ) To: [concealed user-defined recipient]

1533128008 ( 213.130.0.20 ) To: abuse[at]farlep.net

1533128001 ( 213.130.0.20 ) To: abuse[at]sms.co.uk

1533127999 ( 213.130.0.20 ) To: postmaster[at]farlep.net

--------------------------------------------------------------------------------

Submitted: Tuesday 2005/10/18 03:29:17 -0400:

Returned mail: see transcript for details

1533127933 ( 213.130.0.20 ) To: spamcop[at]imaphost.com

1533127922 ( 213.130.0.20 ) To: [concealed user-defined recipient]

1533127918 ( 213.130.0.20 ) To: abuse[at]farlep.net

1533127914 ( 213.130.0.20 ) To: abuse[at]sms.co.uk

1533127912 ( 213.130.0.20 ) To: postmaster[at]farlep.net

--------------------------------------------------------------------------------

Submitted: Tuesday 2005/10/18 03:29:15 -0400:

Returned mail: see transcript for details

1533127797 ( 213.130.0.20 ) To: spamcop[at]imaphost.com

1533127792 ( 213.130.0.20 ) To: [concealed user-defined recipient]

1533127786 ( 213.130.0.20 ) To: abuse[at]farlep.net

1533127773 ( 213.130.0.20 ) To: abuse[at]sms.co.uk

1533127764 ( 213.130.0.20 ) To: postmaster[at]farlep.net

--------------------------------------------------------------------------------

Submitted: Tuesday 2005/10/11 12:45:17 -0400:

Unzustellbar:TV

1527563179 ( 213.130.0.20 ) To: spamcop[at]imaphost.com

1527563162 ( 213.130.0.20 ) To: abuse[at]farlep.net

1527563148 ( 213.130.0.20 ) To: abuse[at]sms.co.uk

1527563135 ( 213.130.0.20 ) To: postmaster[at]farlep.net

--------------------------------------------------------------------------------

Submitted: Thursday 2005/10/06 03:52:38 -0400:

Returned mail: see transcript for details

1522825667 ( 213.130.0.20 ) To: abuse[at]sms.co.uk

1522825665 ( 213.130.0.20 ) To: postmaster[at]farlep.net

1522825664 ( 213.130.0.20 ) To: abuse[at]farlep.net

--------------------------------------------------------------------------------

Submitted: Thursday 2005/10/06 00:45:29 -0400:

Returned mail: see transcript for details

1522715042 ( 213.130.0.20 ) To: abuse[at]farlep.net

1522715022 ( 213.130.0.20 ) To: abuse[at]sms.co.uk

1522715017 ( 213.130.0.20 ) To: postmaster[at]farlep.net

--------------------------------------------------------------------------------

Submitted: Thursday 2005/10/06 00:45:16 -0400:

Returned mail: see transcript for details

1522714683 ( 213.130.0.20 ) To: abuse[at]farlep.net

1522714678 ( 213.130.0.20 ) To: postmaster[at]farlep.net

1522714677 ( 213.130.0.20 ) To: abuse[at]sms.co.uk

--------------------------------------------------------------------------------

Submitted: Thursday 2005/10/06 00:45:06 -0400:

Returned mail: see transcript for details

1522714754 ( 213.130.0.20 ) To: abuse[at]farlep.net

1522714751 ( 213.130.0.20 ) To: postmaster[at]farlep.net

1522714749 ( 213.130.0.20 ) To: abuse[at]sms.co.uk

Please make sure that all of those problems (especially 5 and 6) are repaired before you try to configure Mailhosts for (or use SpamCop to Report spam received at) any farlep.net email address. While you wait for the repairs, if you need to use SpamCop to Report spam received at a farlep.net address, please use an account that does not have Mailhosts configured.

Thanks!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×