Re: Problem with new installation

2019-10-26 Thread Steve Matzura
I thought this was a directory ownership problem. /var/mail/vmail/... was owned by dovenull:dovecot. In any previous Dovecot+Postfix installation I've had, it's been owned by postfix:postfix. using chown on this directory tree didn't fix the problem: Oct 26 12:54:28 theglobalvoice

Re: Problem with new installation

2019-10-23 Thread Viktor Dukhovni
On Wed, Oct 23, 2019 at 06:11:15PM -0400, Steve Matzura wrote: > OK, I'm a rank amateur at this. I'll take the CNAME record out. Note that despite RFC2181 a non-trivial fraction of domains do set the "exchange" portion of an MX RR to a name that is a CNAME alias. I am not aware of any MTAs that

Re: Problem with new installation

2019-10-23 Thread Steve Matzura
OK, I'm a rank amature at this. I'll take the CNAME record out. My mx record looks OK with "10 mail.{my-FQDN}". I will create an A record called mail which will point to my machine's IP address. I have no NS records at this time. On 10/23/2019 3:41 PM, @lbutlr wrote: On 23 Oct 2019, at

Re: Problem with new installation

2019-10-23 Thread Bill Cole
On 23 Oct 2019, at 14:33, Steve Matzura wrote: [...] On a whim, I change the DNS record for mail from A to CNAME. That's a weird and dangerous whim. Hostnames that are used as the value for MX records MUST have A records and hence MUST NOT have CNAME records. The CNAME *MIGHT* work if done

Re: Problem with new installation

2019-10-23 Thread @lbutlr
On 23 Oct 2019, at 12:33, Steve Matzura wrote: > I change the DNS record for mail from A to CNAME Don’t do that. https://tools.ietf.org/html/rfc2181 The domain name used as the value of a NS resource record, or part of the value of a MX resource record must not be an alias. Not only is

Re: Problem with new installation

2019-10-23 Thread Steve Matzura
Things are definitely getting better, but not enough to make eighteen users happy yet. The manual granting of privileges in MySQL stopped the virtual alias errors entirely. More syslog checking revealed I did not have policyd-spf installed. I took care of that, but neglected to comment

Re: Problem with new installation

2019-10-23 Thread Noel Jones
On 10/23/2019 8:27 AM, Steve Matzura wrote: I've narrowed my problems down to three. Two may be related. 1. Virtual alias table lookup failure: syslog is full of pairs of entries like these: Oct 23 13:03:06 theglobalvoice postfix/trivial-rewrite[23647]: warning: virtual_alias_domains:

Re: Problem with new installation

2019-10-23 Thread Steve Matzura
I've narrowed my problems down to three. Two may be related. 1. Virtual alias table lookup failure: syslog is full of pairs of entries like these: Oct 23 13:03:06 theglobalvoice postfix/trivial-rewrite[23647]: warning: virtual_alias_domains:

Re: Problem with new installation

2019-10-22 Thread Steve Matzura
Thanks, Noel. Very helpful. MySQL is definitely installed and working, but I don't know about Milter, as it was set up by someone else who didn't quite do well by me in educating me in the find points of Postfix management, which is why I am where I am today. I'll get on that and report back.

Re: Problem with new installation

2019-10-22 Thread Noel Jones
On 10/22/2019 1:58 PM, Steve Matzura wrote: I am running a copy of configurations from a running version 2 installation from Ubuntu 14.04, now alive as version 3 on Ubuntu 18.04. I thought I'd be slick and port over all the user mailbox directories in /var/mail/vmail, all the customized

Problem with new installation

2019-10-22 Thread Steve Matzura
I am running a copy of configurations from a running version 2 installation from Ubuntu 14.04, now alive as version 3 on Ubuntu 18.04. I thought I'd be slick and port over all the user mailbox directories in /var/mail/vmail, all the customized .cf's, and the MySQL database. Everything ported