On Jun 20 you wrote:
> Hello,
>
> On Tue, Jun 19, 2012 at 11:47:53AM -0700, jeremy
> bentham wrote:
> > I can't send mail from my local machine, using
> > my isp's smtp server.
> >
> > I can do it just fine from pine, providing I
> > have started an imap session on one of my isp's
> > machines. (I'm doing this message in pine).
>
> This looks strange. Is this a kind of POP/IMAP
> before SMTP auth? If an IMAP connection from pine
> to an ISP server isn't active, you are unable to
> send from pine too?
In what follows, bear in mind that to me, e-mail programs are
black boxes with a few pinholes in them, allowing me tiny
glimpses of what I am trying to use.
If I'm including irrelevancies/too much, sorry.
What I hope are the relevant lines from my ISP's e-mail help page:
"We are now using what is known as POP-before-SMTP authentication,
after you do a POP3 session from an IP you will be able to send
mail from that IP.
"The old way required identd, unfortunately identd generally is
difficult to make work over NAT which is getting used more and
more as users migrate towards broadband. The old way also didn't
absolutely stop spammers from using our servers to relay spam, if
they were smart enough to run identd they could still relay
through us.
"POP-before-SMTP doesn't allow relaying unless a user
authenticates via POP first."
I found by experimenting that imap works as well as pop: if I
start an imap session before I try to send an e-mail, I can send;
otherwise I can't.
I don't know how to use POP with pine.
from my .pinerc
# incoming-folders are those other than INBOX that receive new messages.
# Folder syntax: optnl-label {optnl-imap-hostname}folder-path
# Use only if you filter incoming email into multiple files or receive
# email on several different machines.
# Example:
# incoming-folders=Consulting {carson.u.washington.edu}filter/to-help,
# Widget-Project {carson.u.washington.edu}filter/to-widget,
# Old-Student-Acct {imap.berkeley.edu}inbox
incoming-folders=Mail/[]
eski {mail.eskimo.com/ssl/novalidate-cert}mail/today
# folder-collections specifies a list of folder collections wherein saved
# messages are stored. The first collection is the default for saves.
# Collection syntax: optnl-label {optnl-imap-hostname}optnl-directory-path[]
# Example:
# folder-collections=Saved-Email {foo.bar.edu}mail/[],
# Widget-Project widget/[], <-- Valid only in Unix Pine
# Local-PC mail\[] <-- Valid only in PC-Pine
folder-collections=Mail/[],
eski {mail.eskimo.com/ssl/novalidate-cert}mail/[t*y],
gmail {imap.gmail.com/ssl}[],
mail/today is a file in my home directory on the ISP's shell
server.
> Probably, mutt closes IMAP before connecting by
> SMTP?
dunno.
> > But, depending on what port I specify in
> > smtp_url, I can either get an instant
> > "connection refused", or, after about ten
> > minutes, "gnutls_handshake: A TLS packet with
> > unexpected length was received."
>
> How does pine do it? By plaintext SMTP? TLS? SSL?
SWAG: SSL
> Which port does it use?
25 or 2525; my .pinerc doesn't specify one, just
"mail.eskimo.com". I also tried 587 in mutt, and gmail has
another one I don't remember right now that I also tried.
> Probably you can try
> tcpdump to see what pine is doing and try to
> replicate it with mutt.
Oh, boy. I don't even have tcpdump _installed_. Probably lotsa
stuff to learn there before I could even understand what to try.
{-:
> I'm sure you can easily hit the same ports and the
> same plain/TLS/SSL settings with .muttrc, but WRT
> IMAP-before-SMTP I'm not that sure.
--
Dave Williams
d...@eskimo.com
