Michael:
> Jan 14 08:16:18 deathstar postfix/smtp[16142]: 8CBF11E12B5:
> to=, relay=smtp.gmail.com[173.194.203.108]:587,
> delay=58297, delays=58297/0.05/0.71/0, dsn=4.7.0, status=deferred (SASL
> authentication failed; cannot authenticate to server
> smtp.gmail.com[173.194.203.108]: invalid pa
Hi, can you manually use commands to test the U/P are working from your postfix
server ?
1. Run this to test connectivity to your server
openssl s_client -starttls smtp -connect your.host.name:587
Typical OUTPUT =
250 DSN
quit
221 2.0.0 Bye
On 1/14/19 10:42 AM, Christopher van de Sande wrote:
Just a guess, but are you using App passwords for GMail? It's
possible Gmail is enforcing some 2FA/MFA or otherwise some kind of
"enhanced" authentication.
Even if you aren't using 2FA, it might be worth giving a shot.
I thought this might
On 1/14/19 10:42 AM, Christopher van de Sande wrote:
Just a guess, but are you using App passwords for GMail? It's
possible Gmail is enforcing some 2FA/MFA or otherwise some kind of
"enhanced" authentication.
Even if you aren't using 2FA, it might be worth giving a shot.
Yes, I am using an
Just a guess, but are you using App passwords for GMail? It's possible
Gmail is enforcing some 2FA/MFA or otherwise some kind of "enhanced"
authentication.
Even if you aren't using 2FA, it might be worth giving a shot.
Chris.
On 2019-01-14 11:00 a.m., Michael wrote:
On 1/14/19 8:30 AM, John
On 1/14/19 9:06 AM, Viktor Dukhovni wrote:
On Jan 14, 2019, at 10:28 AM, Fazzina, Angelo wrote:
Hi, I suspect this is wrong
relayhost = [smtp.gmail.com]:587
No, that setting is just fine. Per the subject, the OP is having an issue
with SASL authentication to this relay.
Given:
smtp_sas
> On Jan 14, 2019, at 10:28 AM, Fazzina, Angelo
> wrote:
>
> Hi, I suspect this is wrong
>
> relayhost = [smtp.gmail.com]:587
No, that setting is just fine. Per the subject, the OP is having an issue
with SASL authentication to this relay.
Given:
smtp_sasl_password_maps = hash:/etc/postf
Nick Howitt wrote:
OK. Let's assume I don't have an MX Backup. Then all 30k+ attempted spam
deliveries would have come straight to me. They would all have failed,
initially because of unknown recipient, then, when I added them to the
access list, because of an denied sender. What is the most ef
Michael, I use a gmail account to send system notificacions directly
with s-nail in case postfix may fail, and I had similar problems in the
past with gmail, and it was because:
1.- That gmail account was not configured to accept "less secure"
connections. See https://support.google.com/accoun
On 1/14/19 8:30 AM, John Stoffel wrote:
Michael> I have been using postfix on a local machine for a few years
Michael> to act as a relay for my domain to send email out through
Michael> gmail.
Michael> This has worked well enough, but I noticed recently that I
Michael> had some email queued up a
Michael> I have been using postfix on a local machine for a few years
Michael> to act as a relay for my domain to send email out through
Michael> gmail.
Michael> This has worked well enough, but I noticed recently that I
Michael> had some email queued up and was not getting emails out any
Michae
Hi, I suspect this is wrong
relayhost = [smtp.gmail.com]:587
that looks like typical setup for an email client using IMAP and that is the
config for sending email.
It would require a username and password.
https://support.google.com/mail/answer/7126229?visit_id=636830764979015900-598820322&hl=
Hello,
I have been using postfix on a local machine for a few years to act as a
relay for my domain to send email out through gmail.
This has worked well enough, but I noticed recently that I had some
email queued up and was not getting emails out any longer.
In my mailog, I am seeing the
On Fri, 2019-01-04 at 19:56 +0100, Matus UHLAR - fantomas wrote:
> On 04.01.19 15:23, Christopher R. Gabriel wrote:
> > I have a generator server which injects (via smtp) into postfix,
> > the
> > actual sender, and when burst of delivery happens, the receiving
> > postfix stuck before answering to
14 matches
Mail list logo
