Sorry for the HTML code; I'm trying to fix it. However, I yum-installed mutt and attempted to send the following email:
Date: Sat, 25 May 2013 10:29:39 -0700 From: Mail Delivery Subsystem MAILER-DAEMON@localhost.localdomain To: richard@localhost.localdomain Subject: Warning: could not send message for past 4 hours
[-- Attachment #1 --] [-- Type: text/plain, Encoding: 7bit, Size: 0.5K --]
********************************************** ** THIS IS A WARNING MESSAGE ONLY ** ** YOU DO NOT NEED TO RESEND YOUR MESSAGE ** **********************************************
The original message was received at Fri, 24 May 2013 22:10:06 -0700 from localhost.localdomain [127.0.0.1]
----- Transcript of session follows ----- users@lists.fedoraproject.org... Deferred: Connection timed out with smtp-mm02.fedoraproject.org. Warning: message still undelivered after 4 hours Will keep trying until message is 5 days old
[-- Attachment #2 --] [-- Type: message/delivery-status, Encoding: 7bit, Size: 0.3K --]
Reporting-MTA: dns; localhost.localdomain Arrival-Date: Fri, 24 May 2013 22:10:06 -0700
Final-Recipient: RFC822; users@lists.fedoraproject.org Action: delayed Status: 4.4.1 Remote-MTA: DNS; smtp-mm02.fedoraproject.org Last-Attempt-Date: Sat, 25 May 2013 10:29:38 -0700 Will-Retry-Until: Wed, 29 May 2013 22:10:06 -0700
[-- Attachment #3 --] [-- Type: message/rfc822, Encoding: 7bit, Size: 0.9K --]
any ideas?
On Mon, 27 May 2013, Richard Vickery wrote:
Sorry for the HTML code; I'm trying to fix it. However, I yum-installed mutt and attempted to send the following email: [snip]
Does this happen with all email, or only email to fedoraproject?
Here's the obligatory "Hmmm... It works out of the box for me..." I hate reading that when I have a problem, but I feel obligated to let you know.
I'm not a mutt expert -- I have it installed only so I can script broadcast emails from the command line -- but my impression is that it's like pine in that it's a client, not a server, and uses the mail server software you have installed for sending (e.g. sendmail, postfix), and hands off to that. The error message you gave looks to me like a server issue. Do you have another client on that box, like alpine, that does work?
Since the problem is a timeout, it sounds like the server is talking to fedoraproject, which means, to me, that mutt has handed it off.
Here are some things that have screwed me over in the past:
1) The mailinglist only accepts mail with your name from one ip address or domain, and this ain't it. Usually this gets a better error message than timeout, but I've seen it.
2) There's an authentication problem (this is the most common for me, particularly if I'm doing POP/IMAP stuff involving dovecot). Again, this usually gets a better error message than a timeout, but I've seen it there, too. A lot depends on how the servers are configured.
3) You do not have your client pointing to the correct server/MTA. I've done this when I've had multiple domains and multiple servers behind one firewall/router. I've also made the mistake of using "localhost" for my server when I didn't mean to, and had installed, but not set up, sendmail on my laptop as part of a default setup. So, I kept trying to debug my "real" mail server and couldn't find a problem, when in fact my mail client was trying to use my unconfigured laptop as a server. Doh. That's a day out of my life I'll never get back.
4) You do not have your domain correctly denoted, and so there's a mismatch (e.g. you are sending from "billoblog.com" but you are attaching "localdomain.") That can cause some problems later on, though usually for me the error message tells me that the reverse lookup failed at the recipient site. I also get this on occasion when sending mail through an ISP that returns the ISP domain on reverse lookup.
5) Fedoraproject's MTA was actually down when you tried to talk to it, and you just have bad timing. It will clear up later.
Since this is a bit of a touchy mailinglist culture here, I assume you'll get all sorts of flak if you send an empty test email using a direct sendmail or postfix command. Maybe there's a "test" address that the mailinglist advertises for debugging. If so, I'd just do the old tried and true "/usr/sbin/sendmail -v somewhere@somedomain < /dev/null " and see what you get. If *that* times out, then it's not mutt that's the problem.
billo
On Tue, May 28, 2013 at 9:51 AM, Bill Oliver vendor@billoblog.com wrote:
On Mon, 27 May 2013, Richard Vickery wrote:
Sorry for the HTML code; I'm trying to fix it. However, I yum-installed
mutt and attempted to send the following email: [snip]
Does this happen with all email, or only email to fedoraproject?
Here's the obligatory "Hmmm... It works out of the box for me..." I hate reading that when I have a problem, but I feel obligated to let you know.
I'm not a mutt expert -- I have it installed only so I can script broadcast emails from the command line -- but my impression is that it's like pine in that it's a client, not a server, and uses the mail server software you have installed for sending (e.g. sendmail, postfix), and hands off to that. The error message you gave looks to me like a server issue. Do you have another client on that box, like alpine, that does work?
Since the problem is a timeout, it sounds like the server is talking to fedoraproject, which means, to me, that mutt has handed it off.
Here are some things that have screwed me over in the past:
- The mailinglist only accepts mail with your name from one ip address or
domain, and this ain't it. Usually this gets a better error message than timeout, but I've seen it.
- There's an authentication problem (this is the most common for me,
particularly if I'm doing POP/IMAP stuff involving dovecot). Again, this usually gets a better error message than a timeout, but I've seen it there, too. A lot depends on how the servers are configured.
- You do not have your client pointing to the correct server/MTA. I've
done this when I've had multiple domains and multiple servers behind one firewall/router. I've also made the mistake of using "localhost" for my server when I didn't mean to, and had installed, but not set up, sendmail on my laptop as part of a default setup. So, I kept trying to debug my "real" mail server and couldn't find a problem, when in fact my mail client was trying to use my unconfigured laptop as a server. Doh. That's a day out of my life I'll never get back.
- You do not have your domain correctly denoted, and so there's a
mismatch (e.g. you are sending from "billoblog.com" but you are attaching "localdomain.") That can cause some problems later on, though usually for me the error message tells me that the reverse lookup failed at the recipient site. I also get this on occasion when sending mail through an ISP that returns the ISP domain on reverse lookup.
- Fedoraproject's MTA was actually down when you tried to talk to it, and
you just have bad timing. It will clear up later.
Since this is a bit of a touchy mailinglist culture here, I assume you'll get all sorts of flak if you send an empty test email using a direct sendmail or postfix command. Maybe there's a "test" address that the mailinglist advertises for debugging. If so, I'd just do the old tried and true "/usr/sbin/sendmail -v somewhere@somedomain < /dev/null " and see what you get. If *that* times out, then it's not mutt that's the problem.
billo
users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.**org/mailman/listinfo/usershttps://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/**Mailing_list_guidelineshttp://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
I went to a site for configuration which suggested I install these three packages, one of which we (Fedora) have abandoned in 2008 (may not be these packages):
fetchmail msmtp procmail
Thanks for the help,
Sorry again about the HTML,
Richard
On 28May2013 12:57, Richard Vickery richard.vickeryrv@gmail.com wrote: | On Tue, May 28, 2013 at 9:51 AM, Bill Oliver vendor@billoblog.com wrote: | > On Mon, 27 May 2013, Richard Vickery wrote: | > Sorry for the HTML code; I'm trying to fix it. However, I yum-installed | >> mutt and attempted to send the following email: | >> [snip] | > | > Does this happen with all email, or only email to fedoraproject?
In particular, it looks like the mail system could not connect to the fedoraproject smtp service.
Clearly then, it left mutt.
The framing of the bounce message (and the fact that it bounced at all, versus failing to be handed to your mail system) says:
- mutt did deliver the mail to your mail system - mstmp is probably not involved at all
| > I'm not a mutt expert -- I have it installed only so I can script | > broadcast emails from the command line
I, on the other hand, use it as my main mailer.
| > -- but my impression is that it's | > like pine in that it's a client, not a server, and uses the mail server | > software you have installed for sending (e.g. sendmail, postfix), and hands | > off to that. The error message you gave looks to me like a server issue.
All correct.
| > Do you have another client on that box, like alpine, that does work? | > Since the problem is a timeout, it sounds like the server is talking to | > fedoraproject, which means, to me, that mutt has handed it off.
Looks like the server is failing to talk to fedora project. And since it's failed for 4 hours, I'd guess there is a firewall between the system and the fedoraproject SMTP server, not allows access to port 25.
Probably it is his ISP; many block outbound SMTP from client systems to mitigate spam from comprimised clients.
The correct fix here, if this is the case, is to configure the local mail system to send via the ISP's SMTP server.
This setting is called a "smart host" in sendmail and a "relay host" in postfix; what is your local mail system?
| > 5) Fedoraproject's MTA was actually down when you tried to talk to it, and | > you just have bad timing. It will clear up later.
FOr 4 hours? Unlikely. Hence the firewall suggestion.
| I went to a site for configuration which suggested I install these three | packages, one of which we (Fedora) have abandoned in 2008 (may not be these | packages): | | fetchmail msmtp procmail
Fetchmail is for collecting mail. I use getmail myself, but it is irrelevant here.
msmtp is for sending email. Mutt normally hands off the the host's mail system via the "sendmail" command (like _every_ UNIX mail program is supposed to). MSTMP is an alternative; it does direct SMTP delivery for people whose host mail system is no good for whatever reason.
I recommend adjusting your host's mail system; running a local mail system on your own machine is very nice, because all your mail clients can use it and it has a decent queue; you can "send" email when offline, for example, and the mail system will just pick up again when online. It also means when things are wrong the mail isn't lost, just queued.
procmail is a delivery program, used in conjunction with a tool like ftechmail. It delivers fetched messages to mail folders according to a set of rules. Also irrelevant here.
Cheers,
On 28.05.2013, Richard Vickery wrote:
From: Mail Delivery Subsystem MAILER-DAEMON@localhost.localdomain To: richard@localhost.localdomain
Is this routable?
This is not a mutt, but a mailserver issue. You'll have to get your local mailserver configured to accept mail for you.
On 30.05.2013, Heinz Diehl wrote:
[....]
Forget my previous mail, I read too fast. Sorry! Fedoraprojects mailserver has problems.