Email Account Settings

It amazes me how few people know about + addressing for emails and how useful they are. 🙈 What is + addressing? 🤔 Basically, you can add a + after the username part of your email address and then write any unique word you want afterwards and this will still be a valid email address you can receive on. 🤯 For example if your email address is joe.bloggs@company.com, you can also use joe.bloggs+LinkedIn@company.com as an email address. If anyone were to send an email to this address you would still receive it and you'll see the full email in the To: field. Why is this useful? 💡 1️⃣ If you're going to an Expo where you have to put in your email address so that everyone can scan your badge and spam you for months on end afterwards, you could use joe.bloggs+ExpoName@company.com. This way you'll still receive your registration information and you can keep the email working for a couple of weeks after the event so you get emails from people you want to hear from, then set up a rule to junk all future emails to that address. 2️⃣ Let's say you need to sign up for something that requires a unique email address but you've already used your work one. Create another just by adding a +word. 3️⃣ Additional security method. I've spoken a lot over the years about having unique passwords for every website you sign up to. This is because if a hacker steals your email address and password and you use the same password for multiple applications, you're at a big risk of being breached on other accounts. So if you also have unique usernames: joe.bloggs+Amazon joe.bloggs+PayPal etc Then it makes it even harder for hackers to break into your accounts. Plus, if an account email address is compromised and leaked, you'll know exactly where it was leaked from. This is also useful to work out whether companies are selling your data. Are you already using + addressing in your life and do you have other examples of how you're using them? Did you even know this was a thing? Let me know in the comments 👇🏻 #ithintsandtips #email #security #spam

Gmail users, here's a handy trick to track how your email address is being used. If you provide your Gmail work address in organization and vendor forms, simply insert a "+" and a unique identifier (e.g., a vendor's name) before the "@" symbol. For example: first.last+vendorname@yourcompany.com Gmail will ignore the identifier, but it will let you track how a recipient uses and distributes your email address. For example, if you add "+calbar" when you sign up for a California Bar event, when you later see emails from other groups sent to that address, you'll know where they got it. You can also use Gmail filters to archive, label, or star any emails addressed to first.last+vendorname to help triage a crowded inbox. This feature has been around for years, but I find that many people don't know about it. Now you're in the know.

If your cold emails are starting to randomly land in spam you are not the only one. Here is what we found out so far: - Without spintax (randomizing your content), I am talking about 5+ variations with multiple words randomized, we have seen accounts burn in a matter of days. - Google in particular is starting to catch the structure of emails so in your different variations you should be using longer variations, and shorter variations, having lots of space, and some with no spacing. - Open rate, clickthrough rate tracking, and adding links has been long dead. Don’t do it. You shouldn’t be adding more than one image in the whole sequence and even that can cause your email to go into spam. - Daily manual and automatic checks of the inboxes are almost mandatory at this point. A good warmup tool to help with that is Warmy.io - Email channel. Reliable. - Your sending tool IP can also be banned. We started using dedicated IPs on SmartReach.io since we saw Google was banning shared IPs more (note this is different from your email IPs) - Spam words need to be at zero - check mailmeteor’s tool here, basically any spam keyword like finance, guaranteed, %, funds, etc. can flag your message and send you into spam, especially for newer accounts. - The older the accounts the higher authority it has - it’s clear that newer accounts (even those prewarmed up for 2-3 weeks) get more passes and can get away with some spam words, less spintax, and even having more images and links at times. - You should be rotating inboxes - we do it every time they burn which can happen in a week, a month, or more.  - Certain client accounts always burn faster which I think is a mix of the audience, content, and lower reply rates - eg. financial related content or anyone targ IT related titles since they - A mini cheat code to get your reply and lead rate up - we reengage the not-interested responses across different clients (of course only ones that match the ICP). These prospects tend to respond more to cold emails, so they can help with improving deliverability and often have a higher lead rate. Honestly, the way I see us moving forward is: - Automating email account creation - you can build this with make - Automatic inbox rotation based on checks if accounts are burnt or not - I know QuickMail has a version of this - Diversifying on more email servers - we use Google and Outlook right now, but are looking to add 1-2 more. AMA

The biggest myth in cold email today? That high volume = high results. After a dense (and brutally honest) webinar with some of the best minds in deliverability, one message stood out clearly: Your sending domain is your most valuable asset. And most people are burning it to the ground without even realising. The new rule of cold email success in 2025 isn't about tools or copy. It's about long-term infrastructure thinking, the stuff that doesn't show up in your outreach dashboard but determines whether you inbox or land in spam. Here are 4 big shifts you should make if you care about results that last: 1. Diversify Everything Use multiple domain registrars, email providers (Google, Outlook, SMTP), sequencers, and even IP geos. Don’t let your whole system rely on one platform. 2. Send Less Per Domain Volume is the #1 reason domains get burned. Instead of pushing 150 emails from one domain, spread 50 emails each across three. Smaller volume = longer domain lifespan. 3. Aged Domains Are a Cheat Code Especially for Outlook deliverability. Domains that are a few years old inbox far better than fresh ones. Yes, they cost more. But they save a lot more. 4. Measure at the Domain Level Your bounce and reply rates should be monitored domain by domain. Every month, cut the worst 20% (by reply rate) and replace them. This keeps your entire ecosystem healthy. Bonus: Subdomains, geo-TLDs, warmup strategy changes - there’s a lot more happening under the surface. But if you just internalise these 4, you’ll be ahead of 90% of senders. Big thanks to the panel for sharing real insights, not just theory: Christian Oland (RevGen Labs & RevReply) 🚀 Benjamin Reed ( RevyOps) Kidous Mahteme (Inframail) Dean Fiacco (ScaledMail) V. Frank Sondors 🥓 (Salesforge 🔥) ⚡Felipe Aranguiz (Instantly.ai) Ken Volk (Mailrun) Namit Jindal (Aerosend) Piotr Mikrut (Experiment5m) If you're building or scaling outbound in 2025, watch this space. The playbook is being rewritten.

