I’m looking for a simple sendmail replacement to receive local mail, such as from cron and service failures and forward it to on to a real SMTP server.

I have used msmtpd successfully but thought I’d ask if folks have other solutions they like.

  • @markstosOP
    link
    English
    18 months ago

    Sendmail is a binary provided by a mail system and no mail system is installed by default on Fedora.

    I’m looking for a solution that’s as simple as possible: provide a sendmail binary to pass the message to a third-party SMTP server.

    I’ll connect to Mailgun via TLS— no port 25 involved.

    • Matt The Horwood
      link
      fedilink
      English
      28 months ago

      Not sure if it’s in fedora, but I use nullmail as my mta. Simple to config and does just MTA

      • @markstosOP
        link
        English
        18 months ago

        Thanks. Turns out it’s not in Fedora.

    • @hperrin
      link
      English
      1
      edit-2
      8 months ago

      Sendmail is provided by the sendmail package in Fedora. Here’s some instructions on installing and configuring it:

      https://tecadmin.net/install-sendmail-on-fedora/

      But you might instead be looking for an SMTP client (or a Mail User Agent), which is different:

      https://www.baeldung.com/linux/send-emails-from-terminal

      If you have SMTP credentials with Mailgun, and you’re using port 465 or 587, you want an MUA, not an MTA (Mail Transfer Agent).

      Sendmail can be both, but there are better tools if you’re looking for an SMTP client.

      • @markstosOP
        link
        English
        18 months ago

        Sendmail is a full-blown MTA released 41 years ago that is notoriously difficult to manage. There are reasons that it’s market share has declined from 80% to about 3%. I’m also not looking for a MUA, like mutt. I’m looking for a simple MTA that that only relays outbound mail, like msmtp, ssmtp or nullmailer.

        • @hperrin
          link
          English
          2
          edit-2
          8 months ago

          Again, if you are not using port 25, you don’t need an MTA. Period.

          MTAs are for sending mail from one mail server to another. That’s not what you are doing. You don’t need to be running your own mail server. You are sending mail to an MSA (Mail Submission Agent). Mailgun is the MSA you are submitting to and the MTA that will handle transferring your message to your destination MDA (Mail Delivery Agent).

          If you were submitting mail to your destination server over port 25, you would need an MTA.

          But, as you stated, you are submitting mail to an MSA using port 465 or 587. You need an MUA.

          This terminology is important, because it determines what role the software you’re using plays and how you need to configure it.

          There are plenty of tools that act as both MTAs and/or MUAs depending on how you configure them, because their functionality is very similar. I would guess nearly all tools that can do one can do the other. But if you want to use the right tool the right way, I am telling you, with 100% certainty, you should be looking for an “SMTP client”, “email client”, or “mail user agent” (they mean the same thing). You do not want a relay server, and you do not want an MTA.

          What you probably mean by what you’re asking is something that receives mail addressed locally (acting as an MSA or an MDA), and fowards it (important: this is not the same as relaying, because the destination address is changed) to an MSA (therefore acting as a MUA). If something is forwarding mail like this, instead of relaying, and calling itself an MTA, that is not technically correct. But you probably don’t need that, unless you’re using something that won’t let you configure how/where it sends mail. You just need to set up something that provides a binary that acts as an MUA. Then set up your daemons to send mail to your actual email address using that.

          I’m speaking from experience because I’ve written both an MTA and an MUA, but if you won’t take it from me, take it from Wikipedia:

          An MTA works in the background, while the user usually interacts directly with a mail user agent. One may distinguish initial submission as first passing through an MSA—port 465 (or, for legacy reasons, optionally port 587) is used for communication between an MUA and an MSA, while port 25 is used for communication between MTAs, or from an MSA to an MTA.[5]this distinction is clarified in RFC 8314.

          - https://en.wikipedia.org/wiki/Message_transfer_agent

          • @markstosOP
            link
            English
            18 months ago

            I need a sendmail binary that sends outgoing mail to an SMTP server with as few other features as possible.