Thx, John, your examples are very helpful. I've taken some more steps to get squared away, added a little architecture. So I see postsuper is how to deal with mailq:
wilma@mail:~$ sudo -i
[sudo] password for wilma:
root@mail:~# which postsuper
/usr/sbin/postsuper
root@mail:~# man postsuper
root@mail:~# mailq
...
18AEEFCBE8 2970 Mon Oct 17 20:14:02 MAILER-DAEMON
(Host or domain name not found. Name service error for name=merrillpje
+nsen.com type=MX: Host not found, try again)
root@merrillpjensen.com
-- 19 Kbytes in 10 Requests.
root@mail:~# postsuper -d 18AEEFCBE8
postsuper: 18AEEFCBE8: removed
postsuper: Deleted: 1 message
root@mail:~# mailq
-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
...
6105EFCBD7 2970 Fri Oct 14 20:16:08 MAILER-DAEMON
(Host or domain name not found. Name service error for name=merrillpje
+nsen.com type=MX: Host not found, try again)
root@merrillpjensen.com
-- 16 Kbytes in 9 Requests.
root@mail:~# postsuper -d ALL
postsuper: Deleted: 9 messages
root@mail:~# mailq
Mail queue is empty
root@mail:~#
I'm glad to be able to do that. I wondered upthread aloud whether these wraiths would live forever. Apparently, these 10 didn't.
aliases in etc
I think I'm getting closer to the mark here.
root@mail:~# vi /etc/hosts
root@mail:~# cat /etc/hosts
...
127.0.1.1 mail.merrillpjensen.com mail
127.0.0.1 localhost
192.168.12.1 mail.merrillpjensen.com mail
...
I don't know which numbers on the left a person can use, and I'm taking my best 2 guesses with:
127.0.1.1 mail.merrillpjensen.com mail
192.168.12.1 mail.merrillpjensen.com mail
, figuring that one or the either might be right, given other settings. We shall see.
Moving on to /etc/alias, I tried to imitate davies' scheme:
root@mail:~# vi /etc/aliases
root@mail:~# cat /etc/aliases
# See man 5 aliases for format
postmaster: sammy
root: sammy
root@mail:~# newaliases
root@mail:~# cat /etc/aliases
# See man 5 aliases for format
postmaster: sammy
root: sammy
Looking at the mx records
So, I think this is where I have a glitch, and you have to start with your service provider, which, in my case is Digital Ocean. I've had the account for long enough that port 25 isn't blocked, which we determined at the end of the last thread. (Which reminds me, what's stevieb up to? If I'm OT, let's have some quality threaddrift.)
This screenshot shows my DNS records as they appear on my account with DO. In creating this MX record, I found myself unable to enter anything other than the @ character for the hostname, which outputs it like you see.
Q1) Is it plausibly correct?
I think write-ups are good for people. I was about to lay out all the host commands I had spewed out that hadn't worked:
, and then I hit paydirt looking at my own data during the writeup:
root@mail:~# host -t MX www.merrillpjensen.com
www.merrillpjensen.com mail is handled by 5 mail.merrillpjensen.com.
root@mail:~#
Q2) Is it plausibly correct? Here is what the hostname command reveals:
root@mail:~# man hostname
root@mail:~# hostname -f
mail.merrillpjensen.com
root@mail:~# hostname -d
merrillpjensen.com
root@mail:~#
other architecture
I checked the architecture for /etc/bash.bashrc:
root@mail:~# cat /etc/bash.bashrc
# System-wide .bashrc file for interactive bash(1) shells.
...
export MAIL=~/Maildir
root@mail:~#
This looks right to me. Changed this:
postconf -e "mydestination = mail.merrillpjensen.com, localhost.locald
+omain, localhost"
Q3) Is it plausibly correct?
I thought there was a utility to add the appropriate subdirectories of Maildir, but I couldn't hook it up, so I did it on the command line:
cd /home/sammy/Maildir/
mkdir new cur temp
I have tried everything but the kitchen sink with telnet, I still don't have anything getting to sammy:
root@mail:/home/sammy/Maildir# telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 mail ESMTP Postfix (Ubuntu)
mail from:<root@www.merrillpjensen.com>
rcpt to:<sammy@www.merrillpjensen.com>
data
To: sammy@www.merrillpjensen.com
From: root@www.merrillpjensen
Subject: Hey my first email
This is my first email on debian postfix after installing configuring
+it.
It was easy. (like hell)
Sounds good!250 2.1.0 Ok
250 2.1.5 Ok
354 End data with <CR><LF>.<CR><LF>
.
quit
.
250 2.0.0 Ok: queued as 8BC30FCD5B
quit
221 2.0.0 Bye
Connection closed by foreign host.
root@mail:/home/sammy/Maildir# ll -R
.:
total 20
drwxrwx--x 5 sammy mymail 4096 Oct 18 05:27 ./
drwxr-x--- 3 sammy sammy 4096 May 18 22:18 ../
drwxr-xr-x 2 sammy mymail 4096 Oct 18 05:27 cur/
drwxr-xr-x 2 sammy mymail 4096 Oct 18 05:27 new/
drwxr-xr-x 2 sammy mymail 4096 Oct 18 05:27 temp/
./cur:
total 8
drwxr-xr-x 2 sammy mymail 4096 Oct 18 05:27 ./
drwxrwx--x 5 sammy mymail 4096 Oct 18 05:27 ../
./new:
total 8
drwxr-xr-x 2 sammy mymail 4096 Oct 18 05:27 ./
drwxrwx--x 5 sammy mymail 4096 Oct 18 05:27 ../
./temp:
total 8
drwxr-xr-x 2 sammy mymail 4096 Oct 18 05:27 ./
drwxrwx--x 5 sammy mymail 4096 Oct 18 05:27 ../
root@mail:/home/sammy/Maildir# mailq
-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
8BC30FCD5B* 479 Wed Oct 19 06:33:56 root@www.merrillpjensen.com
sammy@www.merrillpjensen.com
7AFE9FCD5F 966 Tue Oct 18 20:00:01 root@merrillpjensen.com
(Host or domain name not found. Name service error for name=merrillpje
+nsen.com type=MX: Host not found, try again)
root@merrillpjensen.com
0AB56FCD57 460 Tue Oct 18 05:50:04 root@merrillpjensen.com
(Host or domain name not found. Name service error for name=merrillpje
+nsen.com type=MX: Host not found, try again)
sammy@merrillpjensen.com
-- 1 Kbytes in 3 Requests.
root@mail:/home/sammy/Maildir#
That last try looked particularly wrong with the www in it, but I have previous versions failing without that. I wouldn't say that I have a strong handle on fqdn:
THE FQDN
The FQDN (Fully Qualified Domain Name) of the system is the n
+ame that
the resolver(3) returns for the host name, such as, ursula.exam
+ple.com.
It is usually the hostname followed by the DNS domain name (
+the part
after the first dot). You can check the FQDN using hostname --
+fqdn or
the domain name using dnsdomainname.
You cannot change the FQDN with hostname or dnsdomainname.
The recommended method of setting the FQDN is to make the hos
+tname be
an alias for the fully qualified name using /etc/hosts, DNS,
+or NIS.
For example, if the hostname was "ursula", one might have a
+ line in
/etc/hosts which reads
127.0.1.1 ursula.example.com ursula
Technically: The FQDN is the name getaddrinfo(3) returns for t
+he host
name returned by gethostname(2). The DNS domain name is the pa
+rt after
the first dot.
Therefore it depends on the configuration of the resolver (usu
+ally in
/etc/host.conf) how you can change it. Usually the hosts file i
+s parsed
before DNS or NIS, so it is most common to change the
+FQDN in
/etc/hosts.
I was hoping to break through with this effort, but I seem to have come up short again.
|