382 Matching Annotations
  1. Last 7 days
    1. cashes in the items above dashboard 2.1/2.2 soften "Hello, Diego!" section follow-ups; keep the greeting exactly as is 4.1-A hairline chapters between Quick actions / Overview / Recent work 5.1 kicker row with "UPDATED TODAY" on the Recent work card 3.2 pick a watermark policy — this page is where it collides most list-cleaning 5.1 kicker row on the jobs card (47 jobs · updated today) 5.2 signature row at the drawer's end 5.3 Ready badge → teal 7.1 one skeleton strip for the table

      dont knwo what this isç

    2. The motto belongs somew

      lets not use dashboard as the title page or anythign already in the menu highlighted based on which page htey are on. the motto is in the footer on the left and the logo in behing=d as now is delph the octopus

    Annotators

    1. ess carries signals of a poor sending history, the kind that tends to hurt inbox placement rather than help it. We do not spell out exactly which signals (that stays behind the scenes). One of these on its own will not sink you, but as a group they bring a much higher cha

      i still don't get how having bad sender rep is an issue inreceiving an email, there must be other things too this label appears for?

    2. he domain's registration has lapsed, so it is dead and nothing can be delivered.

      exaplin that iit may still have active dns, but human person can'T use i unless htye buy it again or someone else does an creates new inbox

    3. A university or school address, usually real and long-lived but often behind strict spam filters.

      i prefer Schools keep mailboxes alive for years, so old addresses linger and still accept mail. The catch: they sit behind aggressive institutional filters, so a low open rate here is usually the filter, not the person.

    4. il address showed up in a known data breach. Breached inboxes tend to get buried in spam, so even when the person is real their engagement often drops, and some of these addresses quietly get abandoned after the breach. It is not an automatic remove,

      approved

    5. the upside of keeping one is tiny, and the downside is that it drags the deliverability of your whole list, not just this one send.

      i don't think this is true same for the description version , why would sending to somepne who has bad sned er rep be bead for me?

    6. The website won't load (a DNS failure), even though the mail server may still be alive. Mail can sometimes still get through, but a site that's fallen off the internet is a sign the domain may be drifting toward abandoned. Keep sending for now if the mailbox responds, but watch for bounces and don't be surprised if this one d

      approved

    7. The domain has no working website (a 404, or no web DNS), though it may still handle email. Plenty of legitimate senders are email-only, so this isn't fatal, it's a yellow flag that the business could be inactive. Send with a light touch and let engagement and bounces tell you whether anyone's really home.

      approved

    8. The address looks made-up rather than real: all numbers, keyboard mashing (asdf, qwerty), test or filler words, or obvious refusals. These usually come from forms with no confirmation step, where people type junk to get past a gate. Deliverable ones can sit in a low-frequency segment, but anything clearly fake is worth removing, and the real fix is a confirmation step so the junk never lands on your list in the first place.

      approved

    9. address turns up on lots of marketing lists, so the inbox is crowded and your mail competes with everyone else's. It's a real, sendable address, engagement just tends to run lower. To earn attention, make the subject line and timing count and keep the

      lets add everything missing from why it matters and how to that isn't already in report text and lets do this then the merge and write mix of all the descriptions nd the longer smart though provoking report description please

    10. This address has the hallmarks of people who tend to hit 'spam' more often than average, based on its pattern and history rather than anything the person has done to you yet. It's still deliverable, so this is a caution flag, not a removal. Only send mail they clearly asked for and expect, keep the unsubscribe obvious and easy, and watch complaints closely, pulling back fast if they climb.

      lets add everything missing from why it matters and how to that isn't already in report text and lets do this then the merge and write mix of all the descriptions nd the longer smart though provoking report description please

    11. A government or public-sector address (.gov and the like). These are real and reachable, but they sit behind strict filters built to block bulk and marketing mail, so even a valid inbox may never see a promotional send. Keep them

      lets add everything missing from why it matters and how to that isn't already in report text and lets do this then the merge and write mix of all the descriptions nd the longer smart though provoking report description please

    12. The domain's registration has lapsed, so it's no longer live and nothing sent to it can be delivered. Usually the business closed, moved, or simply let the domain go. Remove every address on it. If it was an important contact, look for them somewhere else (LinkedIn, a new address) rather than mailing a dead domain.

      lets add everything missing from why it matters and how to that isn't already in report text and lets do this then the merge and write mix of all the descriptions nd the longer smart though provoking report description please

    13. The domain hasn't set up the usual email authentication (SPF, DKIM, DMARC). This doesn't stop you from sending to them, it just tells you the domain owner hasn't locked things down, which makes the domain easy to spoof. Nothing to remove on its own, but if you weren't expecting this signup it's worth a second look, because a fake address is more likely to hide behind an unauthenticated domain. Keep by default and let other signals decide.

      lets add everything missing from why it matters and how to that isn't already in report text and lets do this then the merge and write mix of all the descriptions nd the longer smart though provoking report description please

    14. The domain is missing the basic security setup a maintained domain normally has, which usually means nobody is actively looking after it anymore. Abandoned domains drift toward trouble over time and are a poor bet to keep sending to. Remove these unless you have a specific reason to believe the domain is still care

      lets add everything missing from why it matters and how to that isn't already in report text and lets do this then the merge and write mix of all the descriptions nd the longer smart though provoking report description please

    15. The domain's registration runs out within the next 30 days. If the owner doesn't renew it, the whole domain stops working and every address on it goes dead, so this is a short clock, not a permanent problem. If the contact matters, reach out now while mail still lands and ask for a longer-term address, and re-check the domain in a month. If they renew, the flag clears on its own.

      lets add everything missing from why it matters and how to that isn't already in report text and lets do this then the merge and write mix of all the descriptions nd the longer smart though provoking report description please

    16. s email is invalid, contains a typo in the domain (like gmial.com instead of gmail.com), or shows characteristics of a spam trap. These addresses cannot receive email or are dangerous to send to. Remove immediately. If it's a typo, the email will bounce. If it's a trap, sending damages your reputation. Either way, do not send.

      approved

    17. s email address appears on many marketing lists and likely receives high email volume. Engagement rates may be lower because your email competes with many others in their inbox. Expect lower engagement. To stand out: (1) Use compelling subject lines. (2) Send at optimal times. (3) Personalize content. (4) Consider this a 'harder to reach' segment.

      dont make it as a list, as a apragraph, use lets add everything missing from why it matters and how to that isn't already in report text too

    18. belongs to a government agency or public institution (.gov). These emails are legitimate but often behind strict security filters that may block marketing or bulk messages. No action required - informational label. Be aware that government email se

      remo dash and update sentence to accomodat this change

    19. mail's domain lacks proper email authentication (SPF, DKIM, DMARC). This doesn't affect your ability to send TO them, but indicates the domain owner hasn't implemented security best practices. Usually safe to send, but note: (1) Domains without authentication are easier to spoof - make sure this signup was legitimate. (2) Ma

      dont make it as a list, as a apragraph, use lets add everything missing from why it matters and how to that isn't already in report text too

    20. eliverable. Time-sensitive risk. Options: (1) Send now while you still can. (2) If important contact, reach out for alternative email. (3) Re-validate after expiration date to see if they renewed.

      write as Paragraph not as a list 123

    21. The address shape looks auto-generated or intentionally fake

      CHANGE TO: The address looks made-up rather than real: all numbers, keyboard mashing (asdf, qwerty), test or filler words, or obvious refusals. These usually come from forms with no confirmation step, where people type junk to get past a gate. Deliverable ones can sit in a low-frequency segment, but anything clearly fake is worth removing, and the real fix is a confirmation step so the junk never lands on your list in the first place.

    22. The domain's website returns a 404 error

      CHANGE TO: The domain has no working website (a 404, or no web DNS), though it may still handle email. Plenty of legitimate senders are email-only, so this isn't fatal, it's a yellow flag that the business could be inactive. Send with a light touch and let engagement and bounces tell you whether anyone's really home.

    23. The domain's website is unreachable (DNS failure)

      CHANGE TO: The website won't load (a DNS failure), even though the mail server may still be alive. Mail can sometimes still get through, but a site that's fallen off the internet is a sign the domain may be drifting toward abandoned. Keep sending for now if the mailbox responds, but watch for bounces and don't be surprised if this one degrades.

    24. The domain shows a 'parked' or 'for sale' page

      CHANGE TO: The domain shows a 'parked' or 'for sale' page instead of a real site, which usually means it's expired, abandoned, or being held by a squatter rather than run by a real business. Mail to it is a coin flip at best. Remove these, because the person or company you thought was there almost certainly isn't sending or receiving from this address anymore.

    25. The domain was registered less than 30 days ago

      CHANGE TO: The domain was registered less than 30 days ago, so it has almost no track record yet. It might be a brand-new business or something short-lived thrown up for a single purpose. Nothing to remove, just watch it: if real engagement develops the flag stops mattering, and if it goes quiet or starts bouncing, treat it as the throwaway it might be.

    26. Domain belongs to a military organization

      CHANGE TO: A military address (.mil). Mail routes through the Department of Defense gateway, which accepts everything at the door but then filters hard inside and often drops what it doesn't like without a bounce, so a real inbox can still silently swallow your mail. Keep them if they're your audience, but treat delivery here as unproven, watch engagement rather than trusting 'delivered', and don't read a lack of bounces as success.

    27. The recipient's mailbox has exceeded its storage quota

      CHANGE TO: The person's mailbox is over its storage limit and can't take new mail right now. Sometimes that's temporary, but an inbox that stays full is usually one nobody empties anymore, meaning abandoned. We'd suppress these by default. If you want to give them a chance, park them in a retry segment and re-check in 60 to 90 days before sending, rather than mailing into a full box now.

    28. Email domain belongs to a defunct or acquired ISP

      CHANGE TO: The address is on a defunct or absorbed ISP (sbcglobal.net, earthlink.net, prodigy.net and similar). These still receive mail, but nobody's really maintaining the service anymore, and many are checked rarely or not at all. On its own it doesn't change the verdict, so keep it, but if it pairs with other caution flags or shows no engagement, lean toward retiring it.

    29. This domain appears on threat intelligence lists

      CHANGE TO: This domain shows up on threat-intelligence lists tied to malware, phishing, or other malicious activity. An address here often means a compromised or throwaway account, and mailing it does nothing good for you. Remove it right away. If it's genuinely someone you know, assume their account may be compromised and find a different way to reach them before sending anything.

    30. This email address appears on many marketing lists

      CHANGE TO: This address turns up on lots of marketing lists, so the inbox is crowded and your mail competes with everyone else's. It's a real, sendable address, engagement just tends to run lower. To earn attention, make the subject line and timing count and keep the content genuinely relevant to them; if they never engage, treat them like any other cold contact and taper off.

    31. This email has characteristics associated with higher spam complaint

      CHANGE TO: This address has the hallmarks of people who tend to hit 'spam' more often than average, based on its pattern and history rather than anything the person has done to you yet. It's still deliverable, so this is a caution flag, not a removal. Only send mail they clearly asked for and expect, keep the unsubscribe obvious and easy, and watch complaints closely, pulling back fast if they climb.

    32. Domain belongs to a government agency or public institution

      CHANGE TO: A government or public-sector address (.gov and the like). These are real and reachable, but they sit behind strict filters built to block bulk and marketing mail, so even a valid inbox may never see a promotional send. Keep them, but expect low reach on anything that looks like marketing, and lead with plain, expected, relevant mail.

    33. The domain registration has lapsed and is no longer active

      CHANGE TO: The domain's registration has lapsed, so it's no longer live and nothing sent to it can be delivered. Usually the business closed, moved, or simply let the domain go. Remove every address on it. If it was an important contact, look for them somewhere else (LinkedIn, a new address) rather than mailing a dead domain.

    34. The email's domain lacks proper email authentication

      CHANGE TO: The domain hasn't set up the usual email authentication (SPF, DKIM, DMARC). This doesn't stop you from sending to them, it just tells you the domain owner hasn't locked things down, which makes the domain easy to spoof. Nothing to remove on its own, but if you weren't expecting this signup it's worth a second look, because a fake address is more likely to hide behind an unauthenticated domain. Keep by default and let other signals decide.

    35. The domain lacks basic security configuration and shows signs

      CHANGE TO: The domain is missing the basic security setup a maintained domain normally has, which usually means nobody is actively looking after it anymore. Abandoned domains drift toward trouble over time and are a poor bet to keep sending to. Remove these unless you have a specific reason to believe the domain is still cared for.

    36. The domain's registration expires within 30 days

      CHANGE TO: The domain's registration runs out within the next 30 days. If the owner doesn't renew it, the whole domain stops working and every address on it goes dead, so this is a short clock, not a permanent problem. If the contact matters, reach out now while mail still lands and ask for a longer-term address, and re-check the domain in a month. If they renew, the flag clears on its own.

    37. is is a role-based email (info@, support@, sales@, etc.) rather than a personal address. Role accounts are shared inboxes with higher complaint risk because

      approved. we can add a "cta" to decide if they wan to send to all the role accon=unts, or remove people that might not be the same or interested?

    38. This is a role-based email (info@, support@, sales@, etc.) rather than a personal address. Role accounts are shared inboxes with higher complaint risk because multiple people access them. Consider your use case. For marketing: send less frequently, expect higher complaints. F

      lets add everything missing from why it matters and how to that isn't already in report text too in this definition

    39. his email shows reputation risk signals such as reputation-risk address characteristics or reputation-risk patterns. Sending may damage your sender reputation.

      this means nothing, can e make it ore clear without being specific?

    40. This email is from a legitimate privacy/forwarding service like Apple Hide My Email, Firefox Relay, AnonAddy, or SimpleLogin. These forward to the user's real inbox - the person is reachable but privacy-conscious.

      remove the dashes, and explain what that means for them simply put? harder spam filters, lower thresholds?

    41. This is a temporary/disposable email address. These addresses self-destruct or become inaccessible after a short time. The person wanted your offer but not an ongoing relationship. Remove from marketing lists. Consider: the person may have wanted a one-time download (PDF, resource). You may allow the signup and deliver gated content, but skip follow-up emails.

      lets add everything missing from why it matters and how to that isn't already in report text

    42. The domain has no mail server (MX records) configured. This means there's no technical capability to receive email at this domain. The domain might exist as a website but cannot receive email. Remove all emails from this domain immediately. There's zero chance of delivery. If this is a known contact, reach out through other channels to get an updated email.

      how is this different from invalid email? no mx records is als invalid email no? (the same as Invalid/Typo/Trap no?)

    43. The domain's website shows a "coming soon" or placeholder page. The domain is active and connected, but no real website content exists yet. This might indicate a new business or inactive project. Usually safe to send. The domain is functional, just not fully launched. Monitor for changes - if the site never launches, the business may have stalled.

      Some of these mght be new domains that have automatically adde mx records but not real person, or there is a real person they just donM 't on'T care about having a website

    44. The mail server accepts all incoming email without verifying if specific mailboxes exist.

      lets add everything missing from why it matters and how to that isn't already in report text Accept-All is high. Be smart about how you read "delivered" About 21% of this sample is on Accept-All servers. For B2B outreach this is normal (lots of corporate Microsoft 365 / Mimecast / Proofpoint behind those domains), but it means a "delivered" status from your sending tool is NOT the same as "the inbox actually exists." Mailbox providers will silently drop unknown addresses on accept-all servers, and those failures show up as zero engagement, not as bounces. Watch click rates per domain. Accept-All domains with consistent 0% clicks across multiple campaigns are likely dead boxes.

      Accept-All 412 emails Accept-all mail servers say yes at the connection level without revealing whether a specific mailbox is active. Our checks can verify some of these addresses directly, but not all of them depending on how the server is configured. Consumer providers like Yahoo and AOL often run in accept-all mode, and on business domains this usually comes from security gateways such as Proofpoint, Mimecast, or Barracuda sitting in front of the real inbox. We tag every address on an accept-all server so you can track them as their own segment and watch how they behave in your campaigns. Segment these addresses into their own group and send to them separately from your other contacts. Track their engagement (opens, clicks, replies) over a few sends. Addresses that engage can be moved into your main list with confidence. Addresses that never engage after multiple sends are safe to segment aside for re-engagement campaigns or suppression, depending on your goals.

      66% of this list is in great shape to send to For a combined tax marketing and booking customer list, the validation profile is healthy. Only 29 of 598 addresses (4.8%) need removal. The Monitor segment is mostly Accept-All on consumer providers like Yahoo and Hotmail, where the addresses are real but the providers respond conservatively to validation queries. These should still be sent to. Accept-All 123 emails Accept-all mail servers say yes at the connection level without revealing whether a specific mailbox is active. Our checks can verify some of these addresses directly, but not all of them depending on how the server is configured. Consumer providers like Yahoo and AOL often run in accept-all mode, and on business domains this usually comes from security gateways such as Proofpoint, Mimecast, or Barracuda sitting in front of the real inbox. We tag every address on an accept-all server so you can track them as their own segment and watch how they behave in your campaigns. Segment these addresses into their own group and send to them separately from your other contacts. Track their engagement (opens, clicks, replies) over a few sends. Addresses that engage can be moved into your main list with confidence. Addresses that never engage after multiple sends are safe to segment aside for re-engagement campaigns or suppression, depending on your goals.

      Accept-All 19,281 emails Accept-all mail servers say yes at the connection level without revealing whether a specific mailbox is active. Our checks can verify some of these addresses directly, but not all of them depending on how the server is configured. Consumer providers like Yahoo and AOL often run in accept-all mode, and on business domains this usually comes from security gateways such as Proofpoint, Mimecast, or Barracuda sitting in front of the real inbox. We tag every address on an accept-all server so you can track them as their own segment and watch how they behave in your campaigns. Segment these addresses into their own group and send to them separately from your other contacts. Track their engagement (opens, clicks, replies) over a few sends. Addresses that engage can be moved into your main list with confidence. Addresses that never engage after multiple sends are safe to segment aside for re-engagement campaigns or suppression, depending on your goals. all incoming mail at the gateway but may silently discard messages that don't pass security checks. Monitor carefully. Military domains accept all email at the gate (accept-all) but have aggressive internal filtering. Bounces may not be reported, making it hard to detect delivery failures.

      Accept-All 1,320 emails Accept-all mail servers say yes at the connection level without revealing whether a specific mailbox is active. Our checks can verify some of these addresses directly, but not all of them depending on how the server is configured. Consumer providers like Yahoo and AOL often run in accept-all mode, and on business domains this usually comes from security gateways such as Proofpoint, Mimecast, or Barracuda sitting in front of the real inbox. We tag every address on an accept-all server so you can track them as their own segment and watch how they behave in your campaigns. Segment these addresses into their own group and send to them separately from your other contacts. Track their engagement (opens, clicks, replies) over a few sends. Addresses that engage can be moved into your main list with confidence. Addresses that never engage after multiple sends are safe to segment aside for re-engagement campaigns or suppression, depending on your goals. ✓ 3,159 addresses are clean and safe to send first The Keep bucket is deliverable-only. Every risky, low-confidence, and accept-all-without-a-website address has been pulled out into Monitor or Suppress, so what is left in Keep is what a fresh sender can lead with.

      One ask: if any of these bounce because the mailbox genuinely does not exist (a true "no such user" bounce, not a blocklist or content block), tell us at lists@reviewmyemails.com and we will credit 2 emails back. It helps us learn and improve the checks, and you get the credits. 1,885 addresses are real but need care (Monitor) Monitor is where the address is real but comes with a caveat, and the decision on each is yours. Some sit on accept-all servers: we confirmed the domain is live and its mail server responds, but the server says "yes" to every address at the connection level, so the one specific mailbox cannot be confirmed active by any tool. That is their server's setting, not a gap in our check. Another 1,334 verified as real but with lower delivery confidence. Many of these domains also sit behind security gateways like Proofpoint, Mimecast and Barracuda that only let mail through from senders they already trust, so even a real, active inbox can block a cold sender until you are recognised or allowlisted. A few carry other flags (breach history, a shared role inbox, heavy mail volume), each explained per label below.

      Go label by label below and decide what fits your risk tolerance: som e are worth sending to with care, others you may prefer to hold back. Either is a valid choice. Accept-All 1,416 emails These sit on a server that says "yes" to every address at the connection level, so we cannot confirm whether the individual mailbox actually exists. That is the key difference from Low Delivery Confidence, where we did get a mailbox-level answer. Consumer providers like Yahoo and AOL run this way, and on business domains it usually comes from a security gateway (Proofpoint, Mimecast, Barracuda) sitting in front of the real inbox. We tag every accept-all address so you can track them as their own segment. Do not blast these. Sprinkle a few into your sends over time rather than hitting them all at once, use a shorter sequence with bigger gaps between emails, and cut them off faster if they show no engagement. The ones that do engage can move into your main list; the rest you set aside. Low Delivery Confidence 1,281 emails We checked these mailboxes and they came back real, but with a "risky" signal. This is the key difference from Accept-All: with Accept-All the server accepts everything and hides whether the specific mailbox exists, whereas here we did get a mailbox-level answer, it just was not a clean pass. It usually means the domain or provider has a weaker sending reputation, or the domain is small and low-traffic. These are worth sending to, just keep a close eye on them: track opens and bounces, and drop any that hard-bounce on the first touch. Yahoo and AOL cannot be individually verified, and that is normal These providers run accept-all servers: they say "yes" to every address at the connection level, so no tool can confirm one specific mailbox. That is their server's design, not a gap in the check. Since these subscribers opted in, keep them, but Yahoo and AOL are strict on complaints, so send consistently and prune anyone who never opens.

      Accept-All 609 emails Accept-all mail servers say yes at the connection level without revealing whether a specific mailbox is active. Our checks can verify some of these addresses directly, but not all of them depending on how the server is configured. Consumer providers like Yahoo and AOL often run in accept-all mode, and on business domains this usually comes from security gateways such as Proofpoint, Mimecast, or Barracuda sitting in front of the real inbox. We tag every address on an accept-all server so you can track them as their own segment and watch how they behave in your campaigns. Segment these addresses into their own group and send to them separately from your other contacts. Track their engagement (opens, clicks, replies) over a few sends. Addresses that engage can be moved into your main list with confidence. Addresses that never engage after multiple sends are safe to segment aside for re-engagement campaigns or suppression, depending on your goals.

    45. The domain has no MX records configured, meaning it cannot receive email. Any emails sent will bounce. Remove immediately. This domain is not configured to receive email. All sends will fail.

      its a bit repetitive

    46. Domain belongs to a university, college, or educational institution. These domains

      lets add everything missing from why it matters and how to that isn't already in report text . reply here with change and then once approved replace it

    47. This email is from a service that provides persistent but often temporary-use inboxes. Free tiers of privacy-focused providers or lesser-known email services fall here - real inboxes that may go inactive over time. Include but track engagement separately. These are real inboxes with real people, but usage patterns vary. Some users are privacy-conscious and engaged; others created the account for a single purpose and may never check it again.

      approved

    48. This email is from a short-lived disposable service like Guerrillamail, Mailinator, or 10MinuteMail. The inbox exists for minutes to hours before self-destructing or becoming inaccessible. Remove from ongoing campaigns. The person wanted your content but not a continued relationship - perhaps they grabbed a PDF or signed up for a webinar replay. Allow the initial delivery but do not expect engagement afterward.

      approved

    49. This email is from a refresh-based disposable service where the inbox exists only momentarily - often just for the duration of a browser session. Services like Tempmail or Fakeinbox create addresses that disappear when the page is refreshed or closed. Remove from email lists. These inboxes may not exist by the time you send. The person likely wanted a one-time download or access - consider allowing the signup but skipping follow-up emails entirely.

      approved

    50. This email address appeared in a known data breach. Breached emails are often abandoned after the breach, sold to spammers, or converted to spam traps. Higher risk of deliverability issues.

      Let's just remove the last sentence or replace something else because reach in a lot of things so it's just like these emails might be a band that have lower engagement because you get too much and we need to add the white matter

    51. The mail server accepts all incoming email without verifying if specific mailboxes exist. We can't confirm if this exact address is real - the server says 'yes' to everything then may bounce later.

      We need a better way to say this like some of these inboxes we can't actually tell like like a weird way but like if a yahoo email says it's except all and it works but then I tried to go sign up with it and I can then I'm about provider doesn't doesn't exist whereas if I try to create an account with just does exist don't exist so there are ways to check certain thingsbut is also a waste like do some deep checks but an acceptable inbox has been created to accept any variation of the username so instead of saying that we can't verify it let's just explain what it is it's possible it's some small cases to actually figure out if an inbox does or does not exist but except all is a domain that's been set up to meaning any username from a domain email address to go to a specific inbox and that's it and so how to and the white it's important we need to beat it up it has a higher stress it's more difficult to check if the email just doesn't engagement and which kind of accept all is important yahoo versus a main base one and making a decision on which wants to keep overtime or how long to keep them is important so they can create like a graph of all the six of these inboxes to create like a baseline and anybody who falls below the baseline get kicked off I thought amount of time the baseline says someone is less likely to return and pay or engage in why and the way it matters is that these emails will not bounce if they actually stop existing which is uneven worse thing than having the wrong email address or something and you not realizing this address is dead so

    52. Parked PageMERGED-merged into Parked Domainsuppress · highThe domain shows a 'parked' or 'for sale' page instead of a real website. Parked domains are often expired, abandoned, or held by domain squatters. Email delivery is unreliable or impossible.Remove these emails. Parked domains indicate the business or person is no longer operating at this address. Very high chance of bounces or being a recycled spam trap. Possible InvalidMERGEDvaliditymerged into Unverifiable Inboxmonitor · mediumThe email couldn't be fully verified but isn't definitively invalid. The mail server didn't give a clear yes or no. There's a chance this email will bounce.Send with caution and monitor bounces. If this email bounces, suppress it immediately. Consider sending less critical content first to test deliverability. Potential TrapMERGEDreputation

      what are these merged into or with which other label can you add it here and then show me the label or add it I guess it should be one of the new labels or in use I guess

    53. Disposable - InstantMERGEDdisposablefolded into Disposablesuppress · criticalThis email is from a refresh-based disposable service where the inbox exists only momentarily - often just for the duration of a browser session. Services like Tempmail or Fakeinbox create addresses that disappear when the page is refreshed or closed.Remove from email lists. These inboxes may not exist by the time you send. The person likely wanted a one-time download or access - consider allowing the signup but skipping follow-up emails entirely.These are the most extreme disposable emails. The inbox may literally not exist moments after signup. Sending will result in bounces. Disposable - Short-livedMERGEDdisposablefolded into Disposablesuppress · criticalThis email is from a short-lived disposable service like Guerrillamail, Mailinator, or 10MinuteMail. The inbox exists for minutes to hours before self-destructing or becoming inaccessible.Remove from ongoing campaigns. The person wanted your content but not a continued relationship - perhaps they grabbed a PDF or signed up for a webinar replay. Allow the initial delivery but do not expect engagement afterward.Short-lived disposables are used to bypass signup forms. The person explicitly chose not to give you a real email - respect that by not attempting ongoing communication. Disposable - TemporaryMERGEDdisposablefolded into Disposablemonitor · mediumThis email is from a service that provides persistent but often temporary-use inboxes. Free tiers of privacy-focused providers or lesser-known email services fall here - real inboxes that may go inactive over time.Include but track engagement separately. These are real inboxes with real people, but usage patterns vary. Some users are privacy-conscious and engaged; others created the account for a single purpose and may never check it again.Unlike instant disposables, these addresses may receive and read your emails. However, lower engagement rates are common. Worth trying but watch closely.

      For the disposable I wanted to be clear that in the database and Hetzner we have these labels in use but on the reports and for the client it's only disposable as a label and yes or whatever in the cell of the column disposable or whatever temporary email whatever we call it. what do you call the column of disposable email addresses where we say yes or – for now in the export what is that column called

    1. Single-check "Recent checks" history panel (7 entries, "kept for 60 days")Mongo results have a 60-day TTL ✓, but a per-user single-check history endpoint could not be confirmedKeep the design verify data exists — real frontend has a HistoryResultCard, confirm its source (may be client-side only)

      i donT' know how to check htis

    2. ng pricing slider/presets hardcoded ($0.0062/email etc.)GET /billing/pricing returns real tier boundaries + POST /billing/calculate prices any quantity

      dont know what that means. is it bad? its jsut to show templates in react to devs for reskin, and some corrections

    3. Team invite roles "Admin / Member" onlyBackend supports Owner + permission_template: read_only | validator | member and per-permission flagsEither add the templates to the dropdown or explain Owner somewhere (table shows one)

      sure we can make pop up contact your admin

    4. job rows are unnamed <button>s (screen reader hears "button" ×10); div-tables expose header cells as plain generic nodes (no columnheader/row roles, no aria-sort); confirm-email and reset-password each contain three <h1>s; api-docs jumps h2→h4; dashboard has zero alt text. Each is a one-line fix; do them as a sweep.

      we can fix those accross the board too right?

    5. Every purchase path lands on the billing-purchase.html stub; sidebar "Billing" (Pricing & Plans) vs settings tab "Billing" (Billing Settings) are two different pages with one name; dashboard-states/onboarding sidebars link everything to # and omit Settings while adding "Analytics" (sender-profiles' sidebar also sneaks "Analytics" in); error pages drop the whole app shell. Normalize the nav from one shared partial.

      yea i agree billing setting should just be in billinf and sender preference should be in same place as notification we already have notdsa bout this and other things

    6. e wins sitting in existing responses: credits_saved + cache_hit_count (the "we didn't re-charge you" story), queue_position / estimated_completion / full progress steps with ETA, estimated_credits_min/likely/max for uploads, days_remaining_at_current_rate for billing, the per-job health score + badge + callouts, unique_domains + top_flagged_domains in the results breakdown, typo_suggestion / did_you_mean, segmented downloads (keep|monitor|suppress|did_you_mean + ZIP), and API-key last_used_at / usage_count / expires_at. Individual suggestions below.

      ok no problem to all

    7. Credit pill says 8,450 on most pages, 1,000 on dashboard-states/onboarding, 8,449 on single-check; billing.html's low-balance banner says the balance is 820 in the same viewport as the 8,450 pill; billing-history's newest "Balance After" is 58,450; list-cleaning-new claims You need 40,450 more credits while showing cost 5,200 vs balance 8,450. Pick one coherent demo account state and thread it through every page.

      ok sure we can fix that easy

    8. e scaffolding is leaking into the product surface. "Prototype state:" switchers, the floating 🆕 New pattern badge (login, 404, api-docs, settings-api-keys), Preview — sample data captions, and design-spec prose rendered as body copy (settings-api-keys: In the app this dialog opens centered over a page scrim…; team.html: Cancel invitation confirms the same way…; sender-profiles: Shown open for the handoff…). Fine for handoff review — but tag them all with one consistent data-proto wrapper/class now so they can be stripp

      i don't knwo what this emeans

    9. job-status vocabulary, please. The backend enum is pending · queued · processing · completed · failed · cancelled (rme-backend/app/models/postgres/job.py). The reskin uses three different sets: dashboard badges say Done / Cleaning / Uploaded / Failed, list-cleaning badges say Complete / Cleaning / Ready, and the list-cleaning status filter offers Completed / Processing / Queued / Failed / Cancelled — so the filter options never match the badges beside them. Pick one display mapping (e.g. Queued

      lets update our front end to say the same thing like the backend says add that to glossary with description that are short but explian well what each process means

    10. 2 · Verdict & label terminology drift. Canonical backend verdicts are keep / monitor / suppress. The reskin mostly says "To Keep / To Monitor / To Suppress" (good), but: the dashboard chart legend shortens to "Keep / Monitor / Suppress", api-docs.html says safe, monitor, suppress, glossary prose says "Temporary Email" where the profile editor and single-check say "Disposable", and 403.html says "team admin" where team.html distinguishes Owner/Admin. One glossary of terms, applied everywhere. (The 29-label glossary set also doesn't match any of the three label sources in the codebase — see the drift table below.)

      Let tell the devs to update it then To Keep, etc

    1. This email address appeared in a known data breach. Breached emails are often abandoned after the breach, sold to spammers, or converted to spam traps. Higher risk of deliverability issues. Proceed carefully. The email might still be valid, but: (1) The person may have abandoned it post-breach. (2) It might receive more spam, making engagement harder. (3) Track bounce and engagement rates separately for breached em

      lets add everything missing from why it matters and how to that isn't already in report text and all the following Breached ompromised Address 149 emails This email address has appeared in a known data breach. The account may have been abandoned, taken over, or is now used as a spam trap by security researchers. Send with caution. If the address has been abandoned since the breach, it may bounce or generate complaints. Compromised Address 86 emails This email address has appeared in a known data breach. The account may have been abandoned, taken over, or is now used as a spam trap by security researchers. Send with caution. If the address has been abandoned since the breach, it may bounce or generate complaints. Compromised Address 14,695 emails This email address has appeared in a known data breach. The account may have been abandoned, taken over, or is now used as a spam trap by security researchers. Send with caution. If the address has been abandoned since the breach, it may bounce or generate complaints.

      Compromised Address 757 emails This email address has appeared in a known data breach. The account may have been abandoned, taken over, or is now used as a spam trap by security researchers. Send with caution. If the address has been abandoned since the breach, it may bounce or generate complaints. ,885 addresses are real but need care (Monitor) Monitor is where the address is real but comes with a caveat, and the decision on each is yours. Some sit on accept-all servers: we confirmed the domain is live and its mail server responds, but the server says "yes" to every address at the connection level, so the one specific mailbox cannot be confirmed active by any tool. That is their server's setting, not a gap in our check. Another 1,334 verified as real but with lower delivery confidence. Many of these domains also sit behind security gateways like Proofpoint, Mimecast and Barracuda that only let mail through from senders they already trust, so even a real, active inbox can block a cold sender until you are recognised or allowlisted. A few carry other flags (breach history, a shared role inbox, heavy mail volume), each explained per label below.

      Go label by label below and decide what fits your risk tolerance: some are worth sending to with care, others you may prefer to hold back. Either is a valid choice. Compromised Address 117 emails This address has appeared in a known data breach. It may still be a normal working inbox, or the person may have gone quiet on it since. We have placed it in Monitor, but the call is yours. The mailbox is deliverable, so it will not bounce; the realistic outcomes are that the person engages, ignores it, or clicks "report as spam". Decide by your own risk tolerance: send with care, or hold it back. 2,253 are real but carry a signal to watch (Monitor) Most of the Monitor bucket is normal for consumer email: addresses that have appeared in a data breach (Compromised), that sit on a lot of marketing lists (Saturated), or that have a higher historical complaint pattern. These are still your customers and still sendable, they are just the ones to watch for complaints and engagement. A separate 268 are flagged Possible Invalid (short or numeric localparts) for you to eyeball, and most will be real.

      Compromised Address 911 emails This email address has appeared in a known data breach. The account may have been abandoned, taken over, or is now used as a spam trap by security researchers. Send with caution. If the address has been abandoned since the breach, it may bounce or generate complaints.

    2. Schools keep mailboxes alive for years, so old addresses linger and still accept mail. The catch: they sit behind aggressive institutional filters, so a low open rate here is usually the filter, not the person

      use this as final glossary description

    1. No action required. This is an informational label.

      These inboxes can be hearder to inbox, and are more"emotional". can trigger issues from even one complaint or small negative thing. So if not needed or want to ignore small inboxes, =they can chyeck and drop these emals or monitor them.?

    1. Auto-generated number IDs 1,639 emails Real examples from this list cr8716311@gmail.comak781105@hotmail.comdp7121256@gmail.comav3736262@gmail.comas698144@gmail.com1961rj51@gmail.comdm971378@gmail.com

      can all thee section not have a sub container with beig background and jsut show two columns of info? side bby side make it take less space?

    2. Unverifiable Inbox 1,783 emails Verification could not complete (legacy ISPs, strict servers). Unknown is not bad, it is unknown.

      Unverifiable Inbox 1,783 emails Verification could not complete (legacy ISPs, strict servers). Unknown is not bad, it is unknown.

      doe sthis mean we couldn't check and give a reponsse? so we give 1783 credits back?

    3. Mailbox Full 1,790 emails The inbox is over its storage quota. Often a real person whose storage lapsed, so we do not force-remove. Our recommendation: suppress these from campaigns, keep them in a retry segment, and re-validate in 60-90 days.

      lets add in bold in description this label is in to monitr. so if it is the ony label for the meail the email will be marked as to monitor in the csv file.

    4. Three separate signals, and each address carries at most one of them, so these numbers do not overlap. Saturated Inbox (10,423): the address shows up on many email lists. Not fake, just someone who receives a lot of marketing mail, with lower engagement and higher unsubscribe rates. Compromised Address (15,880): the address appeared in known data breaches. Sending still works, but breached addresses are more likely to be abandoned or end up on trap lists. Spam Report Risk (8,905): signals suggest this address has a pattern of reporting mail as spam, and each report counts against sender reputation. Keep them, but in a low-frequency segment. Judge these by clicks and purchases, not opens.

      are we using the right terminology? for saturated inbox or compromised addressetc?

      also why are they one label instead of three? do we have three labels or we have merged ones as engagement risk signals?

    5. Accept-All 51,596 emails The domain accepts mail to any address, so individual mailboxes cannot be confirmed. 49,606 are on consumer providers (the Yahoo family behaves this way by design and stays in Keep when nothing else is wrong); 1,990 are on business domains where the uncertainty is rea

      For the accept all some of them can be checked with deep checks etc, so we need to explain what it is, but without losing its meaning or useflnness? what do you think we shoudl write?

    Annotators

  2. Jul 2026
    1. Hook: Everyone says email is dead. 4.6 billion people didn't get the memo. — Beats 1–2, end on "you can reach them, every time."

      This is the hook, but we need the rest? ii gues we jsut didnT' make it yet right?

    1. Yes, send me the two monthly emails. The Deliverability Dispatch (deliverability know-how) and Notes from Yanna-Torry (her take on the industry, plus the occasional Review My Emails product update). Manage or leave any time from any email. Track my opens and clicks to tailor what I get. Optional, off any time.

      this is the correct form that should be on all the pages at the bottom of the page that they have it but we still have the little bug from yesterday where the checkbox is centered in like two columns and a text in another column we need the checkbox to the complete left at th level as where the email field starts and then the tax for the fields need to be closer to the checkbox so it doesn't end up being 27 lines

    2. ghts

      I don't know why it seems to be in a column on the left there's nothing on the right so either center it and make the insights waitlist just a little bit longer so that it's not so tight and small

    1. ionKeeps you signed in to the dashboard. Required for the service to work af

      for now there's no app so it should be as well the free tools I don't know if that works there but if they give us a email we will remember them as long as they don't clear the cookies for extra amount of time

    1. It’s not a mystery.

      I need something stronger like maybe not it's not a scam but something along the lines at good business cards makes good friends or if one sex if one of us succeed we all do kind of thing and maybe something along the lines that we're not too small for any kind of help everybody needs to grow some way in I don't know I don't have $1 million to put in Google art I would much rather work with partners then spend my time marketing myself and why not share the knowledge I have with one person who was lots of customers then try to manage individually I want to change the way people think about email their knowledge s let's give access to everyone to grow together

    2. ou do not need to manage the relationship after the referral. We handle the cleaning, the report, the walkthrough. You just need to make the introduction. 1 introduction. That is your whole side of the work. Drop the link, make the connection. 48h average turnaround from upload to a report your client can act on. Our side. 15% of every credit purchase they ever make comes back to you. Monthly, net 30.

      let's make the text on the left a smaller column so that the table with the one $40.15 percent has more space and I think the font still too small

    1. Because I have been stuck before too. Staring at bounce logs at midnight, Googling error codes, not sure who to ask. Most email questions fall into a handful of common patterns. Answering them takes me five minutes and saves you five hours. If you need more than guidance, I also do done-for-you list reviews, but no pressure.

      replace with Trust beats tactics.

      We offer real help without charging because it is the right thing to do. Most questions fall into a few common patterns I see every week. Some people need a quick answer. Some need deeper support. Either way, the conversation starts the same.

      If you need more than guidance, we offer done-for-you list reviews with expert interpretation included. But there is no pressure. The SOS Hotline exists to help, not to sell.

    2. Litmus Coach 2020·Ask a Deliverability Expert·8,000+ lists reviewed·Lenovo Twinning Finalis

      Litmus Coach Award 2020 MARsum Top 100 Marketing & Advertising Leaders 2021 Marketing 2.0 Best Business Award 2022 Lenovo Twinning Finalist 2026 this issue seems to have persisted across the website other than the 8000+ less reviewed unless it's specifically done this way we need to add the rest of the awards

    1. Start free

      We need to save a copy of this page as is but we need to update the text a little bit or at least the call to action because we're telling him go clean your list but the app isn't coming out for a couple more weeks so what we can do is offer them to sign up with their email no password and sign it with the newsletter to get 15,000 free extra credit on top of the 1000 and unless they click the checkbox for the newsletter they will only get an email to let them know that the app is available online and that they got their 15 while they're 16,000 credits the wood free gets you free credits and everything like that is fine is just that the apps already yet so many people to get on the waiting list

    1. Runs the things that make every customer feel handled. Makes sure no question gets dropped and every customer leaves understanding what we did.

      here is her job description, maybe something better you can peopose?DESCRIPTION The Head of Operations & Growth is the operational backbone of Review My Emails and Shipshape. She runs point on everything that keeps the two businesses moving day to day: localization and translation across English and Vietnamese, marketing and social planning, Vietnamese market development, competitive and customer research, freelancer management, and serving as the founder's primary sparring partner on new ideas. The role sits at the intersection of operations, marketing, and growth, and its scope is intentionally broad. If it is not the founder's job to do directly, it is very likely hers RESPONSIBILITIES Translate and localize content across English and Vietnamese for both Review My Emails and Shipshape, including product copy, marketing content, customer communication, partner outreach, and training material. Tone and cultural fit matter as much as literal accuracy. Own the marketing and social media calendar across both brands. Plan content, brief designers and writers, coordinate publishing across channels, and monitor engagement and performance. Develop the Vietnamese market for both companies. Identify partners, prospects, and channels. Coordinate introductions, meetings, and follow-through with customers, resellers, agencies, and communities in Vietnam. Run research on competitors, pricing, new tools, and new market segments. Return usable, decision-ready findings, not raw information dumps. Manage the freelancer bench across both companies. Recruit, brief, review deliverables, coordinate payment, and hold quality and turnaround standards. Serve as the founder's sparring partner. Hear new ideas first, pressure-test them, flag risks, push back when something is half-baked, and translate loose ideas into concrete plans, briefs, and next steps. Coordinate the day-to-day operational tasks that keep the businesses running: recordkeeping, small procurement decisions, tool subscriptions, freelancer contracts, and cross-team logistics. Represent the founder's voice and standards internally and externally with freelancers, partners, and vendors. Decisions made in this role carry the same weight as the founder's own. Contribute to strategic planning across both businesses (goals, priorities, quarterly focus) and hold the team accountable to what has been agreed. Other responsibilities as the businesses evolve. Both companies are early stage and scope will shift as they grow.

    2. Builds the backend, then tries to break it. Tests every path and checks every edge, so what we ship is actually right.

      here is her description frok linked in, maybe something better you can peopose?Software Engineer with experience designing, developing, and deploying intelligent solutions in production environments. Strong background in AI-driven systems, automation, and data-centric software engineering.

      Focused on building and operationalizing AI pipelines and inference systems, integrating predictive models into scalable applications using DevOps and MLOps best practices, with emphasis on code quality, reliability, and production readiness.

      Experienced in LLM-based agents, RAG systems, computer vision, data pipelines, and inference APIs, working with Python, Flask, Django, Docker, SQL databases, vector stores, and cloud-native environments.

      Hands-on and collaborative professional, comfortable in technically complex projects and multidisciplinary teams, delivering AI solutions that generate measurable business impact.

    3. Built the reasoning layer behind the verdicts. Not the kind of AI that writes your emails for you. The kind that reads dozens of signals per address and explains, in plain English, why one is risky and what to do about it.

      here is his description frok linked in, maybe something better you can peopose?Bruno S. Brasil is a Cloud Engineer with a deep-rooted expertise in Linux, which he has used since childhood. His career began in on-premises environments, transitioning smoothly to cloud computing as he embraced the DevOps culture. Specializing in Google Cloud Platform, Bruno has successfully led and contributed to various projects across industries such as digital banking, marketplaces, and startups, both as a consultant and engineer. He is dedicated to promoting best practices in infrastructure as code, advocating for DevOps principles, and implementing SRE strategies. A passionate Open Source community supporter, Bruno firmly believes it plays a crucial role in fostering innovation and the development of new talent and technologies.

    4. Runs security and Google Cloud infrastructure. Keeps the app protected and the platform humming, so the engine that checks millions of addresses stays fast, safe, and reliable.

      here is his description frok linked in, maybe something better you can peopose?:About 🚀 Cloud Architect | DevOps & Platform Engineer | Product-Focused | Problem Solver

      Since 2017, I’ve been designing, securing, and scaling cloud-native infrastructure for high-impact environments—serving millions of users across global markets.

      With hands-on experience across GCP, AWS, Kubernetes, and Terraform, I specialize in building robust, scalable platforms using GitOps and modern DevSecOps practices. My work consistently balances developer experience, security, and compliance, especially for organizations with high regulatory demands like FinTech.

      🔧 Recent Wins:

      💰 Reduced cloud infrastructure costs by over 30% through deep optimization

      🎯 Implemented strategies that led to my company’s first profitable quarter

      ⚡ Boosted CI/CD performance by 25% while meeting strict security audit requirements

      🌍 Managed infra supporting 60M+ users in 60+ countries

      🚀 Led cloud migration and built scalable, self-healing systems from the ground up

      I’m passionate about Open Source, love solving complex challenges, and thrive in collaborative, diverse environments. Open to remote/hybrid opportunities—currently based in Amsterdam.

      Let’s build what’s next.

    1. Client lists now reviewed before the first send 0 of 12 → 12 of 12

      this clashes with the sent3nce thag this agency was cleaning each list. need better sent3nce. maybe something along the lines of "the result gave them even more strategoes to fix or things outsode the list itself that needed to be abalyzed and fixed

    2. If your authentication is broken, no list cleaning will save you. Start here.

      replace this with something thst wxplains what is below. based on rwlesult of free check they do themselves they can maybe see really ovious checks. if they still dont know if they need it, lsos page link or talk to yt

    1. Profile photo (optional)Used for your contributor card. If you don't add one, we use a letter icon.

      i sent myself a photo got the email from the response but couldnt open file. if we csnt fix this todsy due to credits, we should just remove this photo for now.

    1. 15 questions

      we write the number of quedtion to read here is 15 ( same for other blovks here. they dont go to the actually currated reads. we had done the magoc math of which articles to bunch together. we dont have a lot of token left. we have 8% left until sundsy so maybe we hide this sectioj if it takes too much to rebuild the pages under this with links to content without duplicating it but still makimg it eady to see all 15 questions to read with next next or sokething clever so we dont have duplicated content.

    1. Copying this almanac isn't permitted. Contributing to it is welcomed and rewarded.We credit the experts who help us improve answers, we link back to their work, and we put their name in front of our readers. We work with people, not around them.Ask, correct, or contribute →

      this is just for /emailalmanac pages and under that. nowhere else

    2. month. R

      The form box is broken again etc: we had added two check boxes maybe you find the form design somewhere so it looks the same with the correct text and checkbox intelligence where the newsletter checkbox needs to be checked but the open rate one doesn't in order to submit the formSeems to be an issue other pages wherever there's the newsletter box

    3. Yanna-Torry Aspraki Litmus Coach 2020·Ask a Deliverability Expert·8,000+ lists reviewed·Lenovo Twinning Finalist

      We need to add all four contests that we want Litmus Coach Award 2020 MARsum Top 100 Marketing & Advertising Leaders 2021 Marketing 2.0 Best Business Award 2022 Lenovo Twinning Finalist 2026 Ask a Deliverability Expert·8,000+ lists reviewed

      Put them in whatever order makes more sense, unless we purposofully decided to show this only.