megaphone
Update your Profile with your Support type to get your Support Type badge.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Stay in the know of how NetSuite can help grow your business with our guides, webinars, and events. Subscribe Here
What Topic Should We Cover Next? Your idea could be our next feature—drop your suggestion now!
No Limits. Just possibilities. Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Discover what's next at SuiteConnect Tour 2026.
Try Intelligent Payment Automation – Fee Free For Your First Month For more information, visit this thread.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
Don't miss out on our Question of the Week! You only have until tomorrow, April 2, 2026, 2:00PM ET to comment your answers.

My Stuff

New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.

3944581 Newbie

Comments

  • Hi Kurt, Could you supply the DKIM-Signature header from one of the signed test messages you've generated? It should look something like this : DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=netsuite.com; h=mime-version:content-type:subject:date:message-id:from:to; q=dns/txt; s=selector1; bh=jBTu7Vv/hc4SeCkESgLygdxzZLE=;…
  • I received your message fine and reproduced the same validation error that you got from the sendmail.net reflector. I'll follow up with Development and see if we can figure out what's up here. I appreciate your help getting to the bottom of this. Hopefully we'll be able to work it out quickly.
  • On its face, that all looks fine -- which says to me there's either a small inconsistency in the config that's masked by the redacting you did or that there's a legitimate bug in computing the message hash or something destructive being done by the outbound relay. Either way, it would be helpful if you could send me a test…
  • Some recipients implement broken address validation that causes issues with the way that NetSuite encodes bounce-handling envelope sender addresses (prior to version 2008.2). If you send these mail servers a message with a sender whose address contains an ampersand character (ie. bob&mary@example.com), they will reject…
  • It's not a typo -- the reason you add the . to the end of the domain is because godaddy’s DNS wizard doesn’t let you leave it blank (which is the other valid way of designating a record for the root domain in your zone). Without adding that trailing ‘.’ Character, that CNAME record in the documentation would be for…
  • Tom - unfortunately, while the change you made works today, it will cease to be supported (and stop working) in future when the old shopping.netsuite.com IP address (63.208.29.41) is finally retired. The NetSuite directions as you've posted them are correct, but there are a number of different methods of arriving at a…
  • I'm a Senior Systems Engineer at NetSuite and worked with our documentation team on that particular howto. Evan, our CTO, asked me directly to respond to your post, so I'm probably the right choice to believe if you had to pick. :) With regards to the core problem -- I'll send you a private message and make sure to…
  • Hey guys -- I'd like to apologize for being a while in responding to this thread, but in the meantime we've been looking at this issue seriously and come up with a change in our recommendations on configuring webstores with DNS hosted at GoDaddy. Tom and Debbie both found and correctly identified an issue where following…
  • I was able to find both messages you referenced in the case delivered successfully to the appropriate recipient mail relays. It doesn't seem like this is a problem with NS code or infrastructure. Maybe the messages ended up in a Junk Mail folder by mistake? Here's what the recipient mail servers said : (names/addresses…
  • If you can file a case with support and provide recipients and approximate sent times for the undelivered messages, we can try and track down exactly what happened to them. Once you have a case number, please post it here and I'll pick it up.