Read next

Jump to

1. Main content
2. Search
3. Account
4. Jump to top of page

Read next

Read next

Read next

The article Google’s AI Features Sent One Site An Estimated 21% Of Its Clicks appeared archetypal on Search Engine Journal.

Read next

Comparing vLLM vs. Ollama, the key difference between them is what all tool prioritizes: vLLM focuses on serving models to apps and controlling how requests use GPU resources, during Ollama makes it easier to download, switch, and run models locally.

We ran vLLM and Ollama on matching NVIDIA L40S GPU instances using the identical ample tongue example (LLM), Qwen2.5-Coder-7B-Instruct, at 16-bit floating-point (FP16) precision.

At eight simultaneous requests, vLLM produced complete 34 times as much output per second, during its median delay for the archetypal content was complete 770 times shorter.

How do vLLM and Ollama work?

vLLM plant through a shared conclusion motor that coordinates requests and GPU resources, during Ollama simplifies example management through a server that loads models and manages their runners for you.

vLLM’s scheduler and recollection components decide which requests run together and how GPU recollection is used. Ollama’s server starts or reuses a example runner as needed and keeps models loaded whenever recollection allows.

How does vLLM assist models?

vLLM serves models by receiving requests through an API, deciding which ones to process, and returning generated tokens to your app. Its scheduler decides which requests run together according to the accessible GPU recollection and handling capacity.

To create a new token, the example needs data it calculated from the tokens that came before it. vLLM keeps this data in the key-value cache (KV cache), so the example doesn’t have to compute it again for all new token.

PagedAttention, vLLM’s method for organizing the KV cache, splits that recollection into small, fixed-size blocks.

vLLM gives all petition additional blocks as it grows and frees them whenever the petition finishes. The blocks don’t have to sit next to all another in GPU memory, which helps decrease wasted space.

vLLM additionally uses uninterrupted batching to keep requests moving through the model. The scheduler checks the requests following all circular of token generation.

It afterward adds waiting requests as capability becomes accessible alternatively of waiting for all petition in the first collection to finish.

How does Ollama run models?

Ollama runs a example by loading it into recollection and passing all petition to a example runner. The runner is the procedure that performs the model’s calculations on the CPU, GPU, or both.

Both the ollama run command and the Ollama API dispatch requests to the identical server. The server checks which example you request, reuses its runner if the example is already loaded, or starts one if needed.

Ollama uses a llama.cpp-based runner for GPT-Generated Unified Format (GGUF) models. It additionally supports a runner according to MLX, Apple’s device learning framework, for compatible models on Apple Silicon.

A Modelfile lets you preserve how you desire Ollama to run a model. You can choose the basis model, set default parameters, add a scheme prompt, and define the immediate template without changing the first example weights.

Ollama additionally handles multiple requests in parallel. The OLLAMA_NUM_PARALLEL environment controls how many requests one example processes at the identical time, during additional requests delay in a queue. Processing additional requests in parallel uses additional memory.

How do vLLM and Ollama difference in a achievement benchmark?

vLLM delivered higher output throughput and shorter waits until the archetypal content appeared than Ollama at all concurrency flat we tested. The achievement gap widened as additional requests ran at the identical time.

At eight concurrent requests, vLLM delivered 34.22 times Ollama’s output throughput, alongside 371.63 tokens/s vs. 10.86 tokens/s.

At the identical concurrency level, the median delay until the archetypal content appeared was 0.19 seconds alongside vLLM, compared alongside 143.6 seconds alongside Ollama.

Both vLLM and Ollama completed all measured petition without a recorded failure.

How was the benchmark set up?

We benchmarked vLLM and Ollama on two matching Hostinger GPU hosting instances, alongside one motor operating on all instance. This kept the hardware and functioning scheme accordant during we compared the two serving setups.

Both deployments ran Qwen2.5-Coder-7B-Instruct at FP16 alongside a 4,096-token environment limit. vLLM used Qwen/Qwen2.5-Coder-7B-Instruct from Hugging Face, during Ollama used qwen2.5-coder:7b-instruct-fp16.

We verified that the two deployments used the identical example name and precision, but not that the underlying example records were identical revisions.

Treat the benchmark as a difference of these two deployments fairly than a controlled difference of byte-identical example files.

We ran the identical Python benchmark client on all case and sent requests to its local API. Every immediate contained example Python code and asked the example to rewrite it alongside validation, category hints, and pytest tests.

Each reply streamed as it was generated and had a 256-token output limit. Both deployments used temperature=0, top_p=1, and seed=42. The benchmark didn’t automatically retry unsuccessful requests.

We tested one, four, and eight concurrent requests. At all concurrency level, the client processed 32 measured requests during keeping up to that many requests energetic at the identical time.

Each concurrency flat ran three times, giving us 96 measured requests per burden and 288 per engine. We changed the command for all repetition, using 1 → 4 → 8, 8 → 4 → 1, and 4 → 1 → 8, so the identical burden didn’t continually run archetypal or last.

Before all repetition, we sent three warmup requests to verify that all deployment was responding normally but excluded them from the measured results.

The benchmark didn’t measure example startup time, answer quality, or maximum server capacity. We additionally didn’t tune either motor to discover its finest imaginable performance.

How do vLLM and Ollama difference in throughput?

vLLM delivered higher total output throughput than Ollama at all tested concurrency level, ranging from 7.67 times Ollama’s throughput at one concurrent petition to 34.22 times at eight.

Throughput measures how many output tokens the server generates per second throughout all energetic requests. For an app serving multiple users at once, higher total throughput method the server produces additional content throughout those requests all second.

Each value is the median of the three throughput rates we measured at that concurrency level.

From one to four concurrent requests, vLLM’s throughput risen concerning 278%, from 49.79 to 188.18 tokens/s. It afterward risen another 97.5% whenever concurrency doubled from four to eight requests, reaching 371.63 tokens/s.

This method the tested vLLM deployment continued turning additional concurrent requests into substantially additional total output. Across the complete range from one to eight requests, its throughput risen 7.46 times.

Ollama followed a distinct pattern. Its throughput risen concerning 61.2% from one to four concurrent requests, from 6.49 to 10.46 tokens/s, but grew fair 3.8% whenever concurrency doubled from four to eight requests. Its general throughput risen lone 1.67 times.

This suggests the tested vLLM deployment had additional area to addition total output as concurrent petition grew. Ollama gained small additional throughput between four and eight requests in our test, notwithstanding handling twice as many requests at once.

Note that these figures measure total server output, not how quickly one idiosyncratic reply finishes.

How do vLLM and Ollama difference in latency?

vLLM’s median delay for the archetypal content stayed below 0.2 seconds throughout all tested concurrency levels, during Ollama’s risen from 1.6 seconds at one concurrent petition to 143.6 seconds at eight.

We measured the delay from sending a petition until the archetypal nonempty streamed content appeared. This includes API handling, server queueing, and immediate handling before generation starts.

For all motor and concurrency level, the median comes from 96 measured requests: 32 requests throughout three repetitions.

vLLM’s median delay risen from concerning 37 ms alongside one petition to 186 ms alongside eight, approximately a 5.1 times increase. In an interactive app, that motionless method users would see the archetypal content nearly immediately.

Ollama’s latency risen much additional sharply. The median delay rosy from 1.6 seconds alongside one petition to 51.4 seconds alongside four, afterward reached 143.6 seconds, or concerning 2 minutes and 24 seconds, alongside eight concurrent requests.

For person using an app, that changes the cognition from a noticeable postpone to waiting minutes before any reply appears.

Our measurements display how lengthy that postpone lasted, although they don’t disclose how much came from queueing, immediate processing, or another server-side factor.

How much VRAM do vLLM and Ollama use for the identical model?

For the identical Qwen2.5-Coder-7B-Instruct example at FP16 alongside a 4,096-token environment limit, our nvidia-smi snapshots showed 40.06 GiB allocated to vLLM and 14.20 GiB to Ollama.

VRAM stores the example weights and another data needed during handling requests. This includes the KV cache, which grows alongside longer contexts and additional simultaneous requests.

The vLLM snapshot showed concerning 2.8 times as much allocated VRAM as Ollama.

