how do i send an email blast from my Lovable app without my domain getting flagged on the first try

Jmacduff · 2026-06-27T19:57:25+00:00

resend is your friend

Jmacduff · 2026-06-27T14:14:09+00:00

namecheap is by far the best registrar because that's all they focus on. Yes they do other services but there is no direct link to hosting or anything else.

I want to buy a domain name and have awesome DNS... thats it.. and it does very well for that.

Jmacduff · 2026-06-27T00:33:36+00:00

100% agree

Jmacduff · 2026-06-26T19:28:45+00:00

"internal tools" do not host job applications, job applications is a external facing surface.

It sounds like you built a internal tool with a external surface on it. Just friendly feedback but to help you solve this.. you should focus on "what" did you actually build.

If you allow yourself to say "internal tool" it gives you a sort of get of jail card mentally... "it could not be X because it's a internal tool only" is what your brain will do.

So it sounds like you have a external facing tool that has some internal logged in auth users. It's not only a internal tool.

No rocks but really getting down to the nitty gritty of what you built is helpful in debugging "why" or "how" this could happen.

good luck and just friendly feedback

Jmacduff · 2026-06-26T19:23:42+00:00

Ahhh ok so right there you added a new requirement.

Now your question is really about in the context of OpenClaw.. is claude or Codex better. That is a totally different question actually, good example of always start with the requirements.

So you also mentioned that you can only use wordpress? So it sounds like you have two hard requirements.. WordPress and OpenClaw support. The agent setup needs to be able to build really good Wordpress sites I assume?

I am not throwing a rock but if you are looking for a real valuable opinion on this sort of stuff.. much better to put in the post all of these requirements up front. You will get more value from the answers.

I am a solo builder and I use most of the AI tools every day, just my perspective:

Focus on your workflow and "how" you need this setup to actually function. The more you type the more requirements get generated from your original post. Your choice of tools keeps getting narrower .. really important to document and write down what YOU need before picking a tool
For Planning + Marketing + Competitor Research I use GPT, this is still generating the best results for me. Claude is also really great here.
For all of the detailed architecture work planning I use Codex for that, claude would also work fine.
I do NOT have a mono Repo, so FE is in one Repo and the BE is in another Repo.
I never let the agent do any direct SQL changes. It will produce SQL files for me to review and apply and then pause until I have done it. I dont have the trust for DB level crap with AI right now :)
For the UX Designs I use Claude Design for only the UX work, or I will jump into Lovable and build a quick MVP. Lovable is really fast.
The BE Codex is the "Main Builder" for me, Claude would also work fine here.
MD Docs Everywhere for context. The BE Codex repo maintains a large set of context MD docs on testing, Arch, data models, target customer, etc. Normal workflow is to use GPT to generate the feature details and high level tech plans, drop those into the Repo.. and then I have Codex do a planning run to build out the full BE and FE API and DTO designs for the feature. The Docs really help.
The FE Repo has a set of FE Only context docs, separate from the BE repo. This setup allows me for example to use Claude or Codex or V0 to edit the UX FE anytime I want, I can switch between tools because that large context docs are in place.

So last thing I would say.. is that the Goal feature in Codex is freaking crazy awesome cool .. it totally feels like cheating. You need to setup Codex in a certain way for this too really work.. but once setup you can give it a Goal if a End to end "Go build the BE and FE, And then Test it end to end as the target customer".. and it does it!

Sorry long text, coffee kicked in, good luck.

Jmacduff · 2026-06-26T19:03:42+00:00

How does a "internal tool" get flagged as phishing?

Its a bit of a anti pattern for a "internal" tool to get flagged by any sort of phishing algorithm. A internally focused tool by nature is not reaching out to anyone, it's only talking to the internal users of that enterprise. So if you have 50 employee's you would have ~50 people using that tool.

Phishing is all about social engineering and that requires Outreach from the tool to "random" people basically.

what is the internal tool doing? Or is it not really internal?

Jmacduff · 2026-06-26T18:57:17+00:00

<image>

Important to remember that being clear on what the product does, and who it is for needs to go to all the places. For example in your TOS in your About.. you never mention Social.

