unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@elta.co.il>
Subject: Re: SMTP transaction failure
Date: 05 Jan 2004 07:56:35 +0200	[thread overview]
Message-ID: <uisjr546k.fsf@elta.co.il> (raw)
In-Reply-To: <NJOdnYShrae7KWWiU-KYkQ@texas.net> (DJV4@Austin.RR.com)

> From: "David Vanderschel" <DJV4@Austin.RR.com>
> Newsgroups: gnu.emacs.help
> Date: Sun, 4 Jan 2004 18:47:33 -0600
> 
> I really prevent the McAfee stuff from running, emacs can send email OK.
> 
> But why does it foul up emacs and not OE?  Has anyone else seen this?

Perhaps M$ pays McAfee a fee to do that?..

Anyway, I'd look into McAfee's docs to find what options they have for
email (SMTP) connections snooping.  That's assuming this is your
problem; a good net sniffer program should tell.

  reply	other threads:[~2004-01-05  5:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-04  7:53 SMTP transaction failure David Vanderschel
2004-01-04 14:02 ` Kai Grossjohann
2004-01-05  0:47   ` David Vanderschel
2004-01-05  5:56     ` Eli Zaretskii [this message]
2004-01-09 15:37     ` Kai Grossjohann

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=uisjr546k.fsf@elta.co.il \
    --to=eliz@elta.co.il \
    /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).