We launched vLLM alongside --gpu-memory-utilization 0.90, which allowed it to allocate up to 90% of GPU recollection for example implementation and the KV cache.

The 40.06 GiB snapshot hence doesn’t portray the minimum VRAM needed to run Qwen2.5-Coder-7B-Instruct alongside vLLM.

Your genuine GPU recollection requirements for Ollama or vLLM depend on the example size, precision or quantization, environment length, concurrency, and recollection settings.

How do GPU expenses difference between vLLM and Ollama?

At the 110-credit/hour charge shown for all Hostinger NVIDIA L40S case in our benchmark, vLLM’s estimated disbursal per myriad output tokens was 613.69 credits at one concurrent petition and 82.22 credits at eight. Ollama’s was 4,708.10 and 2,813.59 credits, respectively.

We calculated these estimates from the measured output throughput:

Cost per 1 myriad output tokens = 110 credits ÷ (output tokens/s × 3,600) × 1,000,000

The difference grew as additional requests ran at once. Ollama’s estimated disbursal per myriad output tokens was concerning 7.7 times vLLM’s at one concurrent petition and 34.2 times vLLM’s at eight.

At eight concurrent requests, one hr at the measured throughput would create concerning 1.34 myriad output tokens alongside vLLM, compared alongside concerning 39,100 alongside Ollama.

That method the identical hourly GPU expend produced substantially additional output alongside vLLM under the higher tested load.

These are modeled costs, not the genuine charges from our benchmark run. They assume all deployment maintains the measured throughput continuously for an hr and exclude setup, example downloads, troubleshooting, and idle time.

The estimates additionally use to our abbreviated coding workload, anywhere we capped responses at 256 output tokens. Your productive disbursal volition alter alongside the model, workload, concurrency, and how much of the paid GPU period you expend actively generating output.

Consider the two the hourly cost and the output you anticipate from that hardware whenever choosing a haze GPU provider for conclusion workloads.

Which hardware do vLLM and Ollama support?

vLLM and Ollama the two assistance CPU-only inference, NVIDIA and AMD GPUs, and Apple Silicon, but they differ in which processors and GPU generations they support.

Ollama supports older NVIDIA GPUs than vLLM. vLLM’s GPU facility guide requires compute capability 7.5 or newer, which covers GPUs specified as the T4 and RTX 20-series. Meanwhile, Ollama’s hardware assistance documentation lists assistance downward to compute capability 5.0.

Apple Silicon assistance additionally differs. Ollama supports M-series CPUs and Metal GPUs directly, during vLLM uses the distinct vLLM-Metal plugin for GPU acceleration.

When should you toggle from Ollama to vLLM?

Switch from Ollama to vLLM whenever expanding traffic leads to longer waits without a akin addition in throughput, or whenever you need to run the example throughout multiple GPUs or servers.

Our benchmark shows how that gap grows as additional requests run at the identical time. Between four and eight concurrent requests, Ollama’s throughput risen lone 3.8%, during its median delay for the archetypal content rosy from 51.4 to 143.6 seconds.

These results don’t set a worldwide switching point, though. Test your own example at the traffic you expect, and appearance for these signals:

• Users delay much longer for the archetypal content as additional requests arrive. Higher traffic is starting to power the cognition directly.
• Throughput barely increases whenever you add additional concurrent requests. The server is taking on additional activity without producing much additional output, so requests are mostly competing for the identical capacity.
• One GPU is no longer adequate for your example or workload. vLLM gives you additional authority complete operating the example throughout multiple GPUs or servers.
• Handling additional simultaneous requests matters additional than model-management convenience. At that point, vLLM’s concentration on serving many requests becomes additional helpful than Ollama’s simpler workflow.

You don’t need to toggle merely since your workload runs in production. Keep Ollama as lengthy as it meets your needs, and measure vLLM formerly serving additional users becomes the chief challenge.

How do you migrate from Ollama to vLLM?

Migrate from Ollama to vLLM by deploying a supported example alongside vLLM, pointing your app to its API, and checking that the prompts and features you depend on motionless activity as expected.

1. Deploy a example that vLLM supports. Check that vLLM supports your example origin and format fairly than assuming the identical Ollama example bundle volition transfer unchanged. Then deploy your LLM alongside vLLM on a GPU server from a provider akin Hostinger.
2. Point your app to the vLLM server. When your app already uses Ollama’s OpenAI-compatible API, you normally lone need to alter the basis URL and example name. For a local setup using the default ports, alter http://localhost:11434/v1 to http://localhost:8000/v1, afterward use the example name you configured in vLLM.
3. Recreate your Ollama settings. Settings in your Ollama Modelfile, specified as the scheme prompt, immediate template, and default reply settings, don’t automatically move to vLLM. Check streaming, tool calls, organized output, and any another API features your app uses.
4. Test before switching your app over. Send the prompts your app normally handles and test the figure of simultaneous requests you expect. Check the responses, streaming behavior, errors, tool calls, and organized output before directing genuine traffic to vLLM.

You’ll need additional than a URL alter whenever your app uses Ollama’s native /api/chat endpoint. vLLM uses the OpenAI-compatible /v1/chat/completions endpoint for chat, so you’ll additionally need to modify how your app sends requests and says responses.

Which should you choose, vLLM or Ollama?

Choose Ollama whenever your workload is mostly local or single-user, and choice vLLM whenever your app needs to grip many requests at the identical period or measure throughout multiple GPUs or servers.

The app itself doesn’t decide which motor you need. The identical RAG, chatbot, or coding workflow can lawsuit Ollama for one person and vLLM formerly requests regularly overlap.

Reproduce the difference alongside your own workload on matching hardware from a GPU provider if your use case falls between these examples.

Hostinger, for example, offers NVIDIA GPU instances including the L40S, A100, and B200, alongside 48 GB, 80 GB, and 192 GB of VRAM, respectively. Use the identical GPU configuration for the two engines during benchmarking so the hardware doesn’t skew the comparison.

The instances are billed hourly during they exist, including idle time. This lets you create matching instances for a abbreviated comparison, run your tests, and delete them whenever you’re done.

Hostinger additionally provides preconfigured templates for multiple apps, including Ollama. You can motionless nexus to an case complete SSH whenever you need to instal and configure application yourself, specified as vLLM.

Keep the model, precision, prompts, output limit, and hardware accordant during benchmarking, afterward test the figure of simultaneous requests you anticipate in practice.

Record output tokens per second, how lengthy users delay for the archetypal text, VRAM allocation, and hourly cost. Those measurements volition display whether Ollama’s simpler workflow is adequate or whether vLLM’s serving achievement is value the additional setup.

What are the alternatives to vLLM and Ollama?

Alternatives to vLLM and Ollama contain llama.cpp server and LM Studio for local example workflows, and SGLang and TensorRT-LLM for handling higher petition loads or scaling throughout multiple GPUs.

• llama.cpp server. Choose llama.cpp server for additional straightforward authority complete serving local GGUF models. Both Ollama and llama.cpp assistance CPU and GPU conclusion and provision OpenAI-compatible endpoints.
• LM Studio. Pick LM Studio for a graphical desktop workflow alternatively of a command-line-focused setup. It lets you download and oversee models, conversation locally, run offline, and disclose models through a local API.
• SGLang. Consider SGLang for apps that need to grip many requests efficiently. It can reuse activity whenever prompts portion the identical beginning, procedure waiting requests continuously, and measure throughout multiple GPUs.
• TensorRT-LLM. Choose TensorRT-LLM for an NVIDIA-focused deployment whenever you desire NVIDIA’s own tools for optimizing example inference. It supports setups ranging from one GPU to multiple GPUs and servers.

All of the tutorial satisfied on this website is topic to Hostinger's rigorous editorial standards and values.

Sorry

PixelOS is an AOSP based ROM, alongside Google apps included and all Pixel goodies. We aim to provision an cognition akin to Google Pixel phones alongside many achievement enhancements and a small amount of helpful additional features.

Get PixelOS

Conversation

Read next

The article Create More Helpful Content For AI Search With 9 Practical Workflows [Webinar] appeared archetypal on Search Engine Journal.

