On Mon, Jun 27, 2022 at 02:15:18PM -0700, Derek B. Noonburg wrote:
> > If you can convince the user to surrender the alias management to you,
> > then you instead configure:
> >
> >
> > owner-user: user
> > user: some.a...@gmail.com
> >
> > And presto magic, email to gmail will be
On 6/27/22 17:15, Derek B. Noonburg wrote:
> On Thu, 23 Jun 2022 20:13:10 -0400
> Viktor Dukhovni wrote:
>
>> On Thu, Jun 23, 2022 at 02:43:02PM -0700, Derek B. Noonburg wrote:
>>
>>> I'm running postfix to handle email for several users. One of them
>>> has a .forward file that points to a
On Thu, 23 Jun 2022 20:13:10 -0400
Viktor Dukhovni wrote:
> On Thu, Jun 23, 2022 at 02:43:02PM -0700, Derek B. Noonburg wrote:
>
> > I'm running postfix to handle email for several users. One of them
> > has a .forward file that points to a gmail address. Gmail's servers
> > are rejecting
On 2022-06-27 at 09:51:16 UTC-0400 (Mon, 27 Jun 2022 08:51:16 -0500)
Rob McGee
is rumored to have said:
On 2022-06-26 21:23, Alex wrote:
Hi,
I was surprised to see I received an email with localhost.localdomain
as the envelope sender. It was a legitimate email, but not from my
This would
On 2022-06-26 21:23, Alex wrote:
Hi,
I was surprised to see I received an email with localhost.localdomain
as the envelope sender. It was a legitimate email, but not from my
This would have been stopped by
http://www.postfix.org/postconf.5.html#reject_unknown_sender_domain
(unless you have
Maurizio Caloro:
>
> On 27.06.2022 00:24, Wietse Venema wrote:
> > Maurizio Caloro:
> >
> > setup also opendkim and will appear now the error "
> >> *key data is not secure: / is writeable and owned by uid 110 which is
> >> not the executing uid (115)* *or the superuser*"
> >> it's seem that i
On Mon, Jun 27, 2022 at 07:19:59AM +0200, Maurizio Caloro
wrote:
> On 27.06.2022 00:24, Wietse Venema wrote:
> > Maurizio Caloro:
> >
> > setup also opendkim and will appear now the error "
> > > *key data is not secure: / is writeable and owned by uid 110 which
> > > is not the executing uid
On Mon, Jun 27, 2022 at 12:00:20AM +0200, Maurizio Caloro
wrote:
>
> setup also opendkim and will appear now the error "key data is not secure: /
> is writeable and owned by uid 110 which is not the executing uid (115)"
> it's seem that i have permission issue?
>
> # opendkim -V
>
On 27.06.22 00:00, Maurizio Caloro wrote:
setup also opendkim and will appear now the error "key data is not
secure: / is writeable and owned by uid 110 which is not the executing
uid (115)"
this looks like you have set owner of root directory to non-root user
it's seem that i have
On Jun 25 2022 at 6:05 PM Jaroslaw Rafa wrote:
Because with such a complicated thing as configuring
a MTA (yes, it *is* complicated) you should never rely
on recipes. You should rely on reading thoroughly
the MTA documentation
I'm not sure what *exactly* do you mean by a "catch-all"
and what
10 matches
Mail list logo
