Yesterday an email exchange ended seemingly without a reply
to my last message. This morning, mutt reported the reply
present, timestamped appropriately in a mix of UTC and PDT
suggesting it actually reached my host at roughly the right time.
But, there had been no "new mail in this inbox" message at least
six hours after the arrival timestamp.
with Sendmail as the transport agent.[snip]
Can anybody suggest where to look for the source of the problem?[snip]
On Sun, 16 Jul 2023 16:39:51 -0000 (UTC), bob prohaska <bp@www.zefox.net> wrote:
Yesterday an email exchange ended seemingly without a reply[snip]
to my last message. This morning, mutt reported the reply
present, timestamped appropriately in a mix of UTC and PDT
suggesting it actually reached my host at roughly the right time.
But, there had been no "new mail in this inbox" message at least
six hours after the arrival timestamp.
with Sendmail as the transport agent.[snip]
[snip]
Can anybody suggest where to look for the source of the problem?
Does mail arrive in your computer when some Mail Transport Agent
out there on the internet initiates an SMTP conversation on your
port 25?
Or, alternatively, does your computer periodically query
some email service out on the Internet, and use POP or IMAP to
slurp up waiting messages?
Does your incoming email pipeline pass through procmail, which mightNo.
make a useful log-file entry?
Do you have a /var/log/mail.log ?
Peter Pearson <pkpearson@nowhere.invalid> wrote:
On Sun, 16 Jul 2023 16:39:51 -0000 (UTC), bob prohaska wrote:
Yesterday an email exchange ended seemingly without a reply[snip]
to my last message. This morning, mutt reported the reply
present, timestamped appropriately in a mix of UTC and PDT
suggesting it actually reached my host at roughly the right time.
But, there had been no "new mail in this inbox" message at least
six hours after the arrival timestamp.
with Sendmail as the transport agent.[snip]
[snip]
Can anybody suggest where to look for the source of the problem?
Does mail arrive in your computer when some Mail Transport Agent
out there on the internet initiates an SMTP conversation on your
port 25?
Truthfully, I've not paid much attention up to now. I start sendmail
and email simply works. If you're asking whether I use any intermediate
mail hosts, the answer is no.
Or, alternatively, does your computer periodically queryNo.
some email service out on the Internet, and use POP or IMAP to
slurp up waiting messages?
Does your incoming email pipeline pass through procmail, which mightNo.
make a useful log-file entry?
On Tue, 18 Jul 2023 19:01:13 -0000 (UTC), bob prohaska wrote:
Peter Pearson <pkpearson@nowhere.invalid> wrote:
On Sun, 16 Jul 2023 16:39:51 -0000 (UTC), bob prohaska wrote:
Yesterday an email exchange ended seemingly without a reply[snip]
to my last message. This morning, mutt reported the reply
present, timestamped appropriately in a mix of UTC and PDT
suggesting it actually reached my host at roughly the right time.
But, there had been no "new mail in this inbox" message at least
six hours after the arrival timestamp.
with Sendmail as the transport agent.[snip]
[snip]
Can anybody suggest where to look for the source of the problem?
Does mail arrive in your computer when some Mail Transport Agent
out there on the internet initiates an SMTP conversation on your
port 25?
Truthfully, I've not paid much attention up to now. I start sendmail
and email simply works. If you're asking whether I use any intermediate
mail hosts, the answer is no.
Or, alternatively, does your computer periodically queryNo.
some email service out on the Internet, and use POP or IMAP to
slurp up waiting messages?
Does your incoming email pipeline pass through procmail, which mightNo.
make a useful log-file entry?
I'm trying to get an idea of how email arrives in your computer,
which might help illuminate how mutt is supposed to become aware
of a newly arrived message. I'm not very good at this, 'cause
my notions of how email works were formed about 40 years ago.
One possibility is that your computer has a domain name, such as bobscomputer.com, and your email address is bob@bobscomputer.com, and
when someone sends email to that address, their mail-transport agent
looks up bobscomputer.com in the domain-name system to get your IP
address, and then sends you the email message by connecting to port 25
at that IP address and conducting an SMTP conversation. This would mean
that your computer has some kind of mail-transport agent constantly
listening for SMTP connections on port 25.
If your email address is not bob@bobscomputer.com, then it's
probably bob@somethingelse.com (maybe somethingelse is GMail),
and there's some arrangement by which either (a) your computer
periodically contacts somethingelse.com to ask about new messages,
or (b) somethingelse.com has some way to notify your computer
when a new message has arrived for you. I use system (a), and
know almost nothing about systems resembling (b).
Does any of this fit your reality?
I'm pretty sure that 95% of the participants in this newsgroup
know a *lot* more about this than I do. Please, guys, won't one
of you jump in?
My mail host is FreeBSD using
Mutt 2.0.6 (2021-03-06)
On Tue, 18 Jul 2023 19:01:13 -0000 (UTC), bob prohaska wrote:
Peter Pearson <pkpearson@nowhere.invalid> wrote:
On Sun, 16 Jul 2023 16:39:51 -0000 (UTC), bob prohaska wrote:
You ought to read the headers first. And, basically, grep logs fromCan anybody suggest where to look for the source of the problem?
I'm pretty sure that 95% of the participants in this newsgroup know a
*lot* more about this than I do. Please, guys, won't one of you jump
in?
In article <u916gk$qkca$1@dont-email.me>,
bob prohaska <bp@www.zefox.net> wrote:
My mail host is FreeBSD using
Mutt 2.0.6 (2021-03-06)
You might try upgrading to the latest mail/mutt
from ports which has 2.2.10:
<URL:http://www.mutt.org/>
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 546 |
Nodes: | 16 (2 / 14) |
Uptime: | 07:20:26 |
Calls: | 10,388 |
Calls today: | 3 |
Files: | 14,061 |
Messages: | 6,416,822 |
Posted today: | 1 |