Henning Hucke <
h_hucke+n...@newsmail.aeon.icebear.org> wrote:
>Adam H. Kerman <
a...@chinet.com> wrote:
>>[...]
>>I'm not using a maildrop as the alpine documentation defines it. I have
>>always used IMAP, since I started using the client in the '90s, I think
>>since Pine 2.3. Glancing at the chronology, that makes sense since IMAP
>>had become mature at that point.
>Erm... You *are* using /a maildrop/ since in the end your mails are
>stored somewhere so somewhere they are local and in some format in some
>file. IMAP is the protocol which you use to access your maildrop(s).
From the alpine help text
What is a Mail Drop?
In some situaions it may make sense to have your
mail delivered to one folder (the Mail Drop) and then
when you want to read mail that has been delivered to
the Mail Drop folder Alpine will move it to another
destination folder. Often the Mail Drop will be a
remote folder and messages will be moved from there
to a local destination folder.
One example where this might make sense is if the
Mail Drop folder is accessible only with the POP
protocol. You could designate your POP inbox as the
Mail Drop folder and have Alpine move mail from there
to a local (on the same machine Alpine is running on)
destination folder, where you'll read it.
I do not use this feature.
>. . .
>In your case its IMHO less the question whether or not you use natively
>encrypted versions of a service but whether you use smtp or submission.
>Deliveries of authenticated clients from anywhere shouldn't SPF checked
>on the submission service while all and every delivery should be checked in
>several ways on the smtp service.
I agree with you. It would make my life easier, yes, if SPF weren't
being checked under these circumstances. Nevertheless, my legitimate
messages I send through the SMTP server associated with the domain get
rejected based on my own SPF policy which includes -all.
>>[...]
>>I wasn't sure about that, which is why I asked about it. Carlos thinks
>>that I have been receiving the SPF failure notices.
>As I already stated there is no such thing like an SPF failure notice;
>especialy if we are talking about a mail about a failure.
You are going to have to believe me on this one. I have an archive
folder in which I keep notices that state that the message was not
delivered due to failing SPF policy. If I weren't being notified, I
wouldn't have even known I was affected by this.
>What I suppose is that you are talking about a message which alpine
>displays . . .
No. I am notified in a message.
>>[...]
>>Oh, I know. I don't have privileges over the DNS zone file to revise the
>>SPF record and I haven't persuaded the guy who does to address this.
>Erm... I also wouldn't change my SPF records to just enable you to send
>mail through my smtp service from anywhere.
From anywhere? Don't be ridiculous.
From what I've read about SPF, it's intended that specific hosts be listed,
either by FQDN or IP. Obviously, I have the alpine mail client installed
on a specific host that should be listed in the SPF policy. The guy with
privileges has had his own mail rejected due to SPF policy for the same
reason. He's ignoring the problem. He stopped sending messages with the
business address on From. Instead, he uses his personal email address
to send business messages.
>Instead I would enable you to send your mail through my submission service
>which wouldn't check SPF records but certainly require authentication
>to be allowed to use it (from outside of my own network).
This is irrelevant. The MX host in the receiving network, checking our
own SPF policy, rejects the message even though I was not prevented from
sending through the SMTP server.