Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: physiculus <physiculus@gmail.com>
To: "Adam Sjøgren" <asjo@koldfront.dk>
Cc: info-gnus-english@gnu.org
Subject: Re: Need help; cannot send email in gnus and emacs anymore; 550 relay not permitted
Date: Sun, 31 Jul 2022 09:32:48 +0200	[thread overview]
Message-ID: <20220731093248.43221d3a@shinri33> (raw)
In-Reply-To: <87mtcq2w2o.fsf@tullinup.koldfront.dk>

Am Sat, 30 Jul 2022 22:18:39 +0200
Adam Sjøgren <asjo@koldfront.dk> schrieb:

> physiculus writes:
> 
> >> Do you have username and password configured in clawsmail for the
> >> outgoing (smtp) mail servers?  
> 
> > yes it is configured inside clawsmail.  
> 
> Ok, so that's at least a difference between "working client" and
> "non-working client".
> 
> > but i do not know, if gnus/smtpmail reads the data from this file.
> > is it possible to log deeper if sending mail?  
> 
> I would expect the smtp trace buffer to have lines about logging in
> (AUTH) if it is.
> 
hello again,
i just try it again with my gmail account.
but for me, nothing that i understand why it does not work.
here is the trace:
220 smtp.gmail.com ESMTP
o21-20020a170906775500b0072f9dc2c246sm3720562ejn.133 - gsmtp
250-smtp.gmail.com at your service,
[2a02:8108:1200:24dc:4f7b:d279:b926:29ee] 250-SIZE 35882577 250-8BITMIME
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-CHUNKING
250 SMTPUTF8
220 2.0.0 Ready to start TLS
250-smtp.gmail.com at your service,
[2a02:8108:1200:24dc:4f7b:d279:b926:29ee] 250-SIZE 35882577
250-8BITMIME
250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-CHUNKING
250 SMTPUTF8
MAIL FROM:<xxx@googlemail.com> SIZE=308
530-5.7.0 Authentication Required. Learn more at
530 5.7.0  https://support.google.com/mail/?p=WantAuthError
o21-20020a170906775500b0072f9dc2c246sm3720562ejn.133 - gsmtp QUIT
221 2.0.0 closing connection
o21-20020a170906775500b0072f9dc2c246sm3720562ejn.133 - gsmtp

Process smtpmail deleted

the mail adress is the same as in my authinfo.gpg file.
could you see, which step brings the error?
or is it possible to deeper log the connection?

> Does what you have put after "machine" in authinfo match what you have
> in your posting styles as the smtp servers?
> 
> 
>   Best regards,
> 
>     Adam
> 



  reply	other threads:[~2022-07-31  7:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27 14:09 physiculus
2022-07-27 14:47 ` Eric S Fraga
2022-07-27 14:56 ` physiculus
2022-07-27 21:13   ` Bob Newell
2022-07-28  8:44     ` physiculus
2022-07-28 19:34       ` Bob Newell
2022-07-29 17:39         ` physiculus
2022-07-29 17:49           ` Adam Sjøgren
2022-07-30 17:55             ` physiculus
2022-07-30 18:50               ` Adam Sjøgren
2022-07-30 19:05                 ` physiculus
2022-07-30 19:55                   ` Adam Sjøgren
2022-07-30 20:05                     ` physiculus
2022-07-30 20:18                       ` Adam Sjøgren
2022-07-31  7:32                         ` physiculus [this message]
2022-07-31  9:35                           ` Adam Sjøgren
2022-07-31 17:18                             ` physiculus
2022-07-31 17:49                             ` physiculus
2022-07-31 21:09                               ` Adam Sjøgren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220731093248.43221d3a@shinri33 \
    --to=physiculus@gmail.com \
    --cc=asjo@koldfront.dk \
    --cc=info-gnus-english@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).