Anyone here with a 1and1 account?

Associate
Joined
16 Oct 2003
Posts
1,520
I need a very small favour.
All I need is someone with a 1and1 account to give me an email address to send a test message to and confirm if you receive it.

I have 2 1and1 accounts, one with a custom MX pointing to our Exchange server and the other with default 1and1 settings. We are unable to send mail from the Exchange server to the other 1and1 account, but it works for everything else. I just want to make sure it's not every 1and1 account that is blocking us.
Cheers :)
 
Thanks Chris, I just sent one now. You should really have it by now, but if you don't have it within the next half-hour, there's a problem somewhere.
 
Charlie Bravo said:
Sorry mate, have only just checked my mail as I was working a double shift yesterday.
No msg recieved I'm afraid.

Thanks for your time. That's what I hoped wouldn't happen, with the other 1and1 account I first got a "Delivery Status Notification (Delay)" and then an "Undeliverable" message about 36 hours later. I have just got the delay notification for your message as well so it looks as if I can't send any mail to any 1and1 accounts.
I checked with one of their support guys last week and was with him for ~15 minutes, he didn't have a clue. Will try again now I have these delay and undeliverable notifications.

I don't suppose anyone here would have any suggestions to try and fix this?
 
theyre not blacklisting your smtp ip that you are sending from are they?

What is the domain you are sending from? - and location of the mailserver?

Alex
 
just_grass said:
theyre not blacklisting your smtp ip that you are sending from are they?

What is the domain you are sending from? - and location of the mailserver?

Alex

I have sent a rather lengthy email to their support so hopefully I can get something out of that. I guess it could be possible the IP address is on some form of blacklist.
The domain I am sending from is one that is hosted with 1and1.co.uk except I changed the MX records to point to our own Exchange server. This is all possible with 1and1's interface, there is nothing 'hacked' about it. The Exchange server is pointed to with a Dynamic DNS address.

Our Exchange server successfully sends and receives all other mail fine, but with other 1and1 domains the messages get ‘stuck’ in our message queue with the status of:
“The connection was dropped by the remote host.”
At the minute there is a delayed queue entitled "charliebravo.co.uk" because it is retrying the transmission of the email to Chris as above.
 
okay, i wonder if your mailserver isn't following some of the required rules or laws of mailserver-age. - try chucking your domain (which the exchange server handles the mail for) into www.dnsreport.com (the box on the left) and see if and what errors it chucks up - specifically in the MX part.

As it is on a dynamic IP, i suspect the connection the exchange server is hanging off, is an a/s_dsl connection?? - home or office? or am i assuming wrongly?

Alex

edit: also have 1and1.co.uk account - running alexmarsden.co.uk - try sending to alex [at] alexmarsden.co.uk.

at the moment i have all mail directed to my gmail and another account where i pick it up from both pop3 accounts. This is while i am at uni and cannot successfully run my own mail server. - So i strictly dont use their mailservers. - could prove something?!?!

Also do you have an SPF record? - could prevernt them accepting mail from your domain if they check it and yours is setup wrongly?
 
Last edited:
Sorry for the delay Alex, I didn't even get email notification of your reply.
Thanks for those suggestions, particularly the dnsreport.com link.
Firstly I'll clear up that it is on a static IP and that the connection has never been known to drop nor is the server offline apart from one or two reboots a month.
I sent an email to you 5 minutes ago but it's stuck in the message queue as well so I don't expect you'll be receiving it.

