• 0 Posts
  • 28 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle


  • I’m not OP, but I recently rewrapped my cat trees and used a staple gun to tack it down. Close to the base, I wrapped the tail vertically a little upwards on the pole, stapled it to secure, then ran it down to the base and started winding over the tail. This causes some bumps in the snaked look, but isn’t too bad from a distance. Plenty of staples keep it in place up the pole in case the cats cut through it from sharpening. It's still holding up so far










  • Adding on to a bit from your comment that I missed, it’s not affecting the car itself. The article should have used the word “phone” instead of “device”.
    All Android Auto is a screen for your phone that also hooks into car buttons. Your phone does all the hard work with projecting data to the screen. If your phone is too old, Android Auto might not work because apps don’t work properly with the base framework by Google.
    You can use a new phone on an older car that officially supports Auto/CarPlay. That’s never been a problem.


  • If you don’t update Android Auto, maybe. Apps still rely on the framework that makes it work, so you are likely to have those break if they use features that Android Auto didn’t have at the update freeze.

    The version they’re cutting off is really old, relatively speaking. You have to be on Oreo or later (8.0+), which came out in 2017.
    Many apps you would use Android Auto will likely bump up to this break point soon. Waze, for example, is 7.0+. You’re bound to run into issues being on Nougat or earlier soon, if not already.




  • Short answer, likely yes. It’s not definitive, you could still slip by after sending enough mail, but you are also very likely to get whacked because that VPS IP doesn’t have an email sending reputation.

    Longer answer, email gateways like Google, Microsoft, and Proofpoint don’t really care who owns what IP. Well, they might, but they’re more concerned about the sending habits of an IP. While you might send good mail from that IP, there’s no reputation for it, so you could be whacked for having a neutral reputation (the ol’ credit score dilemma but for email).
    In order to have a good reputation, you have to send a large volume of messages very gradually over several weeks to “warm” your IP as a reputable sender. I went over this slightly more in detail in another reply, but this article is pretty concise on how an enterprise accomplishes this with a dedicated IP at a provider like SendGrid: https://docs.sendgrid.com/ui/sending-email/warming-up-an-ip-address


  • It’s about sample size. Mail gateways won’t designate an IP as a reputable sending IP until it assesses a large volume of mail sent over a long period of time. You can’t send the quantity it wants all at once or even in a short window because then you’ll be designated as a spammer. So you start small with a few a day and gradually ramp up sending over multiple weeks or months to eventually send several thousands of messages in that period.

    Spammers and malicious actors too often spin up new IPs for sending mail, so gateway patterns already implicitly mandate that email should come from IPs it’s already judged reputable.

    You as an individual can’t reasonably warm your own IP. This is why services like Amazon SES or Sendgrid exist because they have huge IP pools that are ready to go. Plus, those services are very concerned with reputation and have bounce/complaint metrics defined to warn customers that abuse or poorly configure their sending habits.

    This next example is what I’m most familiar with, but I’m sure there are other services like this. If you’re a big enterprise and want your own dedicated sending IP because you’re concerned about using a shared pool, you could use something like Amazon Pinpoint which allocate IPs for your org to use in SES, but they have to be warmed before you switch your production workloads over to it full-time. It automates some of the gradual-ness of warming so you use a mix of SES plus your Pinpoint IPs to keep mail flowing for your product.

    It looks like Sendgrid also does dedicated IP warming guard rails too. This article is pretty decent for understanding how it works - https://docs.sendgrid.com/ui/sending-email/warming-up-an-ip-address The per-day warming limits give you an idea of what scale this kind of process is used for.


  • Definitely listen to this. IP Warming is a very real problem and you have to send thousands of messages at a very gradual rate for most email gateways to 1) mark you as a proper email sender, and 2) classify you as a reputable one that isn’t sending spam. Using a public/private cloud IP isn’t enough, it should be a service already used for mail sending.

    If you self host sending email and ignore using a service for outbound, make sure it isn’t at home. ISPs often block SMTP traffic to keep people from spamming others from their home. A lot of IP blocklists also auto block home IPs so you may not ever get your messages delivered.

    Make sure to set up SPF/DKIM/DMARC. At the very least SPF, DKIM if the platform supports it, and ideally all three or SPF+DMARC. It’s not that hard to configure if you do it as you go instead of years down the line after you have a dozen services sending mail as your domain.