Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Martin Steffen <msteffen@ifi.uio.no>
To: info-gnus-english@gnu.org
Subject: Re: sending email via smtp-server: SSL?/TLS?
Date: Mon, 14 Jul 2008 19:00:40 +0200	[thread overview]
Message-ID: <xk92vdz8jt8n.fsf_-_@shmi.ifi.uio.no> (raw)
In-Reply-To: <ldeb12w178@lisa.anfi.office-on-the.net>

>>>>> "Andrzej" == Andrzej Adam Filip <anfi@onet.eu> writes:

    Andrzej> The page below describes how to make gnus use both STARTTLS
    Andrzej> and SSL: http://www.emacswiki.org/cgi-bin/wiki/GnusGmail

Thanks. Indeed for gmail it works. For the local setting, I am unable to
get that running, even if I think I understood, what the gurus told me
(except that they don't know about emacs). The symptoms are strange:

I have been told, that I can use 

    tls at port 25, or
   
    smpts ssl at port 465

So, I mainly tried 25 (I also tried 465, but mainly I thought 25 is more
standard), and for that, I used 

(setq message-send-mail-function 'smtpmail-send-it
      send-mail-function 'smtpmail-send-it
      smtpmail-starttls-credentials '(("smtp.myorg.com" 25 nil nil))
      smtpmail-auth-credentials '(("smtp.myorg.com" 25 "myname@myorg.com nil)) 
      smtpmail-default-smtp-server "smtp.myorg.com"
      smtpmail-smtp-server "smtp.myorg.com"
      smtpmail-smtp-service 25
      smtpmail-debug-info t
      smtpmail-debug-verb t )

Seem pretty much the same with the config which works for gmail (exept the
server is different). 

Now, when sending an email (either via message-send-mail-function or
send-mail-function), what _should_ happen is that it prompts me for my
password. What actually happens is

>>Cannot connect to smtp.myorg.com:25: Connection timed out
>>Resolving 'smtp.uio.no'...
>>Connecting to 'zzz.xxx.yyy.zz:25'.

Looking at some error traces and the smpt-emacs-trace-buffer, what seems
to happen is that emacs starts the following a process:

gnutls-cli -s smtp.myorg.com -p 25   (***)

Indeed, when I invoke that directly in the shell, the same happens as given
above: basically nothing, until it time-outs.  I guess, that's the reason
of the problem. This belief is supported by the observation, that when I
type (***) when logged on at the university, it opens a TLS-dialogue to the
SMTP-server.

Anyway, that's as far as I got, but now I am stuck (as I think I followed
the instructions of the local administators ("use port 25, use TLS"). What
should I ask them, apart from telling them those observations? Can there be
more authentication hurdles? On some web-pages, there had been mention of
~/.authinfo, is this something, I need to study further?

Thanks, Martin


   




    Andrzej> -- [pl>en Andrew] Andrzej Adam Filip : anfi@priv.onet.pl :
    Andrzej> anfi@xl.wp.pl Dawn, n.: The time when men of reason go to bed.
    Andrzej> -- Ambrose Bierce, "The Devil's Dictionary"

      reply	other threads:[~2008-07-14 17:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-08 17:15 sending email via smtp-server: SSL? Martin Steffen
2008-07-10 15:36 ` Andrzej Adam Filip
2008-07-10 16:10   ` Martin Steffen
2008-07-10 21:47 ` Andrzej Adam Filip
2008-07-14 17:00   ` Martin Steffen [this message]

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=xk92vdz8jt8n.fsf_-_@shmi.ifi.uio.no \
    --to=msteffen@ifi.uio.no \
    --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).