• 0 Posts
  • 14 Comments
Joined 4 months ago
cake
Cake day: June 3rd, 2025

help-circle

  • OP, what bluGill said is exactly your problem (assuming your DMARC and friends are setup correctly).

    The concept is referred to as “email (or domain) reputation”. The implementation details are closely guarded secrets, unique for each email receiver.

    One of the metrics for establishing a positive email reputation the “How much email does your mail server sends?” : the more the better**

    If you’re a large company, it’s fine… but if it’s just a personal domain with < 20 per week, you’re not going to establish a reputation and (depending on the receiver) you’re email might just get dropped.

    The other (frequent) metric is: “Of the emails that are sent, how many are read, and how many are flagged as spam?” In order, for these crowd sourced spam filters to work, they need you to send large amounts of email. Receivers like Gmail/Google are pretty forgiving. However, Outlook/Microsoft are very aggressive, meaning if enough outlook users flag your email as Spam, then future emails sent to outlook from your domain will probably automatically be marked as spam. Obviously, these are all black boxes, so I can only offer my personal observations (take it worth a grain of salt).

    As bluGill mentioned, there is a solution, but it involves moving your custom domain to a larger (re: paid) email provider. If you were to move to Google (for example), it doesn’t matter if your custom domain sends 5 emails per week. Those 5 emails are being sent from Google mail servers (using your custom domain) , which means they’re gaining the “reputation” of google and you can be certain that your emails will arrive, even if it’s (non-obvious) spam. Because, the email receiver assumes that Google will shut you down, if you’re a spammer.

    It’s a sad state that one of the original “pillars of the internet” (email) has degraded to feed only the big tech companies… but unfortunately this has been the case for many years.




  • Actually, those steps are the ones necessary to recover from a hard brick (re: the device is unusable because you did something you shouldn’t have as root).

    The actual process to root the device is simply running a few adb commands (so a prereq is having Developer Mode enabled).

    Once you have ran the exploit, your root escalation is temporary until the device is rebooted or you take additional steps to persists your root privileges (thus, potentially leading you towards a hard brick).

    source: The docs



  • It could be the quality of your headphones.

    I’m not an audiophile, but back-in-the-day I bought some analog “sennheiser studio monitors” as opposed to “just headphones”.

    I actually returned the first one and exchanged them, because when I listened to a live recorded CD, I kept hearing loud “pops” that I didn’t hear with my “regular headphones”. I assumed they were defective.

    The exchanged sennheiser had the same “pop” in this CD. It turns out, most “regular headphones” didn’t have the same depth in sound frequency as studio monitors and the “pops” were accidental artifacts that were mixed into the CD.

    For other CD’s, I’d hear telephones ringing and sirens in the background.

    Eventually, I got use to it. Then after a few years, I replaced my CD collection with mp3’s… and I could tell a different in songs/albums I was really familiar with. The base wasn’t as deep, the high sounds weren’t as high, I didn’t hear telephones ringing in the background.

    I had the same sennheiser, it was just that the nature of mp3’s “flattened” the music.

    Now, with Bluetooth and the disappearance of 3.5 mm jacks, there are too many layers of digital conversion happening. I’ve given up… and now just have some cheap ear buds I listen to.