From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: Sven Bretfeld <sven.bretfeld@gmx.ch>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Gnus and outgoing Mail
Date: Sun, 09 Dec 2007 15:33:19 +0100 [thread overview]
Message-ID: <87ejdw9bv4.fsf@thievol.homelinux.org> (raw)
In-Reply-To: <87k5nonec0.fsf@kamaloka.dhatu> (Sven Bretfeld's message of "Sun, 09 Dec 2007 15:16:15 +0100")
Sven Bretfeld <sven.bretfeld@gmx.ch> writes:
> Hi Thierry
>
> Thierry Volpiatto <thierry.volpiatto@gmail.com> writes:
>
>> Hi, if you write
>>
>> (setq smtpmail-auth-credentials
>> '(("mail.gmx.net" 25 "***" "***")))
>>
>> that mean you want to use starttls and you need to set
>> mail and password instead of "***" "***" and "mail.gmx.net"
>> must be the adress of an smtp server.
>
> Yes, gmx requires authentication, but, according to their
> documentation, doesn't require (isn't able to understand) a secure
> transmission of the login-data. I was thinking this is what is called
> TLS. Gmx doesn't -- of course, grrr -- have a configuration
> instruction for Gnus on its homepage. In the documentation for
> Thunderbird, they say "Use Secure Transmission (TSL/SSL)" must _not_
> be enabled. Anyway, username and password have to be transmitted.
>
> That the "***"'s have to be username and password is clear. I only
> masked them for the posting. mail.gmx.net is the SMTP-Server.
>
>> And are you sure your friend have some MTA installed
>> (i use nbsmtp)
>
> We both have exim4 as the system's MTA. His is not configured. Mine is
> configured for my usual smtp server which is different from gmx (I use
> the one provided by my internet provider). But does Gnus really make
> use of exim4? I was thinking it comes with its own MTA. How else can
> it be explained that I could just edit my .gnus.el for using the
> SMTP-server of gmx yesterday -- which was working -- without changing
> my exim4 configuration?
>
> Thanks for your help
>
> Sven
Gnus use sendmail to send mails:
If you have exim on your system it will use exim, if you have postfix or
anything else it will use that.
--
A + Thierry
Pub key: http://pgp.mit.edu
next prev parent reply other threads:[~2007-12-09 14:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-08 23:39 Gnus and outgoing Mail Sven Bretfeld
2007-12-09 7:24 ` Thierry Volpiatto
2007-12-09 14:16 ` Sven Bretfeld
2007-12-09 14:33 ` Thierry Volpiatto [this message]
2007-12-09 14:38 ` Reiner Steib
[not found] <mailman.4774.1197157208.18990.help-gnu-emacs@gnu.org>
2007-12-09 1:38 ` Exal de Jesus Garcia Carrillo
2007-12-09 16:51 ` Sven Bretfeld
2007-12-09 17:27 ` Thierry Volpiatto
2007-12-09 18:02 ` Sven Bretfeld
2007-12-09 18:35 ` Thierry Volpiatto
[not found] ` <mailman.4798.1197219115.18990.help-gnu-emacs@gnu.org>
2007-12-09 20:26 ` Exal de Jesus Garcia Carrillo
2007-12-10 0:45 ` Sebastian Tennant
2007-12-10 1:16 ` Sven Bretfeld
[not found] ` <mailman.4819.1197249427.18990.help-gnu-emacs@gnu.org>
2007-12-10 5:16 ` Exal de Jesus Garcia Carrillo
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ejdw9bv4.fsf@thievol.homelinux.org \
--to=thierry.volpiatto@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=sven.bretfeld@gmx.ch \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).