A few warnings come up in the DNSReport site -
"WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). If your mailserver sends out E-mail using this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam software. This is also a technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server.
[dyndns IP] claims to be [actual mail domain] but that host is at a different IP address."
(I removed the IP's there)

"WARNING: Your domain does not have an SPF record."
I went to openspf.org and ran through the wizard and it has given me a list of entries to put into a zone file. But there is nowhere in my 1and1 DNS settings to put these?

Also - Another Exchange server I work with is having the exact same problem, but the domain is held at 123-reg. So it's not a problem with domain names hosted with 1and1 like I originally expected. Again I don't see anywhere in the DNS settings there to put the given SPF DNS entries. *edit* I think it's easy enough to do with 123reg but I will need confirmation on what to enter and where.

From what brief reading I have been doing it seems very likely that it's due to the lack of an SPF record. Hopefully I can get that sorted easily enough?
 
Last edited:
Hi mate,

Should you need any others to help you with your 'testing' then feel free to email me on michael @ agdk.co.uk as I'm with 1and1
 
leave the SPF for the time being - that is mainly just security - and could make backwards progress integrating one at this time.

It seems that some configuration on either the servers you administer, or the DNS/RDNS settings of the domain config.

Let me think about it. - I will reply later...

But the problems listed here:
"WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). If your mailserver sends out E-mail using this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam software. This is also a technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server.
[dyndns IP] claims to be [actual mail domain] but that host is at a different IP address." (I removed the IP's there)

Is quite a major one. - It has to conform to these requirements for ALL mailservers to comunicate with it. Some/many will do anyway as it isn't required by all mailservers to accept and check the conformaty to the requirements.

I will detail more when i reply later. It would be helpful for you to send me some of your domain details - like domain, 'A' record of you mail server, software of mailserver being used etc...

Post here if you are ok with that, or contact me through trust or profile.

Alex




EDIT: FOLLOWING THE ANNOUNCEMENT OF A REPLY TO THIS THREAD - I HAVE JHUST RECIEVED THE TEST E-MAIL YOU SENT ME..

I WILL CHECK THE LOGS TO FIND OUT WHETHER THIS HAS REACHED ME VIA THE 1AND1 SERVERS, OR MY BACKUP MX SERVERS.
 
Same here

cannot offer any advice really, but i have bought rdomain, and hosted it through 1and1.

so if you want mail testing fire one over to

Cheers
 
Last edited:
okey, i recieved your e-mail through my backup servers. your server must have given up with 1and1's and used them instead.

You haven't changed your RDNS of your IP. This must be done through your ISP or whoever owns the IP address. Pipex *MAY* provide that function through a control panel of some sort. they may not permit it at all.

At the moment, you will have:

'A' Record DNS translating to your IP.

ANS

And IP, when looked up, translating to an RDNS (reverse DNS record) of equal value to your 'A' record.

at the moment your RDNS record (i can find this out from the test e-mail you send and from the logs of my backup mail servers) is logged as 00-00-00-00.dsl.pipex.net where the 00's specify your ip in reverse. this is a standard format RDNS record.

You must call pipex or change this in your isp config to the same as your 'A' record whether that is www.domain.co.uk or mail.domain.co.uk...

I set a 'www' as cname to domain.co.uk, and have 'mail' also cnamed to the domain.co.uk - the the domain.co.uk 'A' record specifying an IP address.

THIS PRESUMES YOU HAVE A WEBSERVER AND MAILSERVER AT THE SAME IP ADDRESS. - WHICH YOU APPEAR TO NOT HAVE.

It is not necessary to have the RDNS and DNS of equal value, but it makes the next step far simpler and a lot tidyier. When your mailserver answers or calls itself during a conversation with another server / client, it will provide a hostname. You will be able to configure this within the mailserver config, or possibly depending on the mailserver, if it is a poor one, may use the machine's name.

This is probably more likely the cause to your problems, as i said before the only rule to RDNS and A-records, is that you have an RDNS for the IP that the mailserver is operating on. thats it. - And you have completed this.

Your mailserver is answering as tsm.selfip.com not as (for example) mail.yourdomain.co.uk as it should be.

Is this a re-used mailserver? or is it a shared mailserver?

I'm very nearly certain this is your problem. This must be changed. The hostname must be the 'A' record that points to the mailserver's IP.

If the server is a shared server, this will change a lot of the above and is a vital piece of information. please let me know either way and i can adjust or re-iterate certain things to do.


Sorry for the long post, but i thought i may as well get as much out as possible. and *HOPE* its readable!
Alex

ps.
Another tip, you ought to really recieve e-mails of [email protected].
 
Last edited:
looking further into it, it seems to be a shared server.

it is returning the hostname domain.co.uk which points to the ip of the webserver, NOT the mailserver itself.

I think to cure this your mailserver must instead of affiliating to domain.co.uk, it must be assigned to the full 'A' record of the domain that is c-named to the 'A' record of the mailserver or... just to an 'A' record that has the mailservers IP.

I haven't explained this well. but this is the fix.

If you can't decypher it post what you dont get!!
Alex
 
Ok, a lot to take in there and I've re-read your posts 4 or 5 times now :o
The mail server is the server in our office, it's not shared as such. It hosts our email and no-one else's if that's what you mean.
We have a separate mail server and web server. Mail = office server, web = 1and1 server.

There is a lot of stuff you have listed to do, I'll start off by getting the DNS entries right.

Starting off, I have created a subdomain which is in the process of being registered - mail.domain.co.uk. I have set the 'A' record to be the IP of the mailserver. I have set the first MX record to be tsm.selfip.com (the dynamic dns address mapped to the mailserver IP) but I don't know if that is correct or if it even needs to be changed?
And after doing that, do I set the MX record for domain.co.uk to be mail.domain.co.uk?

There is nothing at the pipex end to configure RDNS. How crucial is this?

I will indeed configure abuse@ to be received, I didn't realise how important that was.

Lastly, thanks for your time thus far, you're putting a lot of time into this :)
 
I had thought it was shared due to it being registered under selfip.com and responding for yourdomain.co.uk, but i was unaware that selfip was a dyndns domain...

The RDNS is not crucial, as you do at least have one. thich is the vital part.

Yes, provided the server is on a definate static IP: The 'A' Record of mail.yourdomain.co.uk needs to have the IP of your mailserver. then in your MX records, use mail.yourdomain.co.uk rather than tsm.selfip.com.

I also think there is something on the mailserver to be changed. Will you let me know the software you are using for the server?

When you setup the mailserver, it will ask for/be an option to set a hostname for the server to call itself. - Now, this must be the 'a' record that points to the IP it is operating from.

At the moment, it is set to 'yourdomain.co.uk' which is the 'a' record for your webserver. - it must now be 'mail.yourdomain.co.uk'.

This is all i think you need to change.

Don't worry about my time. Its apart of what this forum's about, helping each other out with problems isn't it?

Alex.
 
Ok, been out & about all day so only got to reply to this now.
I have since set up:

mail.domain.co.uk
A: 8x.xxx.xxx.xxx (IP of office mail server)
MX: mail.domain.co.uk, 10
MX: mx02.schlund.de, 20 (are these MX records right?)

for domain.co.uk:
A: default 1&1 server
MX: mail.domain.co.uk, 10 (this used to be dyndns address)
MX: mx01.schlund.de, 20

We are running Exchange (2003). I know what you mean by the "hostname for the server to call itself" - I had previously set the web server name to be tsm.selfip.com, but I now changed this to mail.domain.co.uk. The actual domain name was already set to domain.co.uk and I left this alone.

Is this OK so far, and what do I do next? Still getting the warning in the dnsreport site that I mentioned earlier:
"mail.domain.co.uk claims to be domain.co.uk but that host is at a different IP address."
 
you do not need the MX's for mail.domain.co.uk - unless you have e-mails <anything>@mail.domain.co.uk rather than <anything>@domain.co.uk

so you can remove these...

From where i am sitting (behind my uni firewall) i can't test to see what your mailserver is actually communicating as (do this by connecting to its mail port using telnet....)

So this hinders it somewhat...

The "domain name" you have left as 'domain.co.uk' in exchange 2003, ... now, is this a box that is labelled "fully-quallified domain name"? as opposed to just "domain name". as in mail terms, these are different.

The fully qualified domain name, is asking for the actual 'A' Record that points to the mailserver. The "domain" is the domain that the server is recieving e-mails for. (A fully qualified domain name includes the subdomain part of the address, for example "www.google.com" as opposed to "google.com")

Get back to me on this one. - This could be the problem. - If it is fully qualified, set it to mail.domain.co.uk and try back with dnsreport.com.

Alex.
 
Last edited:
Where the wizard is at the "Create Web server certificate" part and says "Enter the full domain of your Web server."
I had entered mail.domain.co.uk
There is also an option to 'Use a Web server certificate from a trusted authority' in that same page but I haven't got such a certificate.

And later in the same wizard when it says "Enter your registered Internet email domain name" I typed domain.co.uk

That correct?
 
As i said before, i am limited as to what i can check with your mailserver, but what you can try, is where you ahve put in domain.co.uk, put in mail.domain.co.uk instead.

Check dnsreport.com. if that says it is ok, then double check you are recieving and sending e-mails.

If that doesn't check with dnsreport.com, i will continue to find where the option is that needs to be changed!!! - but it is something to do with this name of the host.

Alex

edit: in response to your question - it sounds right, definetly the first bit, so leave that, but the 2nd bit you could try changing as per above.
 
Back
Top Bottom