Hi,
by hardcoding my GMX mail address in
alpine-2.20/imap/src/c-client/smtp.c, i was able to prove that
my workstation hostname in the MAIL FROM: argument is indeed
the stumblestone which prevented SMTP success with gmx.net.
Whew.
Now i need to find out how to regularly configure the components
Hi,
the trick is to go to the configuration item Customized Headers
and to add a customized From: header. Like
From: Full Name u...@example.com
One can gets this instruction by pressing the help key ?
on the item User Domain and following the here link
in the third paragraph.
By setting my
I suggest you join the alpine discussion list. The
current developer pretty much lives there, and there
is a nice group of subscribers. They talk about this
kind of question all the time.
https://mailman13.u.washington.edu/mailman/listinfo/alpine-info
--
I am not a loony. Why should I be
Quoting Thomas Schmitt (scdbac...@gmx.net):
Hi,
i wrote:
I get a connection to the SMTP server directly by this line
in ~/.pinerc:
smtp-server=mail.gmx.net/ssl/user=my_user...@gmx.net
David Wright wrote:
I assume that you're telling me that this does not work, right?
Yes. It
Hi,
David Wright wrote:
I can direct alpine unencrypted to port 30029 and see the same
effect as with alpine's own encryption via /ssl/ or /tls/.
I'm sorry if I appear to be thick but I get very little sense from
see the same effect as with alpine's own encryption. I can't be
certain
Hi,
Bob Bernstein wrote:
I suggest you join the alpine discussion list.
https://mailman13.u.washington.edu/mailman/listinfo/alpine-info
Will ask there after i managed to get version 2.20 running
from source tarball. (Or after i encountered a showstopper.)
Have a nice day :)
Thomas
--
To
Quoting Thomas Schmitt (scdbac...@gmx.net):
David Wright wrote:
I can direct alpine unencrypted to port 30029 and see the same
effect as with alpine's own encryption via /ssl/ or /tls/.
I'm sorry if I appear to be thick but I get very little sense from
see the same effect as with
Hi,
OK. It would be nice to know which port numbers alpine is trying to
use.
It did connect with explicitely setting port 587 for /tls/.
But i bet that neither port nor encryption protocol is the
problem. If not alpine mimicks a SMTP error 503 then the
connection is good enough to transmit
Le nonidi 9 thermidor, an CCXXIII, David Wright a écrit :
OK. It would be nice to know which port numbers alpine is trying to
use.
strace can tell you that and much more, especially if the encryption is done
by a separate program.
Regards,
--
Nicolas George
signature.asc
Description:
Quoting Thomas Schmitt (scdbac...@gmx.net):
Were I a user of mail.gmx.net, I would ask them.
Futile. They'd want me to use the web interface with lots
of advertising.
Oh dear. Well, could you attack the problem the other way round and
connect alpine to exim, say, on your own machine.
Hi,
Nicolas George wrote:
Do try strace, and if
you know a bit of SMTP, which seems the case, you should be able to spot the
problem in a few minutes.
It's nearly too late in the evening. But (with alpine 2.20 from
source):
read(9, 220 gmx.com (mrgmx102) Nemesis E..., 8192) = 52
Hi,
David Wright a écrit :
It would be nice to know which port numbers alpine is trying to
use.
Nicolas George:
strace can tell you that and much more, especially if the encryption is done
by a separate program.
I do know the port number if stunnel is involved.
Whatever, the ports and
Le nonidi 9 thermidor, an CCXXIII, Thomas Schmitt a écrit :
strace can tell you that and much more, especially if the encryption is done
by a separate program.
Whatever, the ports and encryption are ok. It's alpine's
way of speaking ESMTP and/or Nemesis' unfilfilled ESMTP
expectations which
Hi,
i wrote:
I get a connection to the SMTP server directly by this line
in ~/.pinerc:
smtp-server=mail.gmx.net/ssl/user=my_user...@gmx.net
David Wright wrote:
I assume that you're telling me that this does not work, right?
Yes. It connects, alpine asks for the SMTP password, and then
Quoting Thomas Schmitt (scdbac...@gmx.net):
David Wright wrote:
Port 465 should be encrypted straightaway,
I get a connection to the SMTP server directly by this line
in ~/.pinerc:
smtp-server=mail.gmx.net/ssl/user=my_user...@gmx.net
I assume that you're telling me that this does not
Quoting Thomas Schmitt (scdbac...@gmx.net):
I cannot get alpine mail client to send mail via mail.gmx.net:465.
It reports Bad sequence of commands which is probably SMTP error
503.
My own primitive SMTP client does work (by help of stunnel for SSL).
I'm wondering if there's a mismatch in
Hi,
David Wright wrote:
Port 465 should be encrypted straightaway,
I get a connection to the SMTP server directly by this line
in ~/.pinerc:
smtp-server=mail.gmx.net/ssl/user=my_user...@gmx.net
or via stunnel to mail.gmx.net:465 at port NNN by
Hi,
Celejar wrote:
https://github.com/deanproxy/eMail/issues/7
Yes. Some client glitch like this one combined with increased
pickiness on server side would explain the problem.
A sequence that works is for example
EHLO scdbackup.webframe.org
MAIL FROM:scdbac...@gmx.net
AUTH PLAIN
MAIL
On Fri, 24 Jul 2015 11:49:51 +0200
Thomas Schmitt scdbac...@gmx.net wrote:
Hi,
after a few weeks of settling i got my Debian 8.1 nearly into
the shape of its deceased predecessor (antique SuSE which died
from southbridge radiator pop-off due to material fatigue).
Two problems remain:
19 matches
Mail list logo