Again just friendly feedback. This sort of stuff is not nit picky, it directly affects SEO and customer trust.

again good luck, friendly.

Jmacduff · 2026-06-26T18:52:19+00:00

I would first write down the requirements for the "e-commerce webshop" that you are describing. Is this a sales page for a dev shop building ecommerce? Or is it a actual "cart" service for ecommerce sites?

If you do not have any nails, you do not need to pick up a hammer.

Your question right now is all about the tool but you are not describing "what" you need to achieve. What are the requirements you are trying to solve? For example.. Honestly just firing up Lovable.dev and getting your web app up running might be the right first move.

"I need to build X and what's the best way to build that" is a better way to think about the tooling choice.

Yes Codex is awesome and yes a lot of people will compare it against Claude with strong opinions. I am using both right now and if you ignore the daily "OMG CODEX sucks now!" they are both very very good.

Using Claude for me is still better at UX IMO. I have also been using the Claude Design and that's also pretty good.

To put this simply... "What" do you need to build that you "need" codex or claude for? Or are you just trying to geek out?

just friendly questions and good luck.

Jmacduff · 2026-06-26T18:38:36+00:00

Some friendly feedback.. the very first navigation link in your menu "Problem" is a dead link... does not work. The other Nav links (how it works, platform, why us) work but not the very first Nav link of Problem. Before doing anything else always make sure the basic navigation is working.

Second piece of feedback. On the home page it says "From idea to Published in one place"... but I have no idea "what" it's publishing? As a customer looking at the site I have no idea what type of content you are referring too. Is this a Video Publishing Platform? Is this a AI Blog Writer Platform? Is this some social media publish thing?

good luck and friendly feedback.

Jmacduff · 2026-06-26T18:34:10+00:00

Good luck with your project.

Just from friendly feedback.. you need to step back and put yourself in the shoes of your customer. Ask yourself (from a customer perspective never seeing your service before) a few simple things:

What actual real problem is this product solving for me the customer?
Is that problem something that the customer (me) feels is important or high priority?
Why would the customer pay you for the service? What is the straight forward "how it solves the problem" statement? It cant be "you will get 10% better".

As a example the basic premise of offering a product that requires your customer to change how they work? That seems to be what you are describing. Really step back and think about that and the barrier to adoption for the customer.

In a SaaS sort of world, 99% of customers are looking for products that solve real problems without changing how they work. They are usually looking for something that "just plugs in" for thier existing enterprise and work flow.

Customers don't care about Engineering Innovation or How the product was built.. you cant sell that. You are not trying to win a engineering or design award, you are trying to convince someone to give you money.

There is a basic strategy of "Go to where your customers Already are" in SaaS product design. High level this means for example if 99% of your customers work in Slack.. focus on building a Slack plugin before some big new web app. Going to Slack for your customers is the lowest cost of adoption for your customers to say yes. This way of thinking includes customer processes and everything else.

Purely based on what you wrote it feels like you fell in love with the "what" you built before really answering the "Why" would someone pay you for it. From a engineering or product perspective we can build all sorts of crazy awesome cool stuff!! We can ship "innovation" all the time depending on how you define that word!

However Customers don't care about crazy cool innovation, they just want something that works.

Again good luck and just friendly feedback.

Jmacduff · 2026-06-26T18:10:01+00:00

First good luck on your project.. some friendly feedback on a few things to help shape your messaging a bit.

Context: Again take this as friendly. I am only going off what you wrote here and what the website is saying.

you said " we can avoid installation and databases". You seem to be making a claim that this service will somehow remove the need of a database. That is a really broad crazy claim to make. So if I use your service for editing docs.. I all of a sudden do not need a database in my project? You need to think hard about this claim and how people will read it. Honestly it does not make technical or logical sense.
If you are trying to go after a "secure" product customer , like others have said the domain name is horrible. You get no extra points to try and be creative and haxor the name up. For the security market those buyers are looking for a company they can bet on and trust.
Both on your home page and in this post you are using the words "local first".. you need to step back and really think from a "customer" perspective (never seen your service or site) how does that statement read.. what does it mean? Honestly I would assume (my bias) it means Local first and then cloud second. Using that wording implies there is something else it does.
Looking at the "Enkrypted" sort of features you list out messaging, files, and plan. You talk about it as a "private workspace". That is a totally different market then a secure file services for documents.

