From: Fabrice Popineau <Fabrice.Popineau@supelec.fr>
Cc: ding@gnus.org
Subject: sending attachements via gnus
Date: 13 Jun 2000 15:53:57 +0200 [thread overview]
Message-ID: <1z21g00a.fsf@supelec.fr> (raw)
The patches by Mike Alexander have made things working better, but
still I can't get to send say a 2Mb file attached.
Now after some investigation in smtpmail (since this is what I'm using
on NT), I wonder where the problem really is. Can anybody confirm
using any Unix (or maybe Cygwin ? ) version of xemacs that smtpmail is
able to send a large buffer ?
It seems that the loop sending the buffer line by line aborts before
the end (smtpmail-send-data function), and then a QUIT is sent to the
smtp server, but with no answer (the smtp server is waiting for a '.',
isn't it ?). So the whole thing hang.
Any suggestion ? I'll try to do more investigation when I will have time.
--
Fabrice Popineau
next reply other threads:[~2000-06-13 13:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-13 13:53 Fabrice Popineau [this message]
2000-06-13 17:36 ` WJCarpenter
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=1z21g00a.fsf@supelec.fr \
--to=fabrice.popineau@supelec.fr \
--cc=ding@gnus.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).