Dan Mahoney wrote
>> Here's an SMTP DANE validator that I use when I make changes to my server.
>> https://dane.sys4.de/
>>
>> I'm not sure if it is just what you're looking for, though.
>
> No, I am looking for a server to which I can send mail to make sure DANE is
> being looked up and used
On Mon, Jan 03, 2022 at 10:39:49PM -0500, post...@ptld.com wrote:
>smtp_bind_address6 = []
>
> If I remove the [ ] around the IPv6 the error goes away. The manual
> says [ ] is supported. Is my version is too old? Im okay with not
> using [ ].
Indeed the implementation does not match the doc
Ken Wright:
> On Mon, 2022-01-03 at 20:50 -0500, Viktor Dukhovni wrote:
> > On Mon, Jan 03, 2022 at 08:02:20PM -0500, Ken Wright wrote:
> >
> > > $ sudo chmod g+s /usr/sbin/postdrop
> > > $ ls -la /usr/sbin/postdrop
> > > -r-xr-sr-x 1 postfix postdrop 22808 Sep? 7 02:58 /usr/sbin/postdrop
> > >
>
post...@ptld.com:
> If i use these settings
>inet_interfaces = all
>inet_protocols = all
>smtp_bind_address =
>smtp_bind_address6 =
>smtp_address_preference = any (* Not actually included in main.cf,
> relying on 'any' as the default)
>
> Then most of the time email being
Am 04.01.2022 um 02:02 schrieb Ken Wright:
$ sudo chmod g+s /usr/sbin/postdrop
$ ls -la /usr/sbin/postdrop
-r-xr-sr-x 1 postfix postdrop 22808 Sep 7 02:58 /usr/sbin/postdrop
Wietse, is this what's expected?
AFAICT you are lacking write permission for the user.
--
Alex JOST
Alex JOST:
> Am 04.01.2022 um 02:02 schrieb Ken Wright:
> > $ sudo chmod g+s /usr/sbin/postdrop
> > $ ls -la /usr/sbin/postdrop
> > -r-xr-sr-x 1 postfix postdrop 22808 Sep 7 02:58 /usr/sbin/postdrop
> >
> > Wietse, is this what's expected?
>
> AFAICT you are lacking write permission for the user
My postfix setup sends all emails through google.
Now trying to route some of them through dreamhost.
AUTH from [gmail-smtp.l.google.com]:587
250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH
AUTH from [smtp.dreamhost.com]:587
250-AUTH PLAIN LOGIN
250-AUTH=PLAIN LOGIN
To se
> out of the box, Postfix will randomly deliver over IPv4 or IPv6 as
> both addresses have the same MX preference.
>
> To try an IPv6 address before IPv4 with the same MX preference, use
> "smtp_address_preference = ipv6". But I see no benefits for this
> specific case, and it will hinder error re
Am 04.01.2022 um 16:25 schrieb Wietse Venema:
Alex JOST:
Am 04.01.2022 um 02:02 schrieb Ken Wright:
$ sudo chmod g+s /usr/sbin/postdrop
$ ls -la /usr/sbin/postdrop
-r-xr-sr-x 1 postfix postdrop 22808 Sep 7 02:58 /usr/sbin/postdrop
Wietse, is this what's expected?
AFAICT you are lacking writ
post...@ptld.com:
> The part i am still confused about is the perceived behavior
> difference between
>
>inet_interfaces = all
>inet_interfaces = ipv4, ipv6
inet_interfaces takes 'all' or a list of IP addresses. It will also
take hostnames but such configuration is fragile; however if you
Henrique Martins:
> Redirection through google or dreamhost is handle through
> relayhost = [gmail-smtp.l.google.com]:587
> smtp_tls_policy_maps = hash:/etc/postfix/tls_policy
> smtp_use_tls = yes
> smtp_tls_security_level = may
> smtp_sasl_auth_enable = yes
> smtp_sasl_password_maps =
Wietse Venema:
> Henrique Martins:
> > Redirection through google or dreamhost is handle through
> > relayhost = [gmail-smtp.l.google.com]:587
> > smtp_tls_policy_maps = hash:/etc/postfix/tls_policy
> > smtp_use_tls = yes
> > smtp_tls_security_level = may
> > smtp_sasl_auth_enable = yes
>
wv> Use sender_dependent_default_transport_maps, and create SMTP delivery
wv> transports in master.cf each with their own smtp_sasl_mechanism_filter
wv> setting.
wv> In the lookup result, specify an SMTP delivery transport:host.
wv> Postfix expects the same syntax as "default_transport".
Thanks!
My Postfix woes continue. Now I'm getting this error message:
Jan 4 19:08:47 grace postfix/smtps/smtpd[17286]: fatal: no SASL
authentication mechanisms
This is starting to get old.
Ken
On Tue, 2022-01-04 at 07:30 -0500, Wietse Venema wrote:
> Ken Wright:
> > Okay, I ran sudo postfix set-permissions. It ran with no trouble
> > whatsoever; no errors, warnings, nothing. Still getting the exact
> > same messages in mail.log.
>
> Then your file system is mounted with 'nosuid' optio
On 05/01/2022 10:50 am, Ken Wright wrote:
> Jan 4 19:08:47 grace postfix/smtps/smtpd[17286]: fatal: no SASL
> authentication mechanisms
>
> This is starting to get old.
Posting your running config might get you some help Ken.
Expecting good help otherwise may be a long shot.
Mal
Ken Wright:
> On Tue, 2022-01-04 at 07:30 -0500, Wietse Venema wrote:
> > Ken Wright:
> > > Okay, I ran sudo postfix set-permissions.? It ran with no trouble
> > > whatsoever; no errors, warnings, nothing.? Still getting the exact
> > > same messages in mail.log.
> >
> > Then your file system is m
On Tue, Jan 04, 2022 at 07:20:43PM -0500, Ken Wright wrote:
> My Postfix woes continue. Now I'm getting this error message:
>
> Jan 4 19:08:47 grace postfix/smtps/smtpd[17286]: fatal: no SASL
> authentication mechanisms
The selected SASL backend (Cyrus or Dovecot) is not configured to
support
On Tue, 2022-01-04 at 20:49 -0500, Viktor Dukhovni wrote:
> On Tue, Jan 04, 2022 at 07:20:43PM -0500, Ken Wright wrote:
>
> > My Postfix woes continue. Now I'm getting this error message:
> >
> > Jan 4 19:08:47 grace postfix/smtps/smtpd[17286]: fatal: no SASL
> > authentication mechanisms
>
>
On Tue, Jan 04, 2022 at 09:14:45PM -0500, Ken Wright wrote:
> > > Jan 4 19:08:47 grace postfix/smtps/smtpd[17286]: fatal: no SASL
> > > authentication mechanisms
> >
> > The selected SASL backend (Cyrus or Dovecot) is not configured to
> > support any usable SASL mechanisms.
>
> kwright@grace:~$
On Tue, 2022-01-04 at 21:37 -0500, Viktor Dukhovni wrote:
>
> Is "Dovecot" configured to create the /var/spool/postfix/private/auth
> socket? Did that happen? Is "Dovecot" willing to support the
> expected SASL mechanisms (typically "PLAIN")?
>
> I have:
>
> service auth {
> unix_lis
On Tue, Jan 04, 2022 at 09:57:55PM -0500, Ken Wright wrote:
> > Is "Dovecot" configured to create the /var/spool/postfix/private/auth
> > socket? Did that happen? Is "Dovecot" willing to support the
> > expected SASL mechanisms (typically "PLAIN")?
> >
> > I have:
> >
> > service auth {
>
> That's what I have, except my passdb driver is sql. Could that be the
> problem?
To test if you have dovecot configured correctly for auth you can use the
doveadm tool.
Examples:
doveadm auth lookup
doveadm auth test
> That's what I have, except my passdb driver is sql. Could that be the
> problem?
Following the lines of what Viktor said about creating the auth socket. You
only confirmed you have the service auth{...} in dovecot config. Did you
confirm the socket is being physically created? If there are p
On Tue, 2022-01-04 at 22:29 -0500, post...@ptld.com wrote:
> > That's what I have, except my passdb driver is sql. Could that be
> > the problem?
>
>
> Following the lines of what Viktor said about creating the auth socket.
> You only confirmed you have the service auth{...} in dovecot config.
>
On Tue, 2022-01-04 at 21:14 -0500, Ken Wright wrote:
> flags=DRhu
> user=vmail argv=/usr/bin/maildrop -d ${recipient}
> uucp unix - n n - - pipe
> flags=Fqhu
> user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient)
> ifmail unix -
On Tue, 2022-01-04 at 22:58 -0500, Jim Popovitch wrote:
> Those lines above look debian'ish to me. If you are running debian,
> then make sure you have libsasl2-2, libsasl2-modules and libsasl2-
> modules-db installed.
Definitely debian-ish. Ubuntu. 20.04, to be specific. I checked, and
those l
27 matches
Mail list logo
