Jump to content

Community

Black Tiger

+Clients
  • Content Count

    429
  • Joined

  • Last visited

  • Days Won

    1

Black Tiger last won the day on February 17

Black Tiger had the most liked content!

1 Follower

About Black Tiger

  • Rank
    Member

Contact Methods

Profile Information

  • Gender
    Male
  • Location
    State Penitentiary

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yep, I also discovered this meanwhile. Pity. 🙂
  2. I don't know any on this moment, there wil be some.... but not many. When looking around in my surroundings, people rather not want to give their phone number, especially not to forums and things which don't need them. And how would they do the verification? By SMS provider (extra costs) or how? I would not even come near a forum wanting my phone number. LoL, filling in phone number or email address does not really make any difference in time. And some don't have smarthphones or even phones all together. Email is needed these days for communication. The poor few without email address can easily enough create one with gmail or hotmail or any other free one. As said, want to make things faster? Setup social login, however, they have to got an email address for that too. 😉
  3. Agreed, but there are already suggestions about improving the contact form, including one (from me) to add the ip of the user of the contact form. Also to make the amount of quetions to ask in the question and answer challenge customizable. They all can have some improvement because when not payed for the license anymore (f.e. version 5 comes out and you want to say at 4 and don't pay license anymore), the build in anti-spam will not work anymore. So the variety of protection possibility's or at least customization of these in IPS is a bit poor imho.
  4. I also had more spammers then normal via the contact us form. I think it would be an addition to add the ip addres from the one sending something via the contact form. At this moment I can do nothing except delete the mail and it's getting a bit annoying.
  5. That's why I wrote it relies on both. I did not want to write the complete technical story, it has little use when there is not even a correct SPF setup and DKIM maybe not possible when the mailserver does not support it. But your description of it is correct.
  6. Hold on, I'll check it. Maybe it's a cache issue on your side. The SPF check on MXtoolbox gives me all green. I see you still incuded secureserver.net, but oke no big deal, just take care you don't add to much. Also the mailserver check gives me all green: These 3 I've seen before too. They are not related to my SPF line.
  7. Nobody expects you to. But SPF are just a few lines. The spf wizard is something around for years and nows better then any support forum or desk and is easy to use. One just has to know what to fill in. It's also easy to find that DKIM does sign your messeage, hence the mailserver has to cooperate to do this for you. And when looking around what Dmarc is, it's fastly found that Dmarc relies on spf and dkim, so won't work standalone. 😉 But it's no problem, I'm glad to be a bit of help and explain about this, but don't get too confused about things (which can happen easily with this mailstuff). Patience and checking is a good thing.
  8. Please compare. It's a difference what Godaddy is saying themselves, which I linked to, and what the community is saying, which you linked to.
  9. You can use strings a bold way or a decent way. I prefer to to use the decent way. And that's not what godaddy are saying? Then check this: https://nl.godaddy.com/help/add-an-spf-record-19218 from Godaddy themselves and the example: So Godaddy -is- saying the same. 🙂 But it's no problem. Anyway, since it's shared hosting Godaddy is causing a rDNS issue with your mail. Godaddy is certainly not my choice for forums in the first place anyway, neither is any other host not implementing SPF by default, but everyone must now that for themselves. The rDNS issue is a lot worse. Because you can't fix that. DKIM is a complete different ballgame and the mailserver has to support it and sign your emails otherwise it's totally no use to have DKIM records. I also wonder why Godaddy in the past has decided to remove the automatic SPF implementation. 1.) I hope you did remove the include:spf.protection.secureserver.net line as I suggested. 2.) It's quite logic that support is not answering here. This is not an Invision issue, it's a hosting issue. And it's also holiday time. So you have to have a combination of somebody present, and also knowing enough about SPF, DKIM and DMARC to be able to help.
  10. I just did some tests and it's not looking good: So I would leave out that spf.protection.secureserver.net as an include, because it's not a host. It's an SPF record. So you can't include this with an include. Leave it out. And you have an smtp banner mismatch, so MX and rDNS are incorrect. The helo says: p3plibsmtp03-09.prod.phx3.secureserver.net MX addres mailstore1.secureserver.net. is pointing to 3 different ip adresses. Only 1 ip is pointing back to p3plibsmtp03-09.prod.phx3.secureserver.net so only 1 rDNS is correct. The other 2 ip adresses 68.178.213.243 and 68.178.213.244 do not have correct rDNS. So if any mail is send via those servers (which is very well possible since they are all mailstore1 aliases) your mail can well end up in spamfolders. This is a Godaddy issue, they should fix it.
  11. Oke I will do this once, but it's in fact real easy. People should use the SPF wizard I pointed to. Oke that is understandable. In that case it's still in fact not correct as it should be. If you had used the SPF wizard as I suggested, you would have known. And the reason I know this, is because I'm working with it on a daily base as I told you. As you could have seen then, the MX and A was even recommended. Firstly, look at what is you MX address for the domain seekandsupply.co.uk which is your domain. We already get a bit of an odd naming result seekandsupply.co.uk. 3600 IN MX 0 mailstore1.secureserver.net. seekandsupply.co.uk. 3600 IN MX 10 smtp.secureserver.net. Normally the backup-mx used with 10 is not named smtp, because smtp is normally used by the smtp server, but oke it's not that big a deal. So, your normal MX adres is mailstore1.secureserver.net. In this case your SPF record starts with v=spf1 MX because the server mentioned as your MX is allowed to send on your behalve. Since smtp.secureserver.net is also mentioned as MX it's allowed to send mail. You need the "a" in there to allow the ip of the hosting server to send mail just to be sure, it's common practise. The you should be ready. The only problem is that sometimes strict mail systems also want to see the ip instead of only the a record in the SPF. So in your case either use: seekandsupply.co.uk. IN TXT "v=spf1 mx a ip4:160.153.133.221/32 ~all" or seekandsupply.co.uk. IN TXT "v=spf1 mx a ip4:160.153.133.221 ~all" both should be correct and you have cathed it all. This will generate a softfail if mail is not send via your hosting account of via or from this server. If things work oud well, change it to the -all setting. This already takes care of the inclusion of both MX records, so you don't have to include them. I don't know where you got the include:spf.protection.secureserver.net setting from, but if you want to use that, you can add it. It would be like this: seekandsupply.co.uk. IN TXT "v=spf1 mx a ip4:160.153.133.221/32 include:spf.protection.secureserver.net ~all" Or if you don't trust the /32 you use: seekandsupply.co.uk. IN TXT "v=spf1 mx a ip4:160.153.133.221 include:spf.protection.secureserver.net ~all" And you're done. No need to include "secureserver.net" or "smtp.secureserver.net" because the MX setting takes care of it. This is the correct way to use an SPF record. You really need rDNS to prevent getting your mail flagged as spam on several systems. It's not a service that checks your ip. rDNS stands for "revers DNS", that means that there needs to be a record, which points to your servers hostname, or rather the helo name of the mailserver. You don't need to worry about that if you're on a shared hosting server, the hoster should have that configured correctly. However, if you are on a VPS or your own dedicated server, you should configure this in the datacenter control panel for your dedi/vps. So I don't think you have to worry about this as you're on shared hosting if I understood you correctly.
  12. Correct, but I've got a lot of experience with that over the years. And I don't mind, everybody his choice. As said, you don't have to like it, it's a feature request and opinions can differ.
  13. That is your opinion. We never had issues with that if you keep the questions short and simple. 1 questions is too little and too easy to answer for spammers. Imho it should be configurable, so everybody could make a choice on how many questions to ask. In that case you have your 1 question, I have my 3 and others maybe 0 or 5. Random questions is still one of the best spam preventions. Anyway, you don't have to agree, it's a feature request, no discussion. 😉
  14. Again, DMARC is -only- set AFTER a correct SPF and DKIM record is set. If you don't have a DKIM record and your mails are not signed with DKIM then DMARC has totally no use. First things first otherwise things get messed up. @VladTheGreatI don't know how Godaddy set it up, but you might find some things via Google. I found this video on how to set up DKIM with Godaddy, I hope it will help you:
  15. Just bumping this topic to keep this option in mind, since it might be very useful. ;)
×
×
  • Create New...