unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stephen Berman <Stephen.Berman@gmx.net>
To: help-gnu-emacs@gnu.org
Subject: Re: SMTP library problem
Date: Sun, 09 Mar 2008 00:29:15 +0100	[thread overview]
Message-ID: <87r6ekiylw.fsf@escher.local.home> (raw)
In-Reply-To: kzve3x6zmt.fsf@kafka.physik3.gwdg.de

On Sat, 08 Mar 2008 15:47:54 +0100 David <de_bb@arcor.de> wrote:

> Stephen Berman <Stephen.Berman@gmx.net> writes:
>> Ok, I set smtpmail-default-smtp-server to "localhost" and
>> smtpmail-auth-credentials to '(("localhost" 2000 "myusername"
>> "mypassword")), and indeed it did work -- almost.  Since the mail goes
>> through localhost, it gets picked up by the postfix server running on my
>> system.  
>
> You local postfix listens on another port (25), so it should not pick up
> the mail. You must have done something wrong in your smtpmail.el
> configuration. Here's how it should work:
>
> (setq smtpmail-default-smtp-server "localhost")
> (setq smtpmail-smtp-service 2000)
> (require 'smtpmail)
> (setq send-mail-function 'smtpmail-send-it)
> (setq message-send-mail-function 'smtpmail-send-it)
> (setq smtpmail-debug-info t)
> (setq smtpmail-auth-credentials
>       '(("localhost" 2000 "name" "pass")))

When I tried it I had failed to set smtpmail-smtp-service to 2000
(though I did have that port set in smtpmail-auth-credentials), and its
default value is 25, so that explains why postfix intervened.
Unfortunately, when I set it to 2000 as above, it was rejected:

open-network-stream: make client process failed: connection refused,
:name, SMTP, :buffer, *trace of SMTP session to localhost*, :host,
localhost, :service, 2000

I temporarily disabled my firewall in case it was blocking access to
this port, but that didn't help.  Same with other high ports I tried.
So I'm still stuck. :(  Do you know what the problem could be now?

Steve Berman





  reply	other threads:[~2008-03-08 23:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-04 18:09 SMTP library problem James Long
2008-03-05 11:11 ` Stephen Berman
2008-03-05 12:54   ` David
2008-03-05 19:41     ` Stephen Berman
2008-03-05 23:03       ` David
2008-03-06  0:13         ` Stephen Berman
2008-03-06 11:17           ` David
2008-03-07 14:26             ` Stephen Berman
2008-03-07 15:03               ` David
2008-03-07 22:03                 ` Stephen Berman
2008-03-08 14:47                   ` David
2008-03-08 23:29                     ` Stephen Berman [this message]
2008-03-09 12:15                       ` David
2008-03-09 15:35                         ` Stephen Berman
     [not found]                   ` <mailman.8558.1204987691.18990.help-gnu-emacs@gnu.org>
2008-03-09 17:26                     ` Richard G Riley
2008-03-12 20:22                       ` SMTP library problem [RESOLVED] Stephen Berman
     [not found] <mailman.8306.1204670276.18990.help-gnu-emacs@gnu.org>
2008-03-05  6:42 ` SMTP library problem Volkan YAZICI

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=87r6ekiylw.fsf@escher.local.home \
    --to=stephen.berman@gmx.net \
    --cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).