Sending Mail (SMTP) with Your Virtual Machine
Coming from another cloud?
▸AWS·EC2 Instances
EC2 Instances
- Uses EC2 RunInstances API instead of Nova servers.create.
- Requires predefined instance type selection.
- Supports per-second On-Demand billing and Spot/Reserved options.
- Includes hibernation state not standard in OpenStack.
▸Azure·Virtual Machines
Virtual Machines
- Uses Azure Resource Manager (ARM) REST API at /providers/Microsoft.Compute/virtualMachines instead of OpenStack Nova API at /v2.1/servers.
- Tightly integrated with Azure services like Azure Active Directory for authentication, unlike OpenStack's Keystone.
- VM creation requires specifying size from predefined series with hardware-specific features (e.g., AMD/Intel/ARM), not custom flavor configs.
- Billed per second with complex pricing tiers based on series/reservation options, vs OpenStack's typically hourly or usage-based.
▸DigitalOcean·Droplets
Droplets
- API surface is DigitalOcean’s proprietary REST/CLI/Terraform tooling rather than OpenStack Nova/Neutron/Glance APIs (Droplets are managed via DigitalOcean UI/CLI/API/Terraform).
- Billing is usage-based with per-second billing (60-second minimum and monthly cap) rather than the typical per-hour, quota-based charge model users often see in OpenStack-based clouds.
- Droplets include a bundled outbound transfer allowance with each plan (starting at 500 GiB/month) rather than a separate bandwidth quota/metering model users often encounter in OpenStack deployments.
- Droplets are described as Linux-based VMs on virtualized hardware with local SSD storage, whereas OpenStack deployments commonly expose distinct block storage (Cinder) and image services (Glance) and may not bundle bandwidth/monitoring/firewalls into the instance offering.
▸Google Cloud·VM instances
VM instances
- Uses REST API 'instances.insert' instead of Nova 'servers.create' with different auth via service accounts vs Keystone.
- Supports bare metal instances (no hypervisor), not in standard OpenStack Nova.
- Network interfaces tied to VPC subnets; differs from Neutron ports/floating IPs.
▸Hetzner·Cloud Servers
Cloud Servers
- Servers provisioned individually via Hetzner API (hcloud), not OpenStack Nova flavors; fixed instance types like CX11 (1 vCPU, 2GB RAM, 20GB NVMe).
- No flavor customization; choose from predefined shared/dedicated vCPU series.
- Billing hourly with monthly cap per server (e.g., €3.29/mo cap for CX11), charged even when powered off until deleted, unlike typical OpenStack stop-to-pause billing.
- Custom REST API at api.hetzner.cloud/v1/servers instead of OpenStack Nova /v2.1/servers (different auth, payloads, response formats).
Sending mail (SMTP) with your virtual machine
By default, SMTP (Simple Mail Transfer Protocol) is blocked on all virtual machines in the Quake AI environment. This policy helps to prevent email abuse.
Quake AI is committed to maintaining a secure and reliable platform for all users. Sending spam is strictly prohibited and may result in the suspension or termination of your account. Unsolicited mass emails and spam violate our terms of service and undermine the trust and integrity of our community.
If you need to send emails from your VM using SMTP, you can request access by opening a support ticket. Please follow the steps below to make sure your request is processed as soon as possible. Note that if you are sending mass emails (that is, mailing lists), please refer to our compliance section below.
Step-by-step: requesting SMTP access#
To enable SMTP for your virtual machine, you’ll need to open a support ticket at https://portal.rumble.cloud/help and include the following information:
- Virtual Machine Details
- Name or ID of the VM you want to use for sending SMTP traffic.
- IP Address
- The public IP address that your VM will use to send email.
- PTR Record (Optional)
- Do you want us to create a PTR (reverse DNS) record for your IP address?
- If Yes, include the domain name that the PTR record should point to.
- If No, you can skip this part.
Example support ticket#
Here’s a sample you can copy and customize:
Subject: Request to Enable SMTP for Virtual Machine
VM Name/ID:
vm-prod-001Public IP Address:123.123.123.123PTR Record: Yes PTR Domain Name:mail.example.com
Important notes#
-
SMTP access is granted on a case-by-case basis to prevent spam and misuse.
-
Make sure your DNS settings match your PTR records for best deliverability.
-
Allow up to 24–48 hours for the support team to process your request.
If you have any questions, feel free to contact our support team. We're here to help!
Compliance guidelines for mass email sending
Compliance with email regulations#
When sending mass emails, your communications must comply with all applicable laws, rules, and industry standards. This includes, but is not limited to, the following requirements:
- Opt-In Consent: Only send emails to recipients who have explicitly opted in to receive communications from you.
- Clear Unsubscribe Mechanism: Every mass email must include a prominent option for unsubscribing. Recipients should be able to opt out and without barriers.
- Accurate Sender Information: Verify your contact details and sender information are accurate and match the expectations set with your subscribers.
Failure to adhere to appropriate guidelines and requirements may result in the suspension or termination of your account.
Best practices for sending mass emails#
Following these best practices helps you maintain a healthy sender reputation and ensures your messages reach the intended audience:
- Collect Explicit Permission: Build your mailing list with users who have given their consent. Avoid purchasing or using third-party lists.
- Segment Your Audience: Organize your recipients based on interests, behavior, or demographics to deliver more relevant content.
- Monitor Engagement Metrics: Monitor your bounce rates, open rates, click-through rates, and unsubscribe rates to gauge the performance of your campaigns.
- Maintain an Up-to-Date Mailing List: Regularly remove inactive or bounced email addresses from your list.
- Use a Consistent Sending Schedule: Establish a regular cadence for your emails to avoid overwhelming your recipients.
- Ensure Proper Authentication: Use SPF, DKIM, and DMARC records to improve your email delivery rates and protect against spoofing.
General mass mailing requirements and additional resources#
Below are a couple of resources that provide a broad look at the requirements for mass mailing including best practices for sending mass emails:
-
Google Bulk Sender Guidelines: Google's Email sender guidelines FAQ
-
Yahoo Mass Email Guidelines: Yahoo's Sender Requirements & Recommendations
Adhering to these guidelines not only helps you meet regulatory requirements but also builds trust with your recipients.
Conclusion#
We appreciate your efforts in following these guidelines and best practices. By ensuring that your mass email campaigns are compliant and respectful of recipient preferences, you contribute to a positive and secure email ecosystem.
If you have any questions or need further assistance, please do not hesitate to contact our support team.
Usage Guidelines
The sample code, software libraries, command line tools, proofs of concept, templates, and other related technology on this page (including any of the foregoing that is provided by Quake AI personnel) is provided to you as Quake AI Content under the Quake AI Customer Agreement, or the relevant written agreement between you and Quake AI (whichever applies). Do not use this Quake AI Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the Quake AI Content (such as sample code) as appropriate for production grade use based on your specific quality control practices and standards. Deploying Quake AI Content may incur Quake AI charges for creating or using Quake AI chargeable resources, such as running Compute instances or storing data in Object Storage. Your use is also subject to the Acceptable Use Policy.
For the full policy, see Usage Guidelines.
Last validated: 19.05.2026
Quick answers
- Why does `openstack image save` write a 0-byte file for my boot-from-volume instance?CLI
- Why does `openstack server create` fail with "Only volume-backed servers are allowed for flavors with zero disk"?CLIAPITerraform
- Why does my project still have a 10 GiB Cinder volume after I deleted my instance?CLIAPI
See Also
Instances
Prerequisite
How to monitor your Quake AI workload with Prometheus and Grafana
Shares: Monitoring
How to ship application logs off your VMs
Shares: Monitoring
How to self-host authoritative DNS on Quake AI
Shares: DNS, Instances
How to issue and auto-renew a TLS certificate with Let's Encrypt
Shares: DNS