Tag

Tag: Security

TLS, certificates, authentication, vulnerabilities and the privacy work behind them.

Showing 11 to 12 of 12 · Page 2 of 2

Software Upgrades July 31, 2007

Greylisting: The Next Step in the Spam Control War

Why Revion added greylisting to every mail server, how temporarily rejecting unknown senders stops most spam, and what it means for legitimate mail.

Read article

Software Upgrades January 14, 2007

SmarterMail 4.x upgrade!

Revion upgraded every mail server to SmarterMail 4.x in February 2007, adding antivirus protection and the spam controls earlier releases lacked.

Read article

We value your privacy

We use cookies to run this site, remember your preferences, and understand how visitors use Revion. You can accept all, reject non-essential cookies, or choose which categories to allow. See our Privacy Policy.

We use cookies to run this site, remember your preferences, and understand how visitors use Revion. Accept all, reject non-essential cookies, or choose which categories to allow. See our Privacy Policy.

Customize Consent Preferences

Choose what this site is allowed to load. Essential is always on, because without it we cannot remember what you decide here. The rest stay off until you turn them on, and you can come back and change them whenever you like from our Privacy Policy or Cookie Policy page.

Always on

Needed for the site to work and to remember the choice you make here. It also covers the booking calendar, which is the whole of our meeting request page and so loads for everyone. Nothing in this category identifies you or follows you between visits, and it cannot be switched off.

reCAPTCHA v3

Google. Requested only when you submit a form. Sets nothing before that.

The contact and quote forms are checked by reCAPTCHA v3 so that the inbox stays usable. It is fetched from Google at the moment you press the send button and at no other time. Read a page and leave without submitting a form and your browser never contacts Google at all, and no reCAPTCHA cookie is set, which is why it is not in the table below.
Cal.com booking calendar

Cal.com. On /meeting-request/ only. Loaded for every visitor, before and regardless of any answer to this banner.

The booking calendar. Our meeting request page exists to book a meeting and does nothing else, so a calendar that waited for your permission would leave that page with nothing on it. It is treated as strictly necessary to that one page for that reason, the same as reCAPTCHA above, and it loads as soon as the page does. It is on no other page. Cal.com loads it in a frame of its own, and that frame is Cal.com's page rather than ours, so it carries Cal.com's own suppliers. We measured exactly one: Sentry, which Cal.com uses to collect its own error reports. Sentry stores nothing on your device, which is why it has no row below. No advertising company, no social network and no analytics product is contacted, and no Google host is contacted at all. The four cookies the calendar does set are listed below, and if you would rather not load it, the page carries the booking link, our telephone number and our email address in plain text underneath it.

Essential cookies
Cookie	Duration	What it does, and who sets it
revion_consent	12 months	Set by revion.com. Remembers which categories you allowed here, and which version of this notice you were shown, so that we do not ask again until it changes. It holds a setting and nothing else: no visitor identifier, and nothing that follows you between visits.
__cf_bm	30 minutes	Set by Cloudflare, inside the Cal.com booking calendar, on the cal.com domain. Tells automated traffic apart from real visitors so that the calendar stays available to people. It reads how the request was made, not who made it. Measured at 29 to 30 minutes.
__Secure-next-auth.callback-url	Until you close your browser	Set by Cal.com, on the cal.com domain. Part of the sign-in machinery of Cal.com's own application, which the calendar page is built on. You are not signing in to anything, and it holds no account of yours. It is deleted when you close your browser.
__Secure-next-auth.csrf-token	Until you close your browser	Set by Cal.com, on the cal.com domain. A one-visit token that lets Cal.com tell a form you submitted apart from one another site submitted on your behalf. It is deleted when you close your browser.
uid	Until you close your browser	Set by Cal.com, on the app.cal.com domain, and only once you pick a time slot: opening the page does not write it. It holds the slot Cal.com has put on hold for you while you fill the booking form in, so that two people cannot be given the same time. It is deleted when you close your browser.

Loads Google Analytics 4, so we can see which pages are read and which are not, and fix the ones nobody finds. Off by default, and while it is off this site loads no analytics tag at all, so there is nothing for it to send.

Google Analytics 4

Google. Loaded only once you allow it. The cookies it writes are listed below.

Counts page views, and records which site or search sent you here, so we know which pages earn their place. It is a plain gate rather than a consent signal: while this category is off the tag is not requested, no measurement cookie is written, and nothing about your visit reaches Google from this site in any form. Turn it back off later and the tag is taken out of the page and both cookies are deleted.

Analytics cookies
Cookie	Duration	What it does, and who sets it
_ga	400 days	Set by Google Analytics, on the revion.com domain. Tells one visitor apart from another so that visits can be counted without identifying anyone. Two page views from the same browser count as one visitor rather than two. Written only after you allow this category.
_ga_T94F03YGES	400 days	Set by Google Analytics, on the revion.com domain. Keeps track of the visit you are in the middle of, for our own measurement property: the letters on the end are that property, and no other site shares it. Written only after you allow this category.