Dari Asisten Cerdas ke Tim AI

Channel ini menyajikan materi seputar Data Science & Artificial Intelligence, Networking & Cyber Security, serta Database & Programming. Seluruh materi disusun secara sistematis untuk membantu Anda memahami konsep, teknologi, dan praktik yang digunakan di bumi teknologi informasi, mulai dari tingkat alas hingga lanjutan. Setiap bahasan berfokus pada pengembangan keahlian melalui materi yang gampang dipahami, relevan dengan kebutuhan industri, dan disampaikan untuk tujuan edukasi. Seluruh konten mengedepankan implementasi teknologi secara legal, etis, dan bertanggung jawab, sehingga dapat menjadi rujukan belajar bagi pelajar, mahasiswa, maupun profesional. Jika Anda mau mengembangkan kapasitas di sektor pemrograman, pengelolaan data, kecerdasan buatan, jaringan komputer, maupun keamanan siber, channel ini menyediakan materi yang dapat membantu membangun fondasi ilmu sekaligus menaikkan keahlian secara bertahap. Playlist video terkait: ▪ https://www.youtube.com/playlist?list=PLZGgeqmsm32s ▪ https://www.youtube.com/playlist?list=PLZomBNpDl3vc ▪ https://www.youtube.com/playlist?list=PLE5VyXMZkzb8 PEMBAHASAN MATERI Playlist Materi Ilmu Komputer berisi kumpulan video pembelajaran, tutorial, klarifikasi konsep, studi kasus, demo, dan bahasan komplit seputar beragam sektor dalam ilmu komputer. Materi yang disajikan mencakup alas hingga tingkat lanjut, mulai dari pemrograman, pengelolaan database, jaringan komputer, keamanan siber, mekanisme operasi, pengembangan alat lunak, arsitektur komputer, hingga beragam teknologi yang digunakan dalam bumi komputasi modern. Temukan bahasan mengenai komputer dan pemrograman, algoritma, struktur data, PHP, JavaScript, Python, Laravel, MySQL, PostgreSQL, API, rekayasa alat lunak, database, jaringan komputer, pengelolaan server, cloud computing, virtualisasi, Linux, Windows Server, keamanan jaringan, cyber security, ethical hacking, kriptografi, keamanan aplikasi, DevOps, Internet of Things (IoT), kecerdasan buatan (AI), machine learning, serta beragam konsep, teknologi, dan praktik terbaik di sektor ilmu komputer. Playlist ini cocok bagi pelajar, mahasiswa, programmer, web developer, software engineer, pengelola sistem, ahli IT, maupun siapa saja yang mau mempelajari dan memperdalam wawasan di bumi ilmu komputer secara menyeluruh. CONTACT US ▪ Email support@mycoding.id ▪ WhatsApp https://wa.me/6281274309663 ▪ Telegram https://t.me/mycodingxd OFFICIAL LINKS ▪ Web https://mycoding.id ▪ Blog https://blog.mycoding.id ▪ News https://en.mycoding.id ▪ Apps https://play.google.com/store/apps/dev?id=5237501547073493079 SOCIAL MEDIA ▪ https://linkedin.com/company/mycodingxd ▪ https://facebook.com/mycodingxd ▪ https://instagram.com/mycodingxd ▪ https://tiktok.com/@mycodingxd ▪ https://twitter.com/mycoding_xd ▪ https://pinterest.com/mycoding_xd CHANNEL LINKS ▪ YouTube https://safelink.asia/youtube ▪ DailyMotion https://safelink.asia/dailymotion ▪ WhatsApp https://safelink.asia/whatsapp ▪ Telegram https://safelink.asia/telegram Powered by https://linkedin.com/company/401XDGroup #Networking #Programming #DataScience #CyberSecurity #ArtificialIntelligence #Database

403 Forbidden

sin1::x6mfz-1794207622724-f1589f99814d

Read next

Read next

English · 简体中文 · 日本語

News · Quick start · Models · Options

Flide is accelerated conclusion infrastructure for Jev-style decision models. With exact province forking it is up to 9.5 times faster than vLLM and SGLang, and all answer is the one the example gives the inquiry alone. It serves the Jev /v1/systemone API.

• 🔥 2026-11-09 We added Ainvest-Decision, Darwin-27B-RSI-Decision and KnowLine-31B-Gen1.5 in Flide 0.1.10, and the KnowLine family now says images.
• 🔥 2026-11-09 We added pplx-decider-v1.1-27b and JEV-35B in Flide 0.1.9, and /v1/systemone now takes multiple requests in one body.
• 🔥 2026-11-08 We added two decision example families in Flide 0.1.8, including AutoTrust and Clef, and additionally drex-max-v1.

• 🔥 2026-11-02 We released our document Flide: Accelerating Decision Inference alongside Exact State Forking on arXiv.
• 🔥 2026-10-29 We added three decision example families in Flide 0.1.7, including SynACK Decide, Wald and Xor, and Gemma 4 mixture-of-experts models specified as KnowLine-26B-A4B.
• 🔥 2026-10-29 We added two decision example families in Flide 0.1.6, including Drex and KnowLine, and flide verify checks exact forking on your own example and requests.
• 🔥 2026-10-28 We added six decision example families in Flide 0.1.5, including Jeffan, JevAny, Kev, Lychee, pplx-decider and StartLux, and images for Lumma and mammoth.
• 🔥 2026-10-26 We added five decision example families in Flide 0.1.4, including cerno, JADE, Linne, mammoth and Sieve, and additionally Quyet-1.0-Large.
• 🔥 2026-10-26 We added eight decision example families in Flide 0.1.3, including AJev, Bespoke-Nimble, Darwin, jiwo, Lumma, mogan, Quyet and Senova, and LoRA adapters now assist as they are.
• 🔥 2026-10-25 We added two decision example families in Flide 0.1.2, including Intern-Decision and torchcast, and a inquiry now takes up to 256 options.
• 🔥 2026-10-24 We released Flide 0.1.0 on PyPI, serving Qwen3.5 and Gemma 4 conversation models and the OneJev and Open-Jev decision models. Welcome to have a try.

uv venv -p 3.12 && source .venv/bin/activate uv pip instal flide torchvision flide assist --model OmniJev/OneJev1.6-0.8B

Any example in the model table starts the identical way, for example Perplexity's decision model.

flide assist --model perplexity-ai/pplx-decider-flash-v1.2

Every one of them answers this request.

curl http://localhost:8000/v1/systemone -H "Content-Type: application/json" -d '{  "state": "Order #1182 arrived alongside a cracked screen. The client asks for a refund and attached two photos.",  "questions": {  "action": {"type": "choice", "instructions": "What should assistance do next?",  "criteria": {"refund": "refund the order", "replace": "send a replacement", "escalate": "ask a human"}},  "urgent": {"type": "noul", "instructions": "Does this need a answer inside the hour?"}  } }'

See the docs for all model, images, the API and all options.

The final three columns say how much faster Flide answers one petition than the motor its publish ships, as the median latency complete the requests of all workload on one H200, anywhere DI is the Decision Index. The conversation models run against the faster of vLLM and SGLang, and OneJev against qev, the motor it used before Flide. KnowLine 35B runs alongside --quantize fp8, as its publish serves it in FP8. A value marked ~ is the average complete the sizes tested.

Apache-2.0. flide/kernels/gdn.py holds a kernel derived from two kernels of flash-linear-attention (MIT); THIRD_PARTY_NOTICES lists it with the another code Flide builds on.

If you use Flide in your research, delight citation our paper.

@article{li2026flide, title = {Flide: Accelerating Decision Inference alongside Exact State Forking}, author = {Li, Bobo and Song, Jiajia and Fei, Hao and Hsu, Wynne and Lee, Mong Li}, journal = {arXiv preprint arXiv:2610.42148}, year = {2026} }

Amelia v9.9.2 – Enterprise-Level Appointment Booking WordPress Plugin Free Download. Amelia is a Next-generation Appointment Booking WordPress plugin Built alongside the Newest Technology by an Award-winning Team. Amelia is your Automated Booking to create certain your Customers can create Appointments equal during you Sleep.

Main Features

