Someday I will learn to proof-read emails composed on my phone before pressing the send button. Sadly, today is not that day.
On Thu, Mar 12, 2020, 13:20 Russell Senior <[email protected]> wrote: > The other think it would add is to not trust any information that you get > from the suspicious messages, e.g. there email address to reply to. Look > that up independently. Also, you could start the conversation with them by > generally describing the email, and let them ask for the exact copy. > > On Thu, Mar 12, 2020, 13:16 Richard Owlett <[email protected]> wrote: > >> On 03/12/2020 02:52 PM, Paul Heinlein wrote: >> > On Thu, 12 Mar 2020, Richard Owlett wrote: >> > >> >> I'm getting strange emails PURPORTEDLY from my email service provider. >> >> I've dealt with them (or predecessor) for >3 decades. >> >> The textual content raises many red flags. >> >> a. the emails did *NOT* include local telephone number >> >> b. today's email had a *BLANK* subject line >> >> c. the attachment to one email was an *.EXE* file >> >> *BUT* I'm a Linux user >> >> >> >> I notified them by telephone that I *suspected a problem* >> >> >> how>> How do I safely *FOR THEM & MYSELF* forward suspicious emails? >> > >> > Most e-mail clients will allow you to save to disk the entirety of an >> > e-mail message, headers and body both included. >> >> That is what I wanted. >> >> > >> > I suggest you save it to disk, then gzip or xz it, and send it as an >> > attachment to your provider. >> >> HOW? >> >> I use SeaMonkey version 2.49.4 under Linux (IE. Debian 9.) >> >> Am I askinging the RIGHT questions? >> >> >> >> _______________________________________________ >> PLUG mailing list >> [email protected] >> http://lists.pdxlinux.org/mailman/listinfo/plug >> > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
