mta
Mike Hillyer describes himself as “passionate about all things email infrastructure and deliverability.” Recently, I noticed that his Linkedin profile had changed — he’s now listed as the co-founder of something called Kumo Corp. Their website talks about KumoMTA, an open source, flexible, high performance MTA platform. I reached out to Mike, asking him if he’d like to share with me what they’re doing over there, and I offered to share that along to all of you. So this isn’t really an advertisement — I just thought it would be interesting to share info about something new that caught my eye, and no money changed hands. I hope you find it interesting! And without further ado, take it away, Mike:Here at KumoMTA we all started with a Free/Open-Source software background and then moved into the commercial MTA world. In that time we helped build, install, and support solutions that are
DELIVTERMS: The (more or less) regular series here on Spam Resource that defines deliverability terminology. Unlike some other series out there in the world, this one has neither hot questions nor even hotter wings. But I do hope to help shore up gaps in your email and deliverability-related knowledge. Today, I’m going to talk about MTAs and MUAs, mail transfer agents, and mail user agents.MTA means “Mail Transfer Agent.” The acronym MTA is basically interchangeable with the term “mail server.” An MTA or mail server is an software application running as server software to handle processing and transmission/receipt of email messages. It’s an MTA that responds to a connection on port 25 and answers with “220” and an SMTP banner and accepts or sends inbound or outbound email, transmitted via SMTP. When I look up the MX record for a domain, and I connect to port 25 of that MX
Are you looking for an open source sending MTA solution?For big senders, commercial MTA platforms like PowerMTA or MailerQ are usually the way to go. But for those of you looking for an alternative, ZoneMTA might be something for you to check out.