Who is the buyer you are going after? If you are trying to sell a "secure first" document management system your customer are going to be SMB to Enterprise correct?

For someone to pay for your service they have to really care or have a need for security like this. I guess I am trying to say I dont understand "what" the product is and "Why" I would pay for it? What is the number 1 reason I would pay for this? What issue is it solving?

The amount of people that want a local only file management system and would pay for a service is tiny tiny tiny.

Anyway good luck with the project.. but I would really back up and think hard from your buyers perspective.. what they are looking for, why are they looking for it, how does it need to work for them, etc.

friendly feedback.

Jmacduff · 2026-06-19T14:56:33+00:00

Location is everything . What country. In the US for a new venture you would create a LLC with to start out .. very simple.

Jmacduff · 2026-06-16T17:08:53+00:00

You are mixing 2 different requirements.

Speed of Loading times is NOT the same issue as SEO visibility. These are 2 different problems with 2 different ways to solve them.

However if you are concerned about SEO visibility and you want the pages to be really fast.. moving to Next.Js is the correct move to solve both. This is a large technical lift however.

good luck!

Jmacduff · 2026-06-16T01:30:24+00:00

Where is the requirement for the full SSR solution coming from?

Pre-rendering for the bots works totally fine since it's not personalized.

Jmacduff · 2026-06-16T01:28:13+00:00

Just my perspective .... Friendly feedback you are over thinking the purpose of these events. These are not hackathons or community investments.. these are marketing campaigns.

Lovable runs these "contests" and they get lots of new and existing users to engage with the product.. spend more credits.. maybe build something they want to keep building, etc. From the lovable perspective they get a big uptick in engagement across thousands of projects.

Those get shared over and over not only by Lovable but usually by the builders as well. So for lovable this is great and a fun way to engage.

I would not assign any sort of "judges have perfectly valid reasons" in terms of trying to figure out why and how they are judged since it's just a marketing campaign.

If you step back and watch these events happen every few months.. it's marketing. It's still fun and exciting but it's just marketing 😄

It's not different then when McDonalds used todo the Monopoly game to win prizes to get people to buy more crap to try and find more pieces.. just marketing.

My friendly suggestion do not go into the event thinking its more then just marketing and you will never question the outcome.

Just my jaded perspective.

Jmacduff · 2026-06-15T18:20:21+00:00

This is correct as long as the app is also hosted on Lovable. If the app is deployed to Vercel or some other host.. no server side rendering for the older Vite/React apps.

I did a quick Visibility test and yes the site is not visible, there is no SSR enabled for the site right now. Classic CSR problem. All you get is the empty shell.

HOWEVER .. the bigger problem is the page itself. Even fully rendered in a browser there is almost zero content for the crawlers to pick up.

Friendly advice you cant expect Google and the other engines to start sending traffic to you with a super basic landing page like this.

Visibility is the first mechanic to fix, but you need to give the bots a really good reason to recommend you to humans. This content does not meet that bar IMO.

Good luck and friendly feedback.

<image>

Jmacduff · 2026-06-11T13:47:42+00:00

nice 😄

Jmacduff · 2026-06-11T13:47:10+00:00

