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: Sat, 30 Jul 2022 19:55:18 +0200	[thread overview]
Message-ID: <20220730195518.46448ffa@shinri33> (raw)
In-Reply-To: <87zggru7vt.fsf@tullinup.koldfront.dk>

ok thanks,

first mistake is, that i do have to require smtpmail.
i never did that, but only after that, i see the variables.

unfortunately i do not understand the report:

220 wpxxx.webpack.hosteurope.de ESMTP Host Europe Mail Service Sat, 30
Jul 2022 19:49:55 +0200 250-wpxxx.webpack.hosteurope.de Hello shinri33
[2a02:8108:1200:24dc:4f7b:d279:b926:29ee] 250-SIZE 52428800
250-8BITMIME
250-PIPELINING
250-AUTH PLAIN LOGIN
250-STARTTLS
250 HELP
220 TLS go ahead
250-wpxxx.webpack.hosteurope.de Hello shinri33
[2a02:8108:1200:24dc:4f7b:d279:b926:29ee] 250-SIZE 52428800
250-8BITMIME
250-PIPELINING
250-AUTH PLAIN LOGIN
250 HELP
MAIL FROM:<xx.yy@holnishaus.de> SIZE=301
250 OK
RCPT TO:<zz@holnishaus.de>
550 relay not permitted
QUIT
221 wpxxx.webpack.hosteurope.de closing connection

Process smtpmail deleted


Am Fri, 29 Jul 2022 19:49:10 +0200
Adam Sjøgren <asjo@koldfront.dk> schrieb:

> physiculus writes:
> 
> > Am Thu, 28 Jul 2022 09:34:17 -1000
> > Bob Newell <bobnewell@bobnewell.net> schrieb:  
> 
> >> Have you tried setting smtp-debug-info to t?  
> 
> > yes i have set it, but did not see any difference.  
> 
> Probably because the variable is called smtpmail-debug-info:
> 
> ,----[ C-h v smtpmail-debug-info RET ]
> | smtpmail-debug-info is a variable defined in ‘smtpmail.el’.
> | 
> | Its value is nil
> | 
> | Whether to print info in buffer *trace of SMTP session to
> <somewhere>*. | See also ‘smtpmail-debug-verb’ which determines if
> the SMTP protocol should | be verbose as well.
> | 
> `----
> 
> So try setting that and look at the resulting trace buffer.
> 
> I'm guessing your smtp login is failing, as the mail server is telling
> you that you are not allowed to send email through it (relaying).
> 
> 
>   Best regards,
> 
>     Adam
> 



  reply	other threads:[~2022-07-30 17:55 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 [this message]
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
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=20220730195518.46448ffa@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).