IMAP4 Keywords are small bits of metadata that can be attached to stored email messages.
They're free-form text, but the convention is that
\ indicates a system keyword$ indicates a keyword with a common meaningSee the IMAP4 spec and the IANA registry
| { | |
| "@context": "https://schema.org", | |
| "@type": "ClaimReview", | |
| "claimReviewed": "The Thames is considered one of the cleanest rivers in the world.", | |
| "reviewBody": "This sounds like bollocks, mate", | |
| "itemReviewed": { | |
| "@type": "Claim", | |
| "author": { | |
| "@type": "Person", | |
| "name": "Lucy Williamson" |
| require["mime","fileinto"]; | |
| ## IANA registered type is "text/calendar", but some sources use "application/ics" | |
| if header :mime :anychild :subtype "Content-Type" ["calendar","ics"] { | |
| fileinto "calendar"; | |
| } |
I have a site where there is no legitmate use of the HTTP POST method (or anything other than GET/HEAD).
limit_except is usually used for method restriction, but only produces 403 responses, not 405.
There's a Stack Overflow
question that notes this.
There's a 2015 blog post
that suggests something like the following (which I needed to modify to get the Allow: header to appear):
server {
I have a process that outputs a list of .in-addr.arpa values. These consist of names with 3 to 6 labels.
161.187.42.143.in-addr.arpa
18.139.243.162.in-addr.arpa
38.51.19.58.in-addr.arpa
136.67.34.in-addr.arpa
16.134.243.162.in-addr.arpa
18.240.203.159.in-addr.arpa
240.54.in-addr.arpa
| #cloud-config | |
| ## I want to authenticate sudo via ssh-agent on Ubuntu 22.04 | |
| users: | |
| - name: bob | |
| gecos: Bob | |
| shell: /bin/bash | |
| primary_group: bob | |
| groups: sudo |
Software on Apple platforms that makes use of the File Provider API
| Software | Platform | Used | Notes |
|---|---|---|---|
| Dropbox | macOS, iOS | yes | help |
| OneDrive | macOS | yes | |
| Google Drive | macOS | yes | help |
| NextCloud | macOS | no | in development |
I quite commonly see undelivered mail to [email protected] on the outgoing mail queue. (DSNs and out-of-office replies with empty senders - so not critical mail.)
(The Twitter mail is recieved by en25.com/eloqua.net which is infrastructure for "Oracle Eloqua Marketing Cloud".)
This isn’t a new issue, but I thought I’d drop a note in public about it.
If I run exim4 -v -M on a delivery attempt I can see that it disconnects immediately after attempting to establish a STARTTLS session, so falls back to retrying without TLS.
SMTP<< 220 P01SNJ018.eloqua.net Microsoft ESMTP MAIL Service, Version: 10.0.14393.4169 ready at Tue, 10 Jan 2023 05:50:33 -0500
One annoyance of running a publically-accessible WordPress site is the bots that attempt to rapidly try thousands of login attempts via /wp-login.php.
Even if none of the guesses are ever likely to work, the site will waste resources running PHP and SQL to confirm that to be the case.
A barrier to these drive-by hack attempts can be added using nginx's http_limit_req, where rate limiting is applied only to POST requests for the login page, not affecting the rest of the site.
In /etc/nginx/conf.d/login-limit.conf we create the zone LOGINLIMIT.
1m is the size of the shared memory zone for tracking requests, and 15r/m limits to 15 requests per minute (ie 1 every 4 seconds).
| #!/usr/bin/env ruby | |
| # Remote mastodon accounts can be refreshed with the command | |
| # tootctl accounts refresh --all | |
| # https://docs.joinmastodon.org/admin/tootctl/#accounts-refresh | |
| # however, tootctl was having issues, so I ended up writing a this | |
| # helper script to scan a mastodon cache for missing avatar/header images | |
| # prioritising recently active accounts, and download directly | |
| # |