Re: Current problems solved, but question...

2020-08-10 Thread cfs_postfix
Viktor Dukhovni wrote .. > The intention is not to suggest you avoid the list. Please keep asking, Since I have been able to thus far fix all of the problems I've had (and indeed mostly caused) myself; activate the complete virtusertable successfully; set up the mean-ugly sendmail access

Re: Current problems solved, but question...

2020-08-10 Thread Viktor Dukhovni
On Mon, Aug 10, 2020 at 08:52:52PM -0400, cfs_post...@insec.lofcom.com wrote: > > Without *context* your question was and remains much too vague. > >Since there is no good way to answer this, I won't. Thank you for >your help; I will try not to bother the list any more than >absolutel

Re: Current problems solved, but question...

2020-08-10 Thread cfs_postfix
Viktor Dukhovni wrote .. > Without *context* your question was and remains much too vague. Since there is no good way to answer this, I won't. Thank you for your help; I will try not to bother the list any more than absolutely necessary in the future. Charlie

Re: Current problems solved, but question...

2020-08-10 Thread Wietse Venema
cfs_post...@insec.lofcom.com: >Yes, I understand this (I never use catchalls), again it was >more a fear of the possibility that a bad rewrite (missed space >in a virtusertable line for example) might cause postfix to do >bad things as it did in this case; and other than my never >

Re: Current problems solved, but question...

2020-08-10 Thread Viktor Dukhovni
On Mon, Aug 10, 2020 at 04:44:34PM -0400, cfs_post...@insec.lofcom.com wrote: > Viktor Dukhovni wrote .. > > > You're indeed falling into the very trap I tried to steer you away > > from, that is, describing problems only in free-from prose, rather > > than clearly stated data (logs, configs, ..

Re: Current problems solved, but question...

2020-08-10 Thread cfs_postfix
Viktor Dukhovni wrote .. > You're indeed falling into the very trap I tried to steer you away > from, that is, describing problems only in free-from prose, rather > than clearly stated data (logs, configs, ...). No, I'm really not, and I'm a little insulted that you would accuse me of such.

Re: Current problems solved, but question...

2020-08-10 Thread Wietse Venema
cfs_post...@insec.lofcom.com: >1) May I assume every delivery must have a fully-qualified email >address, even those to MBOX files on the server? Internally in Postfix, all email addresses are in user@domain form. The null sender address is required by RFCm and is the main exception.

Re: Current problems solved, but question...

2020-08-10 Thread Viktor Dukhovni
On Mon, Aug 10, 2020 at 01:39:55PM -0400, cfs_post...@insec.lofcom.com wrote: >1) May I assume every delivery must have a fully-qualified email >address, even those to MBOX files on the server? This question is too vague to have an answer (I have no idea what you're actually getting at).

Current problems solved, but question...

2020-08-10 Thread cfs_postfix
Folks; The initial problems I was concerned about are now completely fixed, literally by my writing them up for you to read. (I used to call this, "restating the problem," and I'm embarrassed I didn't do exactly that on my own.) Briefly, the second test I made, creating a one-line virtuserta