Why to use an email alias service to protect your online identity? It has been around a year ago when I decided to drastically change how I manage my online accounts. I used to have a solid setup, or so I thought. I had a dedicated email address that I used for most of my online registrations. I used strong, unique passwords with MFA everywhere. I only used this email at well known sites, no dodgy stuff. This was working well until one day I started to receive spam emails which was rarely the case before. I also noticed large number of unsuccessful login attempts to my mailbox. It was very disturbing as I was using online identify protection service, I checked Have I been pawned and few other places, nothing came up. Eventually I figured out through a paid threat intel database that my email with a password that I used long time ago, got leaked from somewhere, but I never knew where. This was the point when I decided to start using an email alias service. How does this work: - You link the alias service to your mailbox or mailboxes. - Create unique email addresses to all your online accounts. - When the platforms send you an email, it goes to the dummy address which is automatically forwarded to your real mailbox. - In case you have to reply to the email, you will reply as your dummy email not the real one. The benefits? - You never have to reveal your real address. - You can stop the forwarding any time you wish. Essentially this puts you in charge what emails you want to receive and you won't be at the mercy of your service provider's email protection capabilities. - In case a leak happens you will know exactly what the source was, because you use unique emails. You don't have to panic and start changing your passwords everywhere. Yes it's a bit tedious to change the email for all of your online accounts but your online identity will be in a much better place afterwards. Using unique passwords with MFA is essential. Combining that with unique emails will take you to the next level. #cybersecurity #infosecurity #mfa #onlinesafety

Current insights on what works and doesn’t work for deliverability in 2024, going into 2025. Just a few weeks ago, Microsoft had a “cataclysm” of sorts which made deliverability from & to Outlook accounts absolutely awful. This has begun to clear up a bit as time passes, but we’ve gathered tons of valuable insights from this last deliverability crisis that’s given us clarity on the science behind deliverability. Here’s what we’re seeing is working, and what isn’t: 1. Develop infrastructure according to your target industry Each industry typically has their own go-to provider they use across the board. For example, when targeting enterprise, most of these companies use Microsoft, so sending from Outlook-based private infrastructure is more favorable in this case. Then for E-commerce, Gsuite is more favorable as most brands are using Google. Diversify your infrastructure accordingly. 2. Domain aging In the deliverability masterclass Dean Fiacco presented to The Outbound Code, one point he drove was the importance of aged domains and how there is a direct correlation between reputedly aged domains to consistent deliverability. This is because ESPs monitor new domains thoroughly since most spammers buy a new domain and start sending emails from them immediately. From what we’ve seen, 2 weeks of domain aging is the bare minimum we perform before sending to ensure accounts don’t just blow up day 1. 3. Warm-up Warm-up at the moment has a lot of gray area around it as there are senders that are generating great reply rates with little to no warm-up, while others say a month+ is necessary for good deliverability. Both cases are valid, but really it depends on the ESP you're using. For Gsuite, 2 weeks warm-up & domain aging is crucial, or else they’ll hurt your reputation fast. For Microsoft, really only need a few days warm-up, as they value IP reputation more than anything. My recommendation is to still just perform 2 weeks warm-up, then have some extra accounts on the backend warming for a few months in case you need to replace active ones. 4. Bad copy = spam If ESPs are detecting your cold email copy as a “spam cold email”, your emails are likely not even being sent in the first place. In cases where your campaign is getting 0 replies AND 0 bounces, odds are your provider is preventing you from sending emails. If this is the case for you, your email accounts could be completely fine, you just need to adjust the copy and try again. 5. Positive & Negative feedback loops When it comes to scaling outbound campaigns, the momentum of results you generate will determine your future deliverability. If you have a campaign that’s thriving, deliverability will remain strong and continue to be fruitful as your reputation continues to increase across senders. Vice Versa applies as well though, if you’re generating a lot of negative feedback, your accounts are eventually going to crash & burn.

