Contacting Anton McClure
Contacting Anton McClure
The University of Akron e-mail addresses are not going to be permanent. As per current (October 2024) IT policies. The uakron address will go away when I'm no longer an active student. The zips.uakron address will get deleted, possibly without warning, as with the rest of the zips.uakron accounts following Google's policy changes. The adm_asm135 (administrator) account will be deactivated if I'm ever no longer working IT services at the University of Akron, and the sa_asm135 (student assistant) account when I'm no longer a student assistant. The 1870.uakron address will go away automatically if I do not log in to it every two years as either a non-emeritus retiree or an alumnus. Hence I do not recommend using it since I do not know how many times I will need to ask IT to recreate the mailbox, nor do I know if it will change again in the future.
Here are the addresses I would strongly suggest you use: Some other currently valid addresses I have which forward their mail to aperture are:
If you are contacting me due to an issue on a URL that does not begin with http(s)://www.aperture.presumed.net/~anton/ but it is from another user or page on aperture or presumed.net, you will want to contact that user instead. If it is not a user page, or not on either aperture or presumed.net, you will want to contact the webmaster, typically using e-mail messages. The webmaster e-mail addresses are typically going to be in a format such as webmaster@hostname.example.edu. Here, it is webmaster@aperture.presumed.net.
If you wish to send me a confidential message, you do not want to use e-mail, phone calls, or any other digital form for that matter. Digital communications are never truly going to be private, and multiple third-parties can always access the messages. End-to-end encryption is also worthless when there are backdoors into those encryption mechanisms.
If you are from the University of Akron, use your uakron, zips.uakron, or 1870.uakron e-mail address, unless we have already spoken enough times, and you've shared your personal or other professional e-mail address with me in person.
The most likely ones are that I either did respond but your system bounced due to a misconfigured spam filter, I did not consider a response to be necessary, or I just had not gotten around to sending a reply yet. If I have a way to contact you, I will let you know that the e-mail bounced probably quickly. Either of our Message Transfer Agents (MTAs) may have blocked the message for a number of reasons. If you are a friend, and you tried e-mailing me multiple times, it may be an issue with one of our MTAs. Checking the mail log files in /var/log/ should give sufficient information on what is going wrong in most cases.
Your e-mail messages should be sent either in English or with an English translation provided, written to the best of your ability. If I cannot read or understand your e-mail, I will not reply. While I do know people who can translate languages such as Spanish, German, Italian, French, Japanese, and Portuguese, among others, using this option will not be ideal for communications that involve sensitive information. Naturally, perse will understand what you wrote.
If you administer your own MTA, ensure that your machine can both send messages to and receive messages from my e-mail smarthost's IP addresses 135.148.100.14 or 2604:2dc0:100:380e:: (coco.presumed.net), rather than this machine itself. If someone else administers your e-mails for you, ask that person to ensure messages can be sent and received. This may resolve most issues that would be on your end. If that someone else who administers your e-mails is completely unknown, and they are just nameless employees to a massive e-mail service, such a Google's Gmail, Microsoft's Hotmail/Outlook, Yahoo!'s e-mail, or another similar service, God help you. There is also the chance that I did receive your e-mail, was able to read it, and I was able to reply, but I just chose not to do so. Keep in mind that nobody is required to reply to every message they get.
Better yet: if your ISP or mailing service provider blocks this machine's IP or domain, consider asking your ISP to stop blocking us on your account. To quote John Gilmore, a co-founder of the Electronic Frontier Foundation and the source I cribbed this section from, "Don't just let them put in an exception for mail from me. Get them to take off the blacklist on your incoming mail. It is usually hard -- but worth it. Who else's emails are you missing? Some of us figured out in the 1950s that blacklists were a bad idea."
The PGP ASCII-armored key is below: