Muttrc syntax to enable mutt to send emails
by rnturn from LinuxQuestions.org on (#6KJR5)
I'm sure this is a Muttrc-related problem. Let me know if I'm off base.
Since converting a system to Debian, I cannot get mutt to send emails to internal users using the publicly defined email domain (that has been defined on my ISPs DNS as "mydomain.org"). mutt is being invoked from within scripts running on the Bookworm system and used to work by simply sending mail to "me@mydomain.org". (Inside the firewall, everything is "mydomain.net") Now... I am getting hourly emails telling me that "we're still trying" but mail never makes it to its destination and I get a message from the IMAP subsystem or postfix (not sure which at this point):.
Code:####################################################################
# THIS IS A WARNING ONLY. YOU DO NOT NEED TO RESEND YOUR MESSAGE. #
####################################################################
Your message could not be delivered for more than 1 hour(s).
It will be retried until it is 5 day(s) old.and delivery attempt will continue over the next five days. And this is now happening for ALL of the test emails I tried to send. Oh joy.
I CAN send myself an email to "me@mydomain.org" from Thunderbird if that matters.
The IMAP and SMTP services are running on the same system if that makes any difference. It didn't (for years) before a recent switch to Bookworm that included an older release of mutt. Could it be that SMTP support was not compiled into the mutt binary?
I've minor luck sending an email using mailx but, sadly, that utility doesn't allow me to specify the mime type of the message (I'm sending html in some cases). At least I've not seen the means of specifying the mime type in mailx.
What this predicament results in is, perhaps, having to move cron jobs from one system -- along with the development directories that underlie those jobs (UGH!) -- to run on the mail server. A klugy solution at best.
Any ideas about how to proceed. Please let me know what, if any, additional information would help.
TIA...
Since converting a system to Debian, I cannot get mutt to send emails to internal users using the publicly defined email domain (that has been defined on my ISPs DNS as "mydomain.org"). mutt is being invoked from within scripts running on the Bookworm system and used to work by simply sending mail to "me@mydomain.org". (Inside the firewall, everything is "mydomain.net") Now... I am getting hourly emails telling me that "we're still trying" but mail never makes it to its destination and I get a message from the IMAP subsystem or postfix (not sure which at this point):.
Code:####################################################################
# THIS IS A WARNING ONLY. YOU DO NOT NEED TO RESEND YOUR MESSAGE. #
####################################################################
Your message could not be delivered for more than 1 hour(s).
It will be retried until it is 5 day(s) old.and delivery attempt will continue over the next five days. And this is now happening for ALL of the test emails I tried to send. Oh joy.
I CAN send myself an email to "me@mydomain.org" from Thunderbird if that matters.
The IMAP and SMTP services are running on the same system if that makes any difference. It didn't (for years) before a recent switch to Bookworm that included an older release of mutt. Could it be that SMTP support was not compiled into the mutt binary?
I've minor luck sending an email using mailx but, sadly, that utility doesn't allow me to specify the mime type of the message (I'm sending html in some cases). At least I've not seen the means of specifying the mime type in mailx.
What this predicament results in is, perhaps, having to move cron jobs from one system -- along with the development directories that underlie those jobs (UGH!) -- to run on the mail server. A klugy solution at best.
Any ideas about how to proceed. Please let me know what, if any, additional information would help.
TIA...