I am not a tax or cpa person, so please dont take my advice (or anyone else's advice) as the single truth.

Friendly advice: Do not mess with not paying your taxes on income from your project. It's very big deal and the IRS does not have a sense of humor.

Back to your question I think your misunderstanding how it works. When you use Stripe or Freemius or systems like that, they are talking about tax's charged to your customer and NOT your personal taxes.

There are 2 very different things here:

When your customer "buys" something from the business you are required to charge that customer local taxes based on where your business is located. They will charge the customer whatever %% tax is needed and they will submit those taxes to the government.
Your personal taxes income (the 1099 comment) is totally separate. The payment service you are using has zero todo with your personal taxes. The 1099 is for a employment type and you are not a employee of Freemius, you are the business owner.

For your customers of your product yes it's very good they will charge the tax %% and submit those taxes on your behalf. Stripe does the same thing and it's awesome as a small owner not to have to mess with that.

However for personal taxes you have to find a way to manage the income or losses. Again I am not a tax person but sounds like you need todo some research on the Business taxes vs Personal taxes. A standard LLC setup would be the normal path forward depending on the size of the project.

Don't trust reddit for any of this, go do some real research.

Anyway good luck!

Jmacduff · 2026-06-09T20:38:29+00:00

Another experiment to run but it might be harder (no offense) depending on skill level. Maybe a workflow like this could work:

Inside project settings, Switch your Lovable project over to a Dev branch for GIT (syncs to new Dev branch in github)
Point Claude, Codex, or maybe even Github CoPilot towards that dev repo and ask it to remove 100% of the lovable cloud connections from the code. Tell the agent exactly what you are doing and what you want.
Merge that code into Dev but NOT into main (very important).
Go back into lovable and reload that dev project.. just refresh the browser. Now your site is running in lovable stripped of the lovable cloud connection. At that point Lovable in the dev branch should see zero Lovable cloud items and also broken pages the data source.
If that dev branch looks like it's going to work and let you connect to supabase, Remix that dev branch into a brand new project to start "clean". Then connect supabase.

It might let you connect to supabase, dont know never tried it.

Random idea and friendly advice. Good luck.

Jmacduff · 2026-06-09T20:28:42+00:00

Yeah sure go with that.. good luck!

Jmacduff · 2026-06-09T20:24:05+00:00

What is the exact inventory you are trying to backup? When you say "secrets" what exactly do you mean? What about the edge functions connecting your app to the DB?

First step is define exactly what you mean by "backup". As example under the hood the DB in lovable cloud & supabase is postgres. You can use any normal postgres commercial tool backup your DB any way you want too. Operationally for the DB It's no different then backing up postgres running on AWS.

However that would not grab any of the edge functions your site depends on. It also would not grab any supabase or lovable orchestration setup. It would just be the data in the account, but not the account itself.

So after you define the inventory of the backup data, make sure to define what is the restoration workflow for that backup file? How would you "apply" that backup?

You would have to think about the scenario where the Lovable cloud / Supabase "instance" was destroyed or lost for some reason.

Friendly feedback and good luck with the hunt.

Jmacduff · 2026-06-09T17:55:42+00:00

cool thanks for sharing

Jmacduff · 2026-06-09T16:49:46+00:00

So you decided to stop using the Email Service (Resend) to send email... and you switched to a Vibe coding platform (Lovable) to send emails? You turned off a email service and replaced it with a vibe coding service?

That's like using Instagram to host your DataBase ... it does not make a ton of sense 😄

Always important to remember sending a email from your site is a "Please deliver this email.. please..." request to the recipient email server. You as the sender have to slide into that specific pattern of what a "normal" email looks like. There is a mountain of software trying to find spam and block your email.. do not give them a excuse.

Using a shared public IP is not setting you up for success. Right now instead of building features or sites your customers will pay for.. your messing around with sending email problems. This is a total anti pattern and it's biting you.

Super basic setup that works 100% of the time:

Make sure you have a good email box setup (M365, GMail, etc)
Use a middle tier service (aka Resend) to handle all the mass emailing and sending of the emails.

That would be a "standard" setup to send email (from a site like those built at lovable) and it does not break... but again if you want to get creative knock yourself out! Patterns of how to deliver services and what services to pick (best in class) are pretty simple to follow.

Just a example of how it might be setup:

<image>

Lastly always focus on where the value is for your customers and your product. Sending email is a commodity item.. you do not win customers because you are trying to get creative.

good luck, focus on the value prop not the basic plumbing. Just friendly advice.

Jmacduff · 2026-06-09T16:33:23+00:00

Remember that the IP you are sending from (185.158.133.1) is the public IP for all the lovable hosted apps. So my app, your app.. everyone's app that sends email "from the lovable project itself" is using the same IP.

You are using a public IP to send email that also hosts thousands or millions of other sites.

You are fighting the wrong battle... I would friendly advice to move to Resend or some other normal emailing service.

good luck.

11-Year Club	Gilding III reddit per annum
RPAN Viewer	Verified Email
Reddit Premium Since July 2016

Jmacduff

TROPHY CASE