There are different things at play here.
First, Scrum is not the same as SAFe and neither are the same as Agile. Agile Software Development is a set of values and principles. Scrum is a lightweight process framework that is defined in the Scrum Guide and contains a number of roles, events, and artifacts. Scaled Agile Framework (SAFe) is an enterprise-level framework that may or may not be helpful in helping an enterprise embrace agility.
What this means is that a practice that helps promote agility may or may not be in line with the rules of Scrum or SAFe.
Is sending a status email at the end of the day agile? I'm not sure. Maybe, maybe not. One of the principles of Agile Software Development is that "the most efficient and effective method of conveying information to and within a development team is face-to-face conversation". If there's no face-to-face (or, in today's world, 20 years after the Manifesto for Agile Software Development was written, high fidelity voice and video communication), I'm not sure you can be Agile. However, there's insufficient information to outright say that you aren't Agile.
Is sending a status email at the end of the day consistent with Scrum? Absolutely not. Scrum is defined in the Scrum Guide and is immutable. That means if you are not following the rules that are specified, you may be doing something that works for you, but the result is not Scrum. One of the key Scrum events is a daily planning and coordination meeting called the Daily Scrum. If the Development Team does not get together for up to 15 minutes for the purposes of planning their day, it's not Scrum.
Is sending a status email once a day consistent with SAFe? Again, I'd say no. At the team level, SAFe calls for the Daily Stand-Up (DSU). It's a gathering of the full team at the same time and the same place every day. Since you're not doing that, I'd be hesitant to call what you're doing SAFe.
If your team is so distributed, I'd question how effective they are as a team. They may be more like individuals working on a common project. In such a case, perhaps Scrum and SAFe aren't appropriate for your needs. Most frameworks are built around either co-located teams or at least teams that have not-insignificant overlap in their working hours to support frequent, real-time communication.