From: tomas@tuxteam.de
To: Paul R <paul.r.ml@gmail.com>
Cc: emacs-pretest-bug@gnu.org, Florian Beck <abstraktion@t-online.de>,
Stefan Monnier <monnier@IRO.UMontreal.CA>
Subject: Re: 23.0.60; emacs-report-bug fails silently
Date: Tue, 3 Jun 2008 10:26:35 +0200 [thread overview]
Message-ID: <20080603082635.GB13718@tomas> (raw)
In-Reply-To: <87fxrvejho.fsf@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, Jun 02, 2008 at 09:15:31PM +0200, Paul R wrote:
> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>
> > [So you mean `smtpmail.el'?] AFAIK many (corporate) firewall
> > configurations (and ISPs) won't allow outgoing connections from
> > clients on port 25.
>
> That's a serious limitation, indeed.
>
> > Instead of this, we should better work on a simple web based bug
> > submission form which can be sent to the bugtracker via Emacs' url
> > library (or emacs-w3m?).
>
> Sending mail through http :)
> In the same spirit, we can make it send mail to an ssl-only smtp
> server listening to 443. This should pass through corporate firewalls.
Or just not tacitly assume that the machine Emacs is running
on is on the 'net (Horrors!).
Maybe the user just wants to generate a bug report, save it on an USB
stick and mail it later. Ask the user, I'd say, then try a couple of
possibilities _if_ she said "dunno", then maybe give up loudly and
offer to save if all those alternatives fail.
Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIRQA7Bcgs9XrR2kYRAoodAJ99RSN0xGLM0X5Dyuo6GujC4kaydQCdGMHO
mszuODt6xtDjsadNQz9+M5Y=
=Gjup
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-06-03 8:26 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 12:59 23.0.60; emacs-report-bug fails silently Florian Beck
2008-05-30 13:59 ` Lennart Borgman (gmail)
2008-05-30 21:42 ` Florian Beck
2008-05-30 21:52 ` Lennart Borgman (gmail)
2008-05-31 0:44 ` Florian Beck
2008-05-31 9:18 ` Lennart Borgman (gmail)
2008-05-31 10:56 ` Reiner Steib
2008-06-01 2:47 ` Florian Beck
2008-06-01 8:04 ` Lennart Borgman (gmail)
2008-05-31 9:53 ` Reiner Steib
2008-06-01 2:54 ` Florian Beck
2008-06-01 7:59 ` Lennart Borgman (gmail)
2008-06-02 0:38 ` Stefan Monnier
2008-06-02 2:13 ` Florian Beck
2008-06-02 2:24 ` Stefan Monnier
2008-06-05 5:27 ` Stefan Monnier
2008-06-05 11:53 ` Florian Beck
2008-06-05 13:58 ` Stefan Monnier
2008-06-05 14:28 ` Florian Beck
2008-06-06 6:01 ` Stefan Monnier
2008-06-06 19:04 ` Richard M Stallman
2008-06-07 1:24 ` Stefan Monnier
2008-06-07 2:28 ` Florian Beck
2008-06-07 14:23 ` Chong Yidong
2008-06-07 7:50 ` Reiner Steib
2008-06-13 4:15 ` Kevin Rodgers
2008-06-13 14:17 ` Stefan Monnier
2008-06-02 8:07 ` Paul R
2008-06-02 18:56 ` Reiner Steib
2008-06-02 19:15 ` Paul R
2008-06-03 8:26 ` tomas [this message]
2008-06-05 5:15 ` Stefan Monnier
2008-06-05 12:41 ` tomas
2008-06-05 16:43 ` Don Armstrong
2008-06-05 19:50 ` Stefan Monnier
2008-06-01 5:36 ` Chong Yidong
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=20080603082635.GB13718@tomas \
--to=tomas@tuxteam.de \
--cc=abstraktion@t-online.de \
--cc=emacs-pretest-bug@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=paul.r.ml@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).