No worries. Maybe I made the error in the original. What I had on my test system had the
brackets though, so I don't think so. Hopefully WordPress isn't auto-removing
brackets, but it does still remove leading # characters when I paste stuff into
pre-formatted blocks, so I'm not sure that I would rule out that possiblity.
Anyway, thanks for fixing it.
Gregory Lee Bartholomew
PGP Key ID: 3B67510E
On August 3, 2019 6:48:09 PM UTC, Paul Frields <stickster(a)gmail.com> wrote:
>I fixed this. Not sure how it got messed up since I only deleted some
>the surrounding stuff we talked about, but should be good now.
>On Sat, Aug 3, 2019, 1:30 PM Gregory Bartholomew <
>> It looks like an error may have been introduced during the editing of
>> "Use Postfix" article.
>> I think the values used in password_maps file and the main.cf file
>> to match. Otherwise "WantAuthError" shows up in the logs:
>> Aug 03 12:12:57 eb2027-01.cs.siue.edu
>> delay=0.39, delays=0.03/0.04/0.3/0.02, dsn=5.5.1, status=bounced
>> smtp.gmail.com[188.8.131.52] said: 530-5.5.1 Authentication
>> Learn more at 530 5.5.1
>> f17sm75891337ioc.2 - gsmtp (in reply to MAIL FROM command))
>> I had used "[smtp.gmail.com]:587" in both places because
>> is an SMTP server, not a domain name against which an MX query should
>> run. From the man page:
>> $ man postconf.5 | grep -A 19 ^relayhost
>> relayhost (default: empty)
>> The next-hop destination of non-local mail; overrides
>> domains in recipient addresses. This information is overruled
>> relay_transport, sender_dependent_default_transport_maps,
>> default_transport, sender_dependent_relayhost_maps and with the
>> On an intranet, specify the organizational domain name. If
>> internal DNS uses no MX records, specify the name of the intranet
>> way host instead.
>> In the case of SMTP, specify a domain name, hostname,
>> hostname:port, [hostname]:port, [hostaddress] or [hostaddress]:port.
>> [hostname] turns off MX lookups.
>> If you're connected via UUCP, see the UUCP_README file for
>> relayhost = $mydomain
>> relayhost = [gateway.example.com
>> relayhost = uucphost
>> relayhost = [an.ip.add.ress]
>> Also, the Wikipedia page on MX records points out some limitations
>> the MX protocol:
>> "The MX mechanism does not grant the ability to provide mail service
>> alternative port numbers <https://en.wikipedia.org/wiki/Port_number>
>> does it provide the ability to distribute mail delivery across a set
>> unequal-priority mail servers by assigning a weighting value to each
>> So, I think "[smtp.gmail.com]:587" is the proper value. I think
>> other/newer tricks are used to load balance the smtp.gmail.com
>> and route traffic to the nearest/best server and MX lookups should be
>> avoided in this case. I could be wrong though. I'm not an expert in