___________ .__ .__ ._. \_ _____/____ _______ ______ _ __ ____ | | | || | | __) \__ \\_ __ \_/ __ \ \/ \/ // __ \| | | || | | \ / __ \| | \/\ ___/\ /\ ___/| |_| |_\| \___ / (____ /__| \___ >\/\_/ \___ >____/____/_ \/ \/ \/ \/ \/ After many years of free service, GhettoSMTP is no longer accepting new domains. We will be stopping all service by December 31, 2026. It's been fun! However, stop for a minute and consider why you wanted to use us. Whatever the reason, you'd be better off doing this on your own with a small cloud instance. Top notes for you to keep in mind: - Yes you can do this on your own cheaply and securely. - In 2026 and beyond, AI is your friend. Talk it out with an advanced LLM, stay curious, learn a bit along the way. - Email support@ghettosmtp.com any time if you want to kick around some ideas for redirecting and spooling your own email. - Keep more control over your email! - Learn a little bit about DNS, don't abdicate that to the robots. ;) ________ .________.___. \______ \ | \__ | | | | \| |/ | | | ` \ |\____ | /_______ /___|/ ______| \/ \/ Want to do it yourself? You can, and you should! GhettoSMTP was simply Exim accepting email for a domain, and then relaying it to another server (e.g. the mail server that you ran on a non standard port). We never did outbound email, that's a degree of suffering that no one should ever self inflict. The flow of email for a service like GhettoSMTP goes like this: - Someone wants to send you an email, so they write it and send it to yourname@yourdomain.com. - Their outbound mail server checks DNS for yourdomain.com to determine what servers perform SMTP functions for the domain. That's known as "MX records" or Mail Exchangers. - If you used GhettoSMTP, your MX records for yourdomain.com were: --- in1.ghettosmtp.com --- in2.ghettosmtp.com - The original email that someone was trying to send to you gets sent over the open internet to in1 or in2.ghettosmtp.com over port 25. --- that Port 25 part was the reason you were looking at GhettoSMTP, wasn't it? You can't receive anything over TCP port 25, so you likely have a mail server at home and can't accept standard SMTP server communication. - Our Exim installation received the email and checked to see if the domain was in our list of accepted domains. - If it was accepted, the Exim config then checked what downstream host and port to send the message to. GhettoSMTP customers typically had a mail server with a public DNS name that was listening on port 2525 or 587. - If your mail server accepted the message, we were done with the transaction. - If your mail server was unavailable, we retried every 15 minutes for 30 days, then bounced it back. Here's a sample config that shows the main parts of an Exim config that could be used to operate a service like GhettoSMTP: The following sample Exim config sends email bound to the entire domain to a downstream SMTO server in a route file that also expresses the downstream port to use. This is where the magic happens that allows you to run a fully featured email server at home. ```exim domainlist local_domains = @ : localhost domainlist relay_to_domains = lsearch;/etc/exim/public-routes acl_smtp_rcpt = acl_check_rcpt ignore_bounce_errors_after = 2d timeout_frozen_after = 7d begin acl acl_check_rcpt: require message = relay not permitted domains = +relay_to_domains require verify = recipient accept begin routers dnslookup: driver = dnslookup domains = !+local_domains : !+relay_to_domains transport = remote_smtp no_more ghettosmtp: driver = manualroute domains = +relay_to_domains transport = remote_smtp route_data = ${lookup{$domain}lsearch{/etc/exim/public-routes}} no_more begin transports remote_smtp: driver = smtp begin retry # Change the below to be as generous to yourself as possible to retain email, and as aggressive as you want for redelivery. * * F,30d,15m # Then in the file /etc/exim/public-routes # You use the following syntax to use a nonstandard SMTP port: # example.tld: downstream.example.tld::2525 ``` If you want every address at your domain to go to one Gmail address instead (Or whatever single email address you want), use a redirect router and a domain-to-mailbox map: ```exim domainlist local_domains = @ : localhost domainlist forward_domains = lsearch;/etc/exim/gmail-forwarders acl_smtp_rcpt = acl_check_rcpt ignore_bounce_errors_after = 2d timeout_frozen_after = 7d begin acl acl_check_rcpt: require message = relay not permitted domains = +forward_domains require verify = recipient accept begin routers forward_domain_to_gmail: driver = redirect domains = +forward_domains data = ${lookup{$domain}lsearch{/etc/exim/gmail-forwarders}} no_more dnslookup: driver = dnslookup domains = !+local_domains : !+forward_domains transport = remote_smtp no_more begin transports remote_smtp: driver = smtp begin retry * * F,30d,15m # Then in the file you create at /etc/exim/gmail-forwarders # use the following syntax: # example.tld: yourname@gmail.com ``` The single mailbox config is essentially a catchall forwarder. You will receive literally everything bound for that domain. You should also look in to SRS for forwarding as well, but that's a somewhat more advanced topic for you and your LLM of choice. We'll stop there, but if you have your own port 25 mirror, then you could also perhaps start using plugins or other tools to check IP address reputations or scanning attachments for viruses before they ever make it to your IMAP / Webmail server at home. _ ______ / )/ ___ \ / / \/ \ \ / / ___) / ( ( (___ ( \ \ ) \ \ \ /\___/ / \_)\______/ ♥ Thanks for hanging with GhettoSMTP through all the years. Reach out to support@ghettosmtp.com for any reason in 2026 before the email shuts off. August 2026