This website operates the sovereign addr.bar Federated Messaging Protocol. Visitors and external server hosts can send a direct, authenticated message to this website provided they also operate a website running this same form.
How to Send a Message to this Website:
Visit your own website that operates this script.
Log in to your website and open the Mail Form.
Enter this website's canonical endpoint into the Destination Website URLs field:
https://novy.addr.bar/index.php
Install on Your Website via GitHub:
If you operate a website, you can install the federated correspondence system directly from GitHub using the command line:
git clone https://github.com/addressbar-net/contact.git && cd contact && sudo ./install.sh
🔒 Direct HTTP Stream Transmission: When a message is dispatched, the two PHP files communicate server-to-server using PHP's stream_context_create() and file_get_contents() HTTP POST requests—no Reverse DNS (PTR) configuration is required.
The addr.bar Federated Mail Protocol enables sovereign, decentralized communication between independent websites running this PHP directory script. No centralized middleman or third-party email server is required.
2. Key Features
Single User Per Domain: Each domain has a single sovereign host account that manages the directory and receives all incoming correspondence.
Multiple Destination URLs: Senders can specify one or more destination website URLs in the mail form.
Single Outbox Storage: When a message is sent to multiple destination websites, one consolidated message record is saved in the outbox.
Inbox Storage for Sender: A copy of all sent dispatches is automatically stored in the sender's own inbox for complete record-keeping and conversation review.
Website Message Rate Limiting & Delay: Remote websites can be rate-limited (default 10 messages/day per website). A warning reply is issued when the next message will reach the limit. When the limit is reached, future messages are delayed. If a message cannot be sent due to the limit, it is saved in the sender's inbox as delayed and can be sent after the delay.
Default Messaging Form: Frequently used destination websites can be saved and loaded into the form with a single button click.
Visible Distribution List: Senders can optionally include the full destination website list in the message header.
3. Communication Workflow
Form Composition: A host visits their own website, logs in, and fills the Mail Form with Destination Website URLs (e.g., https://tricurse.com/contact), optional subject, and message.
Direct HTTP Stream Transmission: The sender website's PHP script initiates a server-to-server HTTP POST request using stream_context_create() and file_get_contents() to the destination website's endpoint—without requiring Reverse DNS (PTR) records.
Host Toggle Check: The receiving server verifies that incoming communications are currently enabled by the host.
Site Blocklist Evaluation: The receiving server checks its SQLite blocked_sites table to ensure the sender domain and IP are not blocked.
Inbox Delivery: Accepted messages are recorded in SQLite (incoming_messages table) for the domain's host.
{
"success": true,
"message_id": 42,
"verification": "STREAM_CONTEXT_POST",
"note": "Message received via stream_context_create() HTTP POST and accepted into host inbox."
}