Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About sjdean

  • Rank
  1. Thanks for that. D'oh. I think Im going blind. If I can give an example though of what Im seeing? My Mailhosts through Spamcop shows: anyoldname.com kitkit.net kitkitnet.plus.com plus.com cable.anyoldname.com mail2.kitkit.net zimbo.co.uk finches.plus.com mail.kitkit.net dokicity.com zen.co.uk iamexpert.com simtext.plus.com smtp.anyoldname.com Most of these (in fact Im sure all of them apart from one on each list) aren't associated with my mail server. None of them are used when people send mail to me. The Mail Headers for me show: Return-Path: <service[at]admin.spamcop.net> Received: from sc-app2.spamcop.net (sc-app2.spamcop.net []) by simtext.plus.com (8.12.11/8.12.11) with SMTP id kACHlC5e024538 for <sjdean[at]simtext.plus.com>; Sun, 12 Nov 2006 17:47:15 GMT X-SpamCop-Conf: Zi1p0RNTc0rYhnUd Received: from [] by spamcop.net with HTTP; Sun, 12 Nov 2006 17:47:10 GMT From: SpamCop robot <mhconf.Zi1p0RNTc0rYhnUd[at]cmds.spamcop.net> To: sjdean[at]simtext.plus.com Subject: [SpamCop] account configuration email As you can see, mail arrives directly at my server due to the Primary MX reference as below While my DNS: simtext.plus.com. MX IN 86400 mail.simtext.plus.com. [Preference = 1] simtext.plus.com. MX IN 86400 autoturn.plus.net.uk. [Preference = 5] simtext.plus.com. MX IN 86400 mx.last.plus.net. [Preference = 20] simtext.plus.com. A IN 86400 mail.simtext.plus.com. A IN 86400 I was trying to figure out the reason why these associations with mailhosts are made. I presumed that it was because of Backup MX servers being looked at too. But then I can't explain how other distinctly separate isp's can get in on the mix in the mailhost. Is it a bug? A feature? By design? So, in the FAQ: "If a mailhost record already exists for that domain (i.e. another user on that domain) your account is simply pointed at that already existing record. If any new servers are identified they are added to the existing record." From this, and my headers above, I have my own distinct server and mailhost. I should therefore have a new mailhost record produced? It's not. The only thing that makes any sense to me, is if I share the same BackupMX as another user, even though PrimaryMX is different, I would get added to the existing mailhost? Which is fair enough. But then you get the messy situation as I tried talking about where it seems users have moved to different ISP's and somehow associate those other servers with the existing mailhost. (zen, cable, plus, ntl etc) "If a new server is found subsequently, yes we have to manually add it. Similarly, if the domain changes hosts we have to add the new servers and remove the old ones." This is probably the crux of my argument that I was trying to make. It seems like this work hasn't been done and so you have several physically separate mailhosts and servers under different isp's etc under an ambiguous umbrella. Which as I say, looking through the old posts here, seems to cause a bit of confusion. Thanks Simon
  2. You did the what now? Could you point me in the direction of the FAQ? I've had a look in this section and havent found it yet. My musings were based on trying to understand how the Hosts/Domaints and Relaying IP's are made up since they didn't make any sense. After reading the sticky here titled "Mailhosts - definitions" which quote: "1: the general name of the mailhost as established in the spamcop files. This name is somewhat arbitrary and as the name for a given set of servers (ex. earthlink servers) is set by the first person to register them the name might not be what you expect. If the name is seriously strange it can be changed by writing to deputies <at> spamcop.net." and ""Hosts/Domains" is a bit confusing. What it actually is, is a list of the names of the various mail servers utilized by the "Mailhost name" Those names appear in a drop down list." So for clarification, I guess my questions are: 1) The Mailhost name is completely arbitrary right? And does not necessarily relate to any ISP? 2) The Relaying IP's/Hosts Domains - the way they're linked to Mailhost names mean that there will inevitably be non-related ip's within a single mailhost, right? ie in my Relaying IP's list I have: Plus.com Zen.co.uk ntl.com Three completely separate ISP's and servers all linked under an umbrella arbitrary Mailhost name (incidentally, none of these ip's appear in my headers: Return-Path: <service[at]admin.spamcop.net> Received: from sc-app2.spamcop.net (sc-app2.spamcop.net []) by simtext.plus.com (8.12.11/8.12.11) with SMTP id kACHlC5e024538 for <sjdean[at]simtext.plus.com>; Sun, 12 Nov 2006 17:47:15 GMT X-SpamCop-Conf: Zi1p0RNTc0rYhnUd Received: from [] by spamcop.net with HTTP; Sun, 12 Nov 2006 17:47:10 GMT From: SpamCop robot <mhconf.Zi1p0RNTc0rYhnUd[at]cmds.spamcop.net> ) 3) Are users linked on Backup MX records too? 4) What would you change the Mailhost name to in this scenario? 5) There are other servers listed in the Relay IP's section of my mailhosts file. none of them are involved in processing mail towards me, as I have a Primary MX record on my domain pointing at me. Is this a problem? http://www.dnsstuff.com/tools/lookup.ch?na...om&type=ALL That was never my argument. They're a valid "domain" in their own right and can have associated MX, NS, A records etc. I can see that it does that. And very nicely done too. However I do see a few people on here who have had questions about having non related IP addresses appearing in their "Mailhosts". Me too. As I say, with me on my own static IP address and own domain name, and my own primary MX, I was surprised to be lumped with other Relaying IP's and Hosts/Domains that had no bearing or relation to my own setup. There's probably a very intelligent reason behind why it records what it does, but, it doesn't make a great deal of sense, and being told Im on KitKit.net rather than Plus.net doesn't make any sense, when KitKit.net aren't even hosted at Plus.net anymore. And what do you change the mailname to anyhow? Zen? NTL? Plus? Would probably make more sense not to display any of the Hosts/Domains or Relaying IP information to the users as, it doesn't make any sense. Im not trying to be derogatory, far from it. I think Spamcop is great. From a user point of view, and I've seen it mentioned, it seems that there's some quirks and the information presented to users is confusing. Im a Linux geek, running Sendmail and understand DNS (like Im sure a lot of other people here). I'd be most honoured to go through this with someone to explain my thoughts and what I see, I understand you're still addressing issues, so I mean, if there's anything I can do to help really? Thanks Simon
  3. a and b would be users with their ownsubdomains. So for example, my email address is youknowwho[at]simtext.plus.com. If you look at my DNS settings, simtext.plus.com is marked as a MX with the highest priority while simtext.plus.com also has an A record pointing to my ADSL connection (which just so happens there's a Linux mail server sitting on it). In case my adsl connection goes down, my isp (plus.com) provide a backup MX which should then shunt my mail onto my server. edit: shunt it to my box when my adsl line is back up Other users have their own subdomains as required, thus in my example a and b are both users on isp.com effectively with their own domains. I grant you, that backupisp and yourdomain are not domains in the strictest since, they are hostnames, they're still valid subdomains capable of having their own A, NS and MX records etc, so to all intents and purposes, they are domains. It's not my mailhost file. It's spamcops mailhost file. And it's not so much the extraneous data that bothers me (though it could be construed bad data design), it's the redundant data. Data that shouldn't be there because it's not correct anymore. I apologise. I was obviously not very clear. In my example above, while the IP addresses are dished out by the ISP to its users, its users do still have domain names as eg: a.isp.com b.isp.com so users could enjoy email addresses of anything[at]a.isp.com for example. Further to this the "domain" would enjoy the following DNS records: a.isp.com A xx.xx.xx.xx (IP) a.isp.com MX 5 a.isp.com. a.isp.com MX 10 backup.isp.com edit: this means that all email goes directly to my box from wherever on the world, unless my adsl line is down So then when a.isp.com (xx.xx.xx.xx) isn't available, the next MX record is used (backup.isp.com) to queue up mail for it's users, which then shunts it off to the next MX (a.isp.com) when it becomes available. It's really basic DNS stuff this... While the service does exactly what it does, I reckon there's a huge problem with the data. And it surely cannot work to contact the deputies to change the mailhost name. As I say... IP addresses from various ISP's have now been linked to each other through an arbitrary name called "Mailhost name". It would seem, for example, Two users from isp.com join the "Mailhost name", but then one person leaves and joins another ISP then uses the same Mailhost name. The IP's then seemingly get linked. If I can get the administrators to find out what has happened in my instance, it would be appreciated. As I do have my own mail server and my own static IP address, and as I specified a different Mailhost name to the one I joined, I suspect the system has joined me to a different Mailhost name based on the backup MX record. I then have further examples to check from their about why other isp's ip addresses and domain names are listed under the Mailhost name I've joined... Cheers Simon
  4. Let me see if I understand this wonderful system. A mailhost is defined as a server, right? A server with a realworld IP address? The second person who registers the same mailhost, has to put up with using the same mailhost name as the first person, no matter how wrong it is. Then because this mailhost name is overwritten, the second persons server ip's gets shunted into the Hosts/Domains list for others to look at? Take for example a situation of an isp, providing domains, smtp email delivery with backup mx's, ie: 5 MX <yourdomain>.isp.com 10 MX backupisp.isp.com then say there are two users: a.isp.com b.isp.com User A registers first, and gets the Mailhost name set to: SomethingNotRelatedToTheISP User B comes along, tries to register using the correct ISP name, but has it overwritten by SomethingNotRelatedToTheISP purely based on the fact that these two domains share the same backup.isp.com mailhost? But then even worse IMHO, User B then gets to see User A's IP/Domain Name. Only by this point, the Hosts/Domains are actually irrelevent, because User A has jumped ship to another ISP and those subdomains and IP addresses now don't exist, they're now redundant in the list, and the user has re-registered his NEW mailhost linking his old mailhost IP addresses with his new mailhost IP addresses for User B to see in his list????? Whoever designed this should be shot! Redundant Data that isn't/can't be removed Linked data to arbitrary names No facility to edit MailHost names In all seriousness though, how does it link MailHosts Names to Mailhost IP's? Does it actually look at all MX's for a domain and join it to the first registered? Based on the fact my primary IP MX ( should be unique, I can't understand how Im linked with several other peoples MailHost names - unless the system links on Backup MX records too? Cheers Simon