I actually find it interesting how much it reveals about the target e-mail and account configuration
We know he's running VMS We know he has a disk called $DISK3: We know his user space is under $DISK3:[MARK] And we know we've successfully filled his disk, thus denying some level of service and system functionality In this era of hackers that feed off this sort of exposed data, I doubt any modern mail server would be game to post back so much configuration-specific information that could be used to aid in a targeted hacking attack. Cheers Jason A -----Original Message----- From: Simh [mailto:[email protected]] On Behalf Of Alan Frisbie Sent: Friday, 7 August 2015 7:33 PM To: [email protected] Subject: [Simh] Mark's mailbox full If anyone know how to get in touch with Mark Pizzolato outside of email, please let him know that he has a disk allocation failure: > This is a report on the delivery status of your message. > > Message-ID: <[email protected]> > Subject: Re: [Simh] Problem with default builds > > --Failed delivery to: > Address: MARK+SIMH > Status: error writing !AS > > Reporting-MTA: dns;infocomm.com > Arrival-Date: Fri, 7 Aug 2015 15:25:38 -0700 > > Final-Recipient: x-local;MARK+SIMH > Action: failed > Status: 5.2.0 (Other or undefined mailbox status) > Diagnostic-Code: x-local;error writing !AS %MAIL-W-WRITEERR, error > writing $DISK3:[MARK.MAIL]MAIL.MAI -RMS-F-FUL, device full > (insufficient space for allocation) > Last-Attempt-Date: Fri, 7 Aug 2015 15:25:40 -0700 Thanks, Alan Frisbie _______________________________________________ Simh mailing list [email protected] http://mailman.trailing-edge.com/mailman/listinfo/simh _______________________________________________ Simh mailing list [email protected] http://mailman.trailing-edge.com/mailman/listinfo/simh