Your primary domain will always outperform your burner domains. Here's why that's a problem. Had a call recently where a client was frustrated. Their main domain used to get 15–20% reply rates. Now they're running cold email from fresh multi-inbox domains and struggling to hit 2%. The explanation is simple: a primary domain has age, history, normal business correspondence, backlinks, and years of non-spam behavior baked in. That reputation compounds. A cold email from nike(.)com will inbox at a far higher rate than one from acmeoutreachmail(.)com registered last quarter. It's not magic—it's trust accumulated over time. But here's the tradeoff. That's precisely why you don't want to blast cold email from your primary. Once that reputation is damaged, everything is at risk—CEO emails landing in spam, invoices going missing, vendor comms getting flagged. The whole multi-domain, multi-inbox game exists to keep cold outbound at arm's length from the "real" domain. The price you pay: a significant performance >haircut. Those burner domains start life with zero reputation and only ever see cold outreach and negative engagement signals. They're running uphill from day one. There's no way around this tradeoff. You're either borrowing trust from a domain you can't afford to burn, or building trust from scratch on domains that may never catch up. (Well...or buying aged domains at auction...or from ScaledMail) The best you can do is treat your sending domains like assets—age them properly, mix in warm traffic, and accept that they'll never perform like your primary.

⚡ Day 22: Random Data Generation #APITestingSeries by Kishore Kumar D 👩💻 Ever tested APIs using the same email or number again and again? That’s like filling every hotel booking form with the same guest name – boring and unrealistic. 🏨 In real-time, you need dynamic test data. That’s where Postman random variables shine. 👉 Quick Breakdown ✔ {{$randomEmail}} Generates a random, valid-looking email. Example: john.doe123@random.com Use case: Sign-up APIs where unique email IDs are required. ✔ {{$randomInt}} Generates a random integer. Example: 48291 Use case: Randomizing order IDs, invoice numbers, or customer references. ✔ Other goodies: {{$randomUUID}} → Random unique identifier. {{$timestamp}} → Current UNIX time in seconds. 👉 What to Test in Postman ✔ Avoid duplicate data issues in sign-up or create-user APIs. ✔ Generate dynamic order numbers for regression runs. ✔ Simulate real-world randomness (emails, IDs, numbers). ✔ Stress test APIs with large, varied inputs. 👉 Why Random Data Matters ✔ Prevents false positives caused by re-using the same test data. ✔ Makes regression tests repeatable without manual cleanup. ✔ Mimics real-world user behavior (no two customers are identical). 🧪 Real-Time Office Story In one of our e-commerce APIs, testers used the same email for sign-up. After 5 test runs → API started rejecting with 409 Conflict: Email already exists. ⚠ We switched to {{$randomEmail}} in Postman. Every test run created a fresh user, unblocking automation. Result: Continuous regression testing without manual data resets. 🎤 Interview Moment Q: “Why do we use dynamic variables in Postman?” You: “In real projects, APIs often require unique or changing input values. Using Postman’s dynamic variables like {{$randomEmail}} and {{$randomInt}}, we generate fresh data for every run. This prevents duplicate data errors, supports automation, and simulates real-world scenarios. For example, I use {{$randomEmail}} for sign-up APIs to avoid conflicts, and {{$randomInt}} for generating order numbers in regression testing.” 🔮 Tomorrow’s Topic Preview Day 23: API Chaining in Postman Passing data from one request to another. #PostmanTips #PostmanAPI #APITesting #AutomationForTesters

I Have 200+ Online Account With 200+ Emails ��� Sounds crazy! but having dedicated email address for each account can significantly improve your security posture. 🚀 How do I do that? - 𝗘𝗺𝗮𝗶𝗹 𝗔𝗹𝗶𝗮𝘀𝗶𝗻𝗴 Instead of using your primary email for every single account, I create unique, disposable email addresses (aliases) for each service. For example: • Amazon: amazon.djiere@domain.com • Netflix: netflix.ewriw@domain.com • Twitter: twitter.secj@domain.com All these aliases forward straight to my primary inbox (e.g., primary-mail@proton.com), but they keep my real email hidden and protected! BUT WHY??? • Protect Your Primary Email • Prevent Data Breaches • No More Spam Emails • Minimized Attack Surface • Test Online Services • Reduce User Tracking 💡 And guess what? Setting this up is a breeze with tools like SimpleLogin and addy.io. They make aliasing easy, safe, and totally customizable. Note: In 2022, SimpleLogin was acquired by Proton #privacy #security #email #emailsecurity

Email addresses aren’t just a contact. They’re actually potential gateways, too. Your email address opens a door to your digital life. Once you share it, you’re opening up a door - not just to communication, but to unwanted attention, clutter, phishing - or even worse. Your email address is that crucial, so treat it with the security it deserves: ✍ Use a unique email address for each service you sign up for. Add the name of the website or company to it. This way, if leaked, you are aware and can address it. ✍ Make those addresses random, long, unguessable. Every company has a info@ email address. Guess what email address receives a lot of spam? ✍ Rotate them, and invalidate any that get misused.  ✍ Keep a personal email address that you only share with family and friends. Consider using email aliasing services. They’re often free, quick to set up, and allow you to create personalized addresses on the fly. This way, you can track who’s respecting your privacy, and who isn’t. As always, stay secure my friends! #EmailAliasing #Passwords #CyberSecurity