• Responsive Design
• Search-like Booking Interface
• Categories
• Customize the Design
• Step by Step Booking
• PayPal and Stripe Payment Gateway
• Calendar
• Multiple Employees
• Multiple Services and Locations
• Scheduling
• and more

Download Amelia Enterprise-Level Appointment Booking WordPress Plugin

v9.9.2

v7.4.3

v6.2.3

Free download Amelia enterprise-level project booking WordPress plugin by tms-plugins on Codecanyon 22067497 premium project booking WP plugin download.

My Quines are sometimes specialized for Japanese. But to act RubyConf, I should compose "global" Quines.

v=0000;eval$s=%q~d=%!^Lcf<LK8, _@7gj*LJ=c5nM)Tp1g0%Xv.,S[<>YoP 4ZojjV)O>qIH1/n[|2yE[>:ieC "%.#% :::##" 97N-A&Kj_K_><wS5rtWk@*a+Y5 yH?b[F^e7C/56j|pmRe+:)B "##% ::##########" O98(Zh)'Iof*nm.,$C5Nyt= PPu01Avw^<IiQ=5$'D-y? "##: ###############" g6`YT+qLw9k^ch|K'),tc 6ygIL8xI#LNz3v}T=4W "# #. .####:#######" lL27FZ0ij)7TQCI)P7u }RT5-iJbbG5P-DHB<. " ##### # :############" R,YvZ_rnv6ky-G+4U' $*are@b4U351Q-ug5 " #######################" 00x8RR%`Om7VDp4M5 PFixrPvl&<p[]1IJ " ############:#### %#####" EGgDt8Lm#;bc4zS^ y]0`_PstfUxOC(q " .#############:##% .## ." /,}.YOIFj(k&q_V zcaAi?]^lCVYp!; " %% .################. #. " ;s="v=%04o;ev"% (;v=(v-($*+[45, ":####: :##############% : " ])[n=0].to_i;)% 360)+"al$s=%q#{ "%######. ######### " ;;"%c"%126+$s<< 126}";d.gsub!(/ "##########. #######% " |\s|".*"/,"");; require"zlib"|| "########### :######. " ;d=d.unpack"C*" d.map{|c|n=(n|| ":#########: .######: . " )*90+(c-2)%91}; e=["%x"%n].pack " :#######% :###### #: " &&"H*";e=Zlib:: Inflate.inflate( " ######% .####% :: " &&e).unpack("b*" )[0];22.times{|y| " ####% %### " ;w=(Math.sqrt(1-( (y*2.0-21)/22)**(; " .###: .#% " ;2))*23).floor;(w* 2-1).times{|x|u=(e+ " %## " )[y*z=360,z]*2;u=u[ 90*x/w+v+90,90/w];s[( " #. " ;y*80)+120-w+x]=(""<< 32<<".:%#")[4*u.count(( " . " ;"0"))/u.size]}};;puts\ s+";_ The Qlobe#{" "*18+ ( "# :#######" ;"Copyright(C).Yusuke End\ oh, 2010")}";exit~;_ The Qlobe Copyright(C).Yusuke Endoh, 2010 

This quine turns 45 degrees whenever executed; thus, it volition arrive about whenever executed eight times (see below). You can create it any-degree rotate by giving an entire figure as an command-line argument.

v=0416;eval$s=%q~d=%!^Lcf<LK8, _@7gj*LJ=c5nM)Tp1g0%Xv.,S[<>YoP 4ZojjV)O>qIH1/n[|2yE[>:ieC ".#####%.#% " 97N-A&Kj_K_><wS5rtWk@*a+Y5 yH?b[F^e7C/56j|pmRe+:)B " .#####%##% :" O98(Zh)'Iof*nm.,$C5Nyt= PPu01Avw^<IiQ=5$'D-y? " #####%###: #" g6`YT+qLw9k^ch|K'),tc 6ygIL8xI#LNz3v}T=4W " %######## #." lL27FZ0ij)7TQCI)P7u }RT5-iJbbG5P-DHB<. " :####### ###" R,YvZ_rnv6ky-G+4U' $*are@b4U351Q-ug5 " ###: : ####" 00x8RR%`Om7VDp4M5 PFixrPvl&<p[]1IJ " %#... #####" EGgDt8Lm#;bc4zS^ y]0`_PstfUxOC(q " %### .#####" /,}.YOIFj(k&q_V zcaAi?]^lCVYp!; " :. %% .#####" ;s="v=%04o;ev"% (;v=(v-($*+[45, " :####: :####" ])[n=0].to_i;)% 360)+"al$s=%q#{ " %######. " ;;"%c"%126+$s<< 126}";d.gsub!(/ " ##########. " |\s|".*"/,"");; require"zlib"|| " ########### " ;d=d.unpack"C*" d.map{|c|n=(n|| " :#########: " )*90+(c-2)%91}; e=["%x"%n].pack " :#######% " &&"H*";e=Zlib:: Inflate.inflate( " ######% " &&e).unpack("b*" )[0];22.times{|y| " ####% " ;w=(Math.sqrt(1-( (y*2.0-21)/22)**(; " .###: " ;2))*23).floor;(w* 2-1).times{|x|u=(e+ " %## " )[y*z=360,z]*2;u=u[ 90*x/w+v+90,90/w];s[( " #. " ;y*80)+120-w+x]=(""<< 32<<".:%#")[4*u.count(( " . " ;"0"))/u.size]}};;puts\ s+";_ The Qlobe#{" "*18+ ( " .##### :#" ;"Copyright(C).Yusuke End\ oh, 2010")}";exit~;_ The Qlobe Copyright(C).Yusuke Endoh, 2010 v=0341;eval$s=%q~d=%!^Lcf<LK8, _@7gj*LJ=c5nM)Tp1g0%Xv.,S[<>YoP 4ZojjV)O>qIH1/n[|2yE[>:ieC "#% .#####%." 97N-A&Kj_K_><wS5rtWk@*a+Y5 yH?b[F^e7C/56j|pmRe+:)B " : %#####%##. " O98(Zh)'Iof*nm.,$C5Nyt= PPu01Avw^<IiQ=5$'D-y? " #####%###: " g6`YT+qLw9k^ch|K'),tc 6ygIL8xI#LNz3v}T=4W " %######## " lL27FZ0ij)7TQCI)P7u }RT5-iJbbG5P-DHB<. " :####### " R,YvZ_rnv6ky-G+4U' $*are@b4U351Q-ug5 " :### : " 00x8RR%`Om7VDp4M5 PFixrPvl&<p[]1IJ " %#... " EGgDt8Lm#;bc4zS^ y]0`_PstfUxOC(q " .###: " /,}.YOIFj(k&q_V zcaAi?]^lCVYp!; " :. %% " ;s="v=%04o;ev"% (;v=(v-($*+[45, " :####: " ])[n=0].to_i;)% 360)+"al$s=%q#{ " %######. " ;;"%c"%126+$s<< 126}";d.gsub!(/ " ##########" |\s|".*"/,"");; require"zlib"|| "% ##########" ;d=d.unpack"C*" d.map{|c|n=(n|| " :#########" )*90+(c-2)%91}; e=["%x"%n].pack " ########" &&"H*";e=Zlib:: Inflate.inflate( "#. ######%" &&e).unpack("b*" )[0];22.times{|y| "## :####. " ;w=(Math.sqrt(1-( (y*2.0-21)/22)**(; "#. .###: " ;2))*23).floor;(w* 2-1).times{|x|u=(e+ "% . %## " )[y*z=360,z]*2;u=u[ 90*x/w+v+90,90/w];s[( " . #. " ;y*80)+120-w+x]=(""<< 32<<".:%#")[4*u.count(( " : " ;"0"))/u.size]}};;puts\ s+";_ The Qlobe#{" "*18+ ( "#. .##### " ;"Copyright(C).Yusuke End\ oh, 2010")}";exit~;_ The Qlobe Copyright(C).Yusuke Endoh, 2010 v=0264;eval$s=%q~d=%!^Lcf<LK8, _@7gj*LJ=c5nM)Tp1g0%Xv.,S[<>YoP 4ZojjV)O>qIH1/n[|2yE[>:ieC "####% .####" 97N-A&Kj_K_><wS5rtWk@*a+Y5 yH?b[F^e7C/56j|pmRe+:)B "##### : .#####" O98(Zh)'Iof*nm.,$C5Nyt= PPu01Avw^<IiQ=5$'D-y? "######. #####%" g6`YT+qLw9k^ch|K'),tc 6ygIL8xI#LNz3v}T=4W "####: . %######" lL27FZ0ij)7TQCI)P7u }RT5-iJbbG5P-DHB<. "#### . :######" R,YvZ_rnv6ky-G+4U' $*are@b4U351Q-ug5 "####% ###: " 00x8RR%`Om7VDp4M5 PFixrPvl&<p[]1IJ "### %#..." EGgDt8Lm#;bc4zS^ y]0`_PstfUxOC(q "## .. %###" /,}.YOIFj(k&q_V zcaAi?]^lCVYp!; ":#. . :" ;s="v=%04o;ev"% (;v=(v-($*+[45, ": : : " ])[n=0].to_i;)% 360)+"al$s=%q#{ "% %#: " ;;"%c"%126+$s<< 126}";d.gsub!(/ "#::#.: %#% " |\s|".*"/,"");; require"zlib"|| " : :#% " ;d=d.unpack"C*" d.map{|c|n=(n|| " :% : " )*90+(c-2)%91}; e=["%x"%n].pack " %###%% " &&"H*";e=Zlib:: Inflate.inflate( " ########. " &&e).unpack("b*" )[0];22.times{|y| " ########. " ;w=(Math.sqrt(1-( (y*2.0-21)/22)**(; " ##:%###. " ;2))*23).floor;(w* 2-1).times{|x|u=(e+ " %% . " )[y*z=360,z]*2;u=u[ 90*x/w+v+90,90/w];s[( " . " ;y*80)+120-w+x]=(""<< 32<<".:%#")[4*u.count(( " " ;"0"))/u.size]}};;puts\ s+";_ The Qlobe#{" "*18+ ( "####. .###" ;"Copyright(C).Yusuke End\ oh, 2010")}";exit~;_ The Qlobe Copyright(C).Yusuke Endoh, 2010 v=0207;eval$s=%q~d=%!^Lcf<LK8, _@7gj*LJ=c5nM)Tp1g0%Xv.,S[<>YoP 4ZojjV)O>qIH1/n[|2yE[>:ieC "#######% .#" 97N-A&Kj_K_><wS5rtWk@*a+Y5 yH?b[F^e7C/56j|pmRe+:)B "##########: : " O98(Zh)'Iof*nm.,$C5Nyt= PPu01Avw^<IiQ=5$'D-y? "#############. " g6`YT+qLw9k^ch|K'),tc 6ygIL8xI#LNz3v}T=4W "############: . " lL27FZ0ij)7TQCI)P7u }RT5-iJbbG5P-DHB<. "############# . " R,YvZ_rnv6ky-G+4U' $*are@b4U351Q-ug5 "############## " 00x8RR%`Om7VDp4M5 PFixrPvl&<p[]1IJ "# %######### " EGgDt8Lm#;bc4zS^ y]0`_PstfUxOC(q " %#: %##: : " /,}.YOIFj(k&q_V zcaAi?]^lCVYp!; " #. .:#. . " ;s="v=%04o;ev"% (;v=(v-($*+[45, " : : : : " ])[n=0].to_i;)% 360)+"al$s=%q#{ " :% %#: " ;;"%c"%126+$s<< 126}";d.gsub!(/ " #::#.: %#% " |\s|".*"/,"");; require"zlib"|| " : :#% " ;d=d.unpack"C*" d.map{|c|n=(n|| " :% : " )*90+(c-2)%91}; e=["%x"%n].pack " .###%# " &&"H*";e=Zlib:: Inflate.inflate( " ########. " &&e).unpack("b*" )[0];22.times{|y| " :######## " ;w=(Math.sqrt(1-( (y*2.0-21)/22)**(; " ##:%###. " ;2))*23).floor;(w* 2-1).times{|x|u=(e+ " %% . " )[y*z=360,z]*2;u=u[ 90*x/w+v+90,90/w];s[( " . " ;y*80)+120-w+x]=(""<< 32<<".:%#")[4*u.count(( " " ;"0"))/u.size]}};;puts\ s+";_ The Qlobe#{" "*18+ ( "#######. ." ;"Copyright(C).Yusuke End\ oh, 2010")}";exit~;_ The Qlobe Copyright(C).Yusuke Endoh, 2010 v=0132;eval$s=%q~d=%!^Lcf<LK8, _@7gj*LJ=c5nM)Tp1g0%Xv.,S[<>YoP 4ZojjV)O>qIH1/n[|2yE[>:ieC ":::#######%" 97N-A&Kj_K_><wS5rtWk@*a+Y5 yH?b[F^e7C/56j|pmRe+:)B "################ : " O98(Zh)'Iof*nm.,$C5Nyt= PPu01Avw^<IiQ=5$'D-y? "####################. " g6`YT+qLw9k^ch|K'),tc 6ygIL8xI#LNz3v}T=4W " .####:############: . " lL27FZ0ij)7TQCI)P7u }RT5-iJbbG5P-DHB<. "# # :################# . " R,YvZ_rnv6ky-G+4U' $*are@b4U351Q-ug5 "#######################% " 00x8RR%`Om7VDp4M5 PFixrPvl&<p[]1IJ "######:#### %######### " EGgDt8Lm#;bc4zS^ y]0`_PstfUxOC(q "#######:##% .## .### .. " /,}.YOIFj(k&q_V zcaAi?]^lCVYp!; "##########. #. .:#. . " ;s="v=%04o;ev"% (;v=(v-($*+[45, "#########% : : : : " ])[n=0].to_i;)% 360)+"al$s=%q#{ "######### :% %#: " ;;"%c"%126+$s<< 126}";d.gsub!(/ "#######% #::#.: %#% " |\s|".*"/,"");; require"zlib"|| ":######. : :#% " ;d=d.unpack"C*" d.map{|c|n=(n|| ".######: . :% : " )*90+(c-2)%91}; e=["%x"%n].pack ":###### #: %###%% " &&"H*";e=Zlib:: Inflate.inflate( ".####% :: ########. " &&e).unpack("b*" )[0];22.times{|y| " %### ########. " ;w=(Math.sqrt(1-( (y*2.0-21)/22)**(; " .#% ##:%###. " ;2))*23).floor;(w* 2-1).times{|x|u=(e+ " %% . " )[y*z=360,z]*2;u=u[ 90*x/w+v+90,90/w];s[( " . " ;y*80)+120-w+x]=(""<< 32<<".:%#")[4*u.count(( " " ;"0"))/u.size]}};;puts\ s+";_ The Qlobe#{" "*18+ ( "##########." ;"Copyright(C).Yusuke End\ oh, 2010")}";exit~;_ The Qlobe Copyright(C).Yusuke Endoh, 2010 v=0055;eval$s=%q~d=%!^Lcf<LK8, _@7gj*LJ=c5nM)Tp1g0%Xv.,S[<>YoP 4ZojjV)O>qIH1/n[|2yE[>:ieC "% :::#####" 97N-A&Kj_K_><wS5rtWk@*a+Y5 yH?b[F^e7C/56j|pmRe+:)B " .:################" O98(Zh)'Iof*nm.,$C5Nyt= PPu01Avw^<IiQ=5$'D-y? " ######################" g6`YT+qLw9k^ch|K'),tc 6ygIL8xI#LNz3v}T=4W " #. .####:############: " lL27FZ0ij)7TQCI)P7u }RT5-iJbbG5P-DHB<. " ##### # :################# . " R,YvZ_rnv6ky-G+4U' $*are@b4U351Q-ug5 " :############################ " 00x8RR%`Om7VDp4M5 PFixrPvl&<p[]1IJ " ############:#### %######### " EGgDt8Lm#;bc4zS^ y]0`_PstfUxOC(q " %############:### %#: %##: : " /,}.YOIFj(k&q_V zcaAi?]^lCVYp!; " .################. #. .:#. . " ;s="v=%04o;ev"% (;v=(v-($*+[45, " :##############% : : : : " ])[n=0].to_i;)% 360)+"al$s=%q#{ " ######### :% %#: " ;;"%c"%126+$s<< 126}";d.gsub!(/ " #######% #::#.: %#" |\s|".*"/,"");; require"zlib"|| " :######. : :" ;d=d.unpack"C*" d.map{|c|n=(n|| " .######: . :% " )*90+(c-2)%91}; e=["%x"%n].pack " ######%:# .###%" &&"H*";e=Zlib:: Inflate.inflate( " .####% :: ######" &&e).unpack("b*" )[0];22.times{|y| " .###: :#####" ;w=(Math.sqrt(1-( (y*2.0-21)/22)**(; " .#% ##:%#" ;2))*23).floor;(w* 2-1).times{|x|u=(e+ " " )[y*z=360,z]*2;u=u[ 90*x/w+v+90,90/w];s[( " " ;y*80)+120-w+x]=(""<< 32<<".:%#")[4*u.count(( " " ;"0"))/u.size]}};;puts\ s+";_ The Qlobe#{" "*18+ ( ":##########" ;"Copyright(C).Yusuke End\ oh, 2010")}";exit~;_ The Qlobe Copyright(C).Yusuke Endoh, 2010 v=0000;eval$s=%q~d=%!^Lcf<LK8, _@7gj*LJ=c5nM)Tp1g0%Xv.,S[<>YoP 4ZojjV)O>qIH1/n[|2yE[>:ieC "%.#% :::##" 97N-A&Kj_K_><wS5rtWk@*a+Y5 yH?b[F^e7C/56j|pmRe+:)B "##% ::##########" O98(Zh)'Iof*nm.,$C5Nyt= PPu01Avw^<IiQ=5$'D-y? "##: ###############" g6`YT+qLw9k^ch|K'),tc 6ygIL8xI#LNz3v}T=4W "# #. .####:#######" lL27FZ0ij)7TQCI)P7u }RT5-iJbbG5P-DHB<. " ##### # :############" R,YvZ_rnv6ky-G+4U' $*are@b4U351Q-ug5 " #######################" 00x8RR%`Om7VDp4M5 PFixrPvl&<p[]1IJ " ############:#### %#####" EGgDt8Lm#;bc4zS^ y]0`_PstfUxOC(q " .#############:##% .## ." /,}.YOIFj(k&q_V zcaAi?]^lCVYp!; " %% .################. #. " ;s="v=%04o;ev"% (;v=(v-($*+[45, ":####: :##############% : " ])[n=0].to_i;)% 360)+"al$s=%q#{ "%######. ######### " ;;"%c"%126+$s<< 126}";d.gsub!(/ "##########. #######% " |\s|".*"/,"");; require"zlib"|| "########### :######. " ;d=d.unpack"C*" d.map{|c|n=(n|| ":#########: .######: . " )*90+(c-2)%91}; e=["%x"%n].pack " :#######% :###### #: " &&"H*";e=Zlib:: Inflate.inflate( " ######% .####% :: " &&e).unpack("b*" )[0];22.times{|y| " ####% %### " ;w=(Math.sqrt(1-( (y*2.0-21)/22)**(; " .###: .#% " ;2))*23).floor;(w* 2-1).times{|x|u=(e+ " %## " )[y*z=360,z]*2;u=u[ 90*x/w+v+90,90/w];s[( " #. " ;y*80)+120-w+x]=(""<< 32<<".:%#")[4*u.count(( " . " ;"0"))/u.size]}};;puts\ s+";_ The Qlobe#{" "*18+ ( "# :#######" ;"Copyright(C).Yusuke End\ oh, 2010")}";exit~;_ The Qlobe Copyright(C).Yusuke Endoh, 2010 

translated from mamememo in Japanese (2010-09-05).

Read next

Aimogen Pro v2.9.5 – All-in-One AI Content Writer, Editor, ChatBot & Automation Toolkit WordPress Plugin Free Download. The Fastest, the Best-rated, and the Best-selling, general the #1 AI WordPress Plugin to Create High Quality AI Content, Edit Content using AI, Add a Chatbot to your Website and mor.

Main Features

• AI Content Writer
• Voice Input and Output
• Transform any YouTube Video into a Blog Post
• 150+ Features
• Auto Post Publishing or Updating
• Chatbots
• Capture Leads from Chatbot
• Shortcode System
• Create Unique and Relevant Content
• Manually Post
• Automatically Featured Image, Scraped from Pixabay, Pexels, MorgueFile or Flickr
• AI Assistant
• Enable/Disable Comments
• Scheduled Rule
• Keyword Replacer Tool
• Random Sentence Generator Tool
• Review Writer
• Create Images using Dall-E 3 and Dall-E 3
• AI Forms
• and more

Download AIomatic – Automatic AI Content Writer Plugin

v2.9.5

v2.5.9

v2.4.9

v2.2.6

v1.8.7

v1.3.5

v1.1.4

v1.0.4

Free download Aimogen Pro – All-in-One AI Content Writer, Editor, ChatBot & Automation Toolkit WordPress plugin nulled by CodeRevolution on Codecanyon 38877369 automatic part penning plugin download.

First, several terminology; A representative email volition former through many distinct components on the way to the recipient:

 1. Sender's MUA [Via SMTP on harbor 465] 2. Sending MSA 3. Sending MTA [Via SMTP on harbor 25] 4. Receiving MTA 5. Receiving LDA and communication store [Via IMAP] 7. Receiver's MUA 

(These aren't all necessarily distinct machines or equal distinct programs, but it is helpful to name all step.)

The communication person delegate (MUA) runs on the user's device and is what they use to dispatch or peruse messages. Let's say they dispatch something: that communication volition be uploaded to to the submission delegate (MSA) which checks the user's password before handing off to the communication transfer delegate (MTA).

The transfer agent's job is to conversation to another communication servers and get the communication to the receiving side's MTA. Once received, it's stated to the local shipment delegate (LDA) to be stored until the recipient checks their email. The name "LDA" is non-standard, but I use it to evade having four distinct abbreviations differing by a sole letter.

The logic for this structure is that whenever the scheme was being designed (around 1980), most organizations could lone oversee a sole server. Maintenance was a complete period job and updates frequently required multiple days of downtime. A well-connected device power have dedicated single-digits megabit/second nexus that worked fractional the time.

This forced the MTA and MUA distinction: if the recipient's server isn't up whenever the email is set, the sending MTA volition preserve the communication and re-attempt shipment later. This way, abbreviated outages don't logic bounced mail. Since the communication client is an interactive program the person runs, a distinct communication shop is needed to keep the email until it can be read.

Most MTAs are configured to continue retrying a communication for five days, normally alongside exponential backoff: mine volition delay 5 minutes following the archetypal failure, and addition the duration to one hr in prolonged outages.

The MSA and LDA have continually existed in several capacity, but have gotten a lot additional complicated when group started accessing email from their own computers alternatively or remotely logging onto a server.

SMTP

Most communication happens complete the Simple Mail Transfer Protocol, including MTA-MTA delivery. To narrow it downward a bit, I'll feign do be an MTA sending email to blog@maurycyz.com.

The archetypal stage is to appearance up the receiving MTA for that domain:

 # dig MX maurycyz.com [snip] maurycyz.com. 300 IN MX 1 smallcrow.com. [snip] # dig A smallcrow.com [snip] smallcrow.com. 300 IN A 65.109.172.162 [snip] 

Email is old adequate to have it's own dedicated DNS document alternatively of using subdomain hacks or TXT abuse. The figure is a precedence (smaller is higher), which is used if multiple hosts are specified: a big email provider volition have multiple servers to justify timely delivery.

SMTP is a comparatively straightforward content based protocol. The one capture is that most communication servers volition necessitate a CRLF as a data terminator. This can frequently be sent alongside ctrl-m, but using a tool that automatically inserts cartridge-return bytes is easier:

 # telnet telnet> set crlf Will dispatch wagon returns as telnet <CR><LF>. telnet> open smallcrow.com 25 Trying 65.109.172.162... Connected to smallcrow.com. Escape character is '^]'. 220 smallcrow.com ESMTP Postfix HELO nowhere 250 smallcrow.com MAIL FROM:<me@nowhere> 250 2.1.0 Ok RCPT TO:<blog@maurycyz.com> 250 2.1.5 Ok DATA 354 End data alongside <CR><LF>.<CR><LF> From: <me@nowhere> To: <blog@maurycyz.com> Hello, world. . 250 2.0.0 Ok: queued as C870D7CD93 QUIT 221 2.0.0 Bye 

Each row sent is a command, to which the distant server responds alongside a three numeral figure followed by a individual readable explaintaion. 200 responses average it worked, 300 is "carry on...", 400 indicates impermanent errors which inform the sender to try again later, 500 errors signify that the email have to be returned as un-deliverable.

(If this seems akin to HTTP, that's no coincidence. A lot of the web, including its header syntax, was lifted from SMTP)

The archetypal command is continually HELO (or EHLO), followed the sending MTA's hostname. This is normally not the identical hostname that's in an email address, but many providers necessitate it to equivalent the sender's IP address. . The next two, MAIL FROM and RCPT TO define the location to provision to, and the location for any nonaccomplishment notifications. Bounce messages are normally generated one stage up from anywhere the error occurred: in most cases the receiving MTA has a issue and sends an error code to the sending MTA, but by that period MSA has already disconnect, forcing an emailed notification. Those notification themselves use an bare MAIL FROM to evade infinite loops.

Once the location has been stated and accepted, a DATA command is sent, followed by the genuine message. This, at a minimum, contains the "From" and "To" headers alongside alongside several text. The communication is terminated alongside a solitary duration to which the server replies to signify that the communication was sucessfuly handed off.

Final hop MTAs should onward the email to the LDA before sending rear a position code. This ensures that they never obtain a communication which they can't deliver, which would outcome in a error notification. This "backscatter" communication interacts seriously alongside spammers that forge MAIL FROM: it turns their evidently bogus communication into one that is apt to be delivered and logic a nusance.

There is no necessity for the addresses inner the email to equivalent the ones in MAIL FROM and RCPT TO (also known as the envelope). The most average logic of this is a communication that has been forwarded. For example, a mailing catalog volition set the letter cover destination to equivalent all member's email, but keep the first "From" and "To" headers intact so that replies activity correctly. The letter cover from volition normally be changed to item to location the catalog director volition inspect for error notifications.

Now, it's not that intermediate systems don't modify the headers: Most stages volition add a "received" header to document anywhere they got the message.

While required for MTA to MTA communication, SMTP is used throughout the entire system. The communication client submits email using a distinct port, but complete the identical protocol. Communication between inner components (i.e. MTA to LDA) frequently uses the closely connected Local Mail Transfer Protocol: the chief difference is the assumption that the receiver doesn't have a communication queue and volition either provision the communication immediately or come back an error.

Submission normally uses TLS to harbor 465, alongside the supplement of a password (in base64):

 AUTH PLAIN 334 AGh1bnRlcgBodW50ZXIy 235 2.7.0 Authentication successful 

The one item that's considerably distinct is the MUA's fetch, which operates on a "pull" basis. I won't go into the syntax here, but it's not terribly complicated.

... but if you really try sending an email to, say, gmail, according to what I've written so far, it won't work. Some of that is because of them enforcing things akin the Message-Id header: a distinctive identifier used to de-duplicate communication in cases anywhere the receiving MTA accepts an email but the association drops before the sender is informed concerning this. This causes the sender to try again later, which duplicating the message.

However, a big part of it is...

Authentication

Base SMTP trusts that all sender is be fine behaved: anyone can dispatch email as anyone else. In fact, many hosts were configured to obtain and relay communication from anyone as a conveyance for whenever someone's customary server was down.

The first resolution to bad behavior was to get the culprit kicked off the internet... but that cut distinct quickly formerly the network grew and companies began getting involved: the archetypal documented case of spam email was sent in 1978 and sold 13 myriad dollars in computers. While authentication doesn't forestall spam, it makes it imaginable to display out unwanted senders.

Verifying sender addresses is not imaginable using the MX record, since there is no justify the identical presenter is used for receiving and sending mail. The simplest resolution is to publish the sending location in a seperate DNS record:

 @ TXT v=spf1 ip4:65.109.172.162 ip6:2a01:4f9:c011:841a:b01d::1 -all ; Roughly: ; authorize from 65.109.172.162 ; authorize from 2a01:4f9:c011:841a:b01d::1 ; refuse otherwise 

However, that's not fairly adequate for the email empire. Big-tech additionally wants the email build to be signed alongside a cryptographic key published via a (DKIM) DNS record. This requires adding a stage to sending mails, normally as a plugin for the MTA.

While I rag on big-tech a lot, but this is really a sensible policy: SPF can lone verify the MAIL FROM, since forwarding the email volition chance the origin IP address. DKIM signatures are attached to the communication and can be used to verify the first sender (the "From" address) of a message, which is what's really shown to the person in most cases.

However, the two of these don't really forestall spam, since spammers can fair set up a few TXT records. Big-tech additionally requires the sender's HELO hostname to be accordant alongside their IP address, via the two onward and reverse DNS. This helps forestall compromised devices from spewing out junk: a astute TV is improbable to have a meaningful PTR record, and if it does, that hostname won't determine rear to it's address.

... unfortunately this guideline additionally makes it unattainable to immediately dispatch communication from most residential net connections unless you own the location block. Of course, the resolution is to pay a big-tech business prosperity to relay your emails. If you don't akin this, discover a communication provider alongside additional permissive rules: the lone logic big-tech is capable to keep their racket operating that five or so companies authority 99% of email.

The message

This is anywhere SMTP stops being so simple. Let's appearance at the simplest imaginable email formerly it's been delivered:

 Return-Path: <alex@there> Delivered-To: bob@here Received: from here by current alongside LMTP id bs05E10S7Go4VQMAHrglgg (envelope-from <alex@there>) for <bob@here>; Thu, 05 Nov 2026 05:21:33 +0000 DKIM-Filter: OpenDKIM Filter v2.11.0 current B05E67CD18 Received-SPF: None (mailfrom) identity=mailfrom; client-ip=313.33.33.337; helo=there; envelope-from=alex@there; receiver=here Received: from there (unknown [313.33.333.337]) by current (Postfix) alongside SMTP id B05E67CD18 for <bob@here>; Thu, 05 Nov 2026 05:20:42 +0000 (UTC) From: alex@there To: bob@here Hello, World! 

The format of the headers is superficially akin to HTTP headers, except that no row should exceed 78 bytes. (without the CRLF row terminator) Overlong headers are damaged up and newly created lines are prefixed alongside whitespace to signify that they are a continuation of the final header.

Mail application mostly preppends headers to the commencement of a message, so it's helpful to peruse them backwards. "From" and "to" are fairly oneself explanatory. Next, the "received" header contains a note from the receiving MTA: it includes the source's HELO name, IP address, RCPT TO and a timestamp.

The MTA afterward performed SPF and DKIM checks, which came up empty: There's no signature and the MAIL FROM hostname is not publically resolvable.

The LDA added another "received" header, although it's not extremely helpful. More importantly, it tacked on the "return-path" alongside the first MAIL FROM location and recorded the mailbox the communication was delivered to.

However, the build isn't continually plain text. This is an email that includes formatting:

 [...] MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=----IX71FHL6PHA0538LS1WKT2W9SF7S8X Content-Transfer-Encoding: 7bit ------IX71FHL6PHA0538LS1WKT2W9SF7S8X Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello, World! I can do bold text! ------IX71FHL6PHA0538LS1WKT2W9SF7S8X Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <!DOCTYPE html><html><body><div dir=3D"auto">Hello, world! I can do <b>bold&lt= /b> text</div></body></html> ------IX71FHL6PHA0538LS1WKT2W9SF7S8X-- 

That's right, it's a web page!

However, since not all email clients can comprehend HTML, the communication additionally includes a plain content version. This is done using MIME's "multipart" encoding, in this case, multipart/alternative, which indicates all the versions are functionally equivalent.

MIME's type figure has been stuck at 1.0 since 1996.

The delimiter is a randomly chosen string, which allows multiple multiparts to be nested inner without escaping. Each division of the communication has it's own headers, in this case, indicating that it's sent in the quoted-printable encoding. This allows the email communication to merge any bytes without exposing the MTA to scary things akin non-seven-bit ASCII: remember, the SMTP is 45 years old.

In quoted-printable, equal signs are used as the escape character: if followed by two hex digits, it decodes to that byte. If followed by a newline, the two characters are removed. This is used to interrupt lengthy lines that could alternatively logic trouble.

In this email, "=3D" becomes a literal equal sign and the two lines are joined together. If you've always seen an email alongside stray equals or missing one or two characters ~ all 80 bytes, damaged quoted-printable decoding is normally the culprit.

The second "content-transfer-encoding" is base64, which is used for binary records akin attached images:

 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="5ZTNvId/H+rlk7Fr" Content-Disposition: inline --5ZTNvId/H+rlk7Fr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Check out this file: --5ZTNvId/H+rlk7Fr Content-Type: application/octet-stream Content-Disposition: attachment; filename="file.bin" Content-Transfer-Encoding: base64 J7mtSdbQItOAi345nwaNkkTXrnDIRPA0DSwhbSAOwm2C/KoHjQIotY9lnJRMBRk9InQaHOxL bb7DGd9EN6uRpjvCbox9xblAh3CxH7sl+YAkYcKw1V100RpBwMhgaXfUJBB3oRkLffgRwEyK v9qFBLp9zZ+SiRJoRWbA4aZLexPhHZ35vFROVKYtiAeMlD1s15v3kPZvEADam0e45BoSaqmp 1S3z3b5wBIFHJUxQULD589MKaFx2Z2A+91pl/pbZWmZkzt55D/hZ05kjUUbXUnDnTYAQE2Gk WnN+SnrQvfEO+Tz7AdrbLD1q2DgwWW+k0cVJLKjdwRxesGhAkQCZfHVrno6R4iXjTbInIbQv hXzQiV840iUiUhk282WADd1ffJ0sot2Waf7XHLIE1lZVFQ3iGofYbw8pZlg3sb35AnIWPZKv fbC6Yh95RV23R4K2NHeBX1rpl4bSSiftnD2RbsBzv7cgw/6M/Lj3O40NFGAaUC+J7TpAaXdi tvlPsNQhMo8QRf/ub7WK42cPUlz1fKq1k1pzGN96YOsE5azMfF4vLANtbtbVmLIp2WmgBk0P 9IGMWy/xIAe0cOh+bqzru2+ojJGgx9uX4VSTP9BaTOwkVX5+rQfpp1qJodtHiO8sHw6Pg+Mg WcpqQPC7118ccuT44cVpIRkwOSoJzsW++WM= --5ZTNvId/H+rlk7Fr-- 

This is why size limits are frequently disappointing: the email volition be 33% larger than the attached file. More productive encodings (raw binary data) are supported by several MTAs, but may have to be converted to base64 location downward the path... which would interrupt DKIM signing.

Generally:

• No encoding ("7-bit") can be used if the communication has abbreviated lines and fits in low-bit ASCII. However, "7-bit" is mostly seen as a null encoding for already encoded multipart containers.
• Quoted-printable if the communication is mostly text, but has item that risks breaking ancient software.
• Base64 for binary data.

About TLS

The SSL/TLS used by communication clients is efficiently the identical as for a browser: the communication provider must go to a certificate authority, demonstrate their character and get a certificate.. Algorithms and ciphers are impaired at the least clue they may be insecure.

However, MTAs operates on "trusted" networks... although it's small that an attacker can't get admission to net traffic, but that if they could, it would be imaginable for them to continue an ACME difficulty and obtain out a trusted certificate.

As a result, the goal is mostly to defend against passive eavesdropping: most sysadmins don't annoy dealing alongside a CA and use self-signed certificates. (it's not akin CAs have a fine track record: 4)

Another weird item concerning email is that MTAs don't use a distinct TLS port. All connections on harbor 25 commencement as plaintext, afterward the sender issues a STARTTLS command and hands complete the association to a SSL/TLS library. It's slightly janky, but it allows servers to attempt to use encryption and cleanly autumn rear if it's not supported.

Such an method isn't awesome for submissions, since a autumn rear would leak the password... and baddies on shared networks or nosy residential ISPs can band out the STARTTLS command. For this case, it's finest to default use the dedicated SSL submission port: 465.

(This harbor really has a bit of a history, alongside it being deprecated in favor of STARTTLS before being re-endorsed formerly we realized using optional SSL for passwords was a bad idea.)

So what??

Unless you compose email connected application or run infrastructure, most of this data is deeply useless. However, there are a few things you power desire to remember.

The underlying protocols authorize five days for delivery, and it can sometimes obtain longer. Since users anticipate shipment in seconds and most emails are at smallest slightly period sensitive, some MTAs are configured to dispatch out postpone notification if a communication is taking a while.

You may desire to discover out if yours does this before assuming the recipient is ignoring you.

Emails are digital postcards.

A communication volition be stored and forwarded by multiple systems in plaintext. Anyone on the network way may be capable to peruse your email: SSL/TLS is not universally supported and can trivially be stripped out by energetic attackers.

This is an inherent part of email: there's no way to tack-on powerful encryption without breaking existing clients. If you need a justify of privacy, you must encrypt the communication before sending, and the recipient must decrypt it themselves. Be careful alongside built-in tools akin PGP: these mostly create it way too uncomplicated to accidentally hit "reply-all" without encrypting, in supplement to another flaws akin exposing the topic line.

Since publication, multiple group have written to me explaining how obfuscating the topic row (or alert if the person fills it out) is completly unreasonable to anticipate from a for a self-proclaimed privacy tool. At smallest in my eyes, "encrypted messaging" method encrypted, not 90% encrypted and 10% plaintext.

The deficiency of deniablity and onward secrecy can be excused as limitiations of email's store-and-forward architecture... but default plaintext and making no attempt to encrypt certain the topic row or attachments is a formula for disaster: at smallest alongside vanilla email, group cognize it is not encrypted.

"Encrypted" email providers are mostly snake oil. While the communication shop can encrypt messages and a tradition MUA could decrypt them, the MTA must have admission to plaintext. As a result, it provides minimal to no safety against most assault vectors notwithstanding the "millitary class encryption". The lone way to fix email would be to get everyone to concur to toggle to an end-to-end encrypted protocol... but the entire item of email is worldwide compatability: encrypted messaging can exist, but encrypted email is contradictory.

The finest anticipation is to discover a communication provider that can be trusted not to snoop messages. That is to say, not an Advertising business (google) or one that's been pushing difficult for LLMs (microsoft / apple): both of these businesses create powerful incentives to peruse your messages. Although you'll motionless have to anticipation whoever you are communicating alongside isn't beign snooped on by their provider.

Worse, DKIM signatures act as a lifelong evidence that an email came from your provider's servers, equal if a communication is years old and has no apparent sequence of custody. This makes leaked, hacked, or snooped emails ideal blackmail material: since the bad performer can trivially demonstrate they haven't been fabricated.

This property, called non-repudiation, is mostly not desirable for messaging systems. Avoiding signing not an choice if you desire to interoperate alongside big-tech, but it is imaginable to regularly rotate and publish personal keys. Before they key is published, the signature can be trusted to verify it is legitimate. However, formerly the key has been published, the signature can been forged by anyone and is rendered retroactively untrustworthy.

Since authentication is checked during shipment by the MTA and LDA, this doesn't power how the email volition be handled. However, it volition mold doubt on the authenticity of leaked messages since the signature could have been forged alongside minimal effort.

While key rotation is average practice, most communication providers don't publish their old personal keys, so the signature is motionless trustworthy (modulo the assistance being hacked). I would advise against emailing item you wouldn't be comfortable study out in public.

• https://www.rfc-editor.org/info/rfc821/: Original SMTP
• https://www.rfc-editor.org/info/rfc2045/: MIME extended communication format
• https://www.rfc-editor.org/info/rfc7208/: SPF Authentication
• https://www.rfc-editor.org/info/rfc6376/: DKIM signing