Re: Misconfiguration and documentation clarification help

2019-04-19 Thread ecsd
I am subscribed to the mailing list. I was using the web interface because errors in my mail system ate most of today's list traffic to me and I wanted to be sure I was up to date. It should have occurred to me that the replacements weren't the list's doing (I probably reasoned that the hiding m

Re: Misconfiguration and documentation clarification help

2019-04-19 Thread Philip Paeps
On 2019-04-19 00:28:31 (-0700), Eric Dynamic wrote: Ok, it's nabble doing it (suppressing anything that could be an email when viewing the postfix archives on their service.) People receiving the email (half dozen or so by now) have probably received the markup I intended. Sorry for my confusion.

Re: Misconfiguration and documentation clarification help

2019-04-19 Thread Eric Dynamic
Ok, it's nabble doing it (suppressing anything that could be an email when viewing the postfix archives on their service.) People receiving the email (half dozen or so by now) have probably received the markup I intended. Sorry for my confusion. -- Sent from: http://postfix.1071664.n5.nabble.com

Re: Misconfiguration and documentation clarification help

2019-04-19 Thread Eric Dynamic
God Dammit, what do I have to do to list human-parseable text in contexts where email addresses would be found? I feel like I'm dealing with an editor that writes "e" in place of any vowel I use. My diagnostics are not understandable if I can't write things out. I've never seen such a pest of a cen

Re: Misconfiguration and documentation clarification help

2019-04-19 Thread ecsd
Sorry for the repost, but "[mail hidden]" wiped out what I was trying to show from the logs. Damn, the thing is insistent. I have replaced "@" with " at " and then " xx " to no avail! I am going to replace all "<>" with "[]" and all @ with ?! in hopes to defeat the scanner. == This happens

Re: Misconfiguration and documentation clarification help

2019-04-19 Thread ecsd
Sorry for the repost, but [mail hidden] wiped out what I was trying to show from the logs. I have replaced all email addresses with "user xx domain". == This happens Apr 18 19:34:15 transbay postfix/qmgr[88661]: CC13326F54D2: from=bounce.email.vimeo.com>, size=33062, nrcpt=1 (queue active) Ap

Re: Misconfiguration and documentation clarification help

2019-04-18 Thread ecsd
Sorry for the repost, but [mail hidden] wiped out what I was trying to show from the logs. I have replaced all email addresses with "user at domain". == This happens Apr 18 19:34:15 transbay postfix/qmgr[88661]: CC13326F54D2: from=bounce.email.vimeo.com>, size=33062, nrcpt=1 (queue active) Ap

Re: Misconfiguration and documentation clarification help

2019-04-18 Thread ecsd
This happens Apr 18 19:34:15 transbay postfix/qmgr[88661]: CC13326F54D2: from=, size=33062, nrcpt=1 (queue active) Apr 18 19:34:21 transbay postfix/local[89631]: CC13326F54D2: to=<*ca...@localhost.transbay.net*>, orig_to=<*ca...@transpacific.net*>, relay=local, delay=606, delays=601/0.01/0/5.

Re: Misconfiguration and documentation clarification help

2019-04-18 Thread Viktor Dukhovni
On Thu, Apr 18, 2019 at 03:49:16PM -0700, ecsd wrote: > I set "mydestination = localhost, localhost.transbay.net" and think > "localhost.transbay.net" ought to be able to go away, > though for now it's being used as a key to deliver. Much depends on your setting of "append_dot_mydomain", which u

Re: Viktor Dukhovni Re: Misconfiguration and documentation clarification help

2019-04-18 Thread ecsd
Re: Viktor Dukhovni I took your suggestions about reconfig and things have improved, but there are still anomalies. I set "mydestination = localhost, localhost.transbay.net" and think "localhost.transbay.net" ought to be able to go away, though for now it's being used as a key to deliver (bec

Re: Misconfiguration and documentation clarification help

2019-04-18 Thread Wietse Venema
ecsd: > If I am writing production software (i.e. the end users have a > very vested interest in it working properly), then if I see the > user attempt to give me "empty" for a symbol required to be nonblank > and for which I otherwise have a default value in hand, I would > syslog that I had refus

Re: Misconfiguration and documentation clarification help

2019-04-18 Thread Matus UHLAR - fantomas
On 17.04.19 21:53, ecsd wrote: *(1)* On 4/17/19 12:02 AM, Viktor Dukhovni wrote: On Tue, Apr 16, 2019 at 06:22:12PM -0700, ecsd wrote: (1) the control "check_relay_domains" is not documented. It is obsolete, and should no longer be used. (1) postfix itself says to use it, and (2) it was the o

Re: Misconfiguration and documentation clarification help

2019-04-18 Thread Viktor Dukhovni
On Wed, Apr 17, 2019 at 09:53:14PM -0700, ecsd wrote: > The documentation should list the parameter as long as it exists > (supported by the code, which it is) and say it is deprecated > and not to be used. It is an obsolete and mostly equivalent form of reject_unauth_destination, which only dif

Re: Misconfiguration and documentation clarification help

2019-04-17 Thread ecsd
*(1)* On 4/17/19 12:02 AM, Viktor Dukhovni wrote: On Tue, Apr 16, 2019 at 06:22:12PM -0700, ecsd wrote: (1) the control "check_relay_domains" is not documented. It is obsolete, and should no longer be used. (1) postfix itself says to use it, and (2) it was the only option offered that did not

Re: Misconfiguration and documentation clarification help

2019-04-17 Thread Viktor Dukhovni
On Tue, Apr 16, 2019 at 06:22:12PM -0700, ecsd wrote: > (1) the control "check_relay_domains" is not documented. It is obsolete, and should no longer be used. > I had this: > > smtpd_relay_restrictions = > permit_mynetworks > permit_sasl_authenticated > reject_unauth_destination > perm