Ticket #159 (closed defect: fixed)
~/.pinerc sometimes refers to mit.edu/hesiod/imap?
Reported by: | geofft | Owned by: | geofft |
---|---|---|---|
Priority: | low | Milestone: | Karmic Deploy (Canceled) |
Component: | -- | Keywords: | |
Cc: | Fixed in version: | ||
Upstream bug: |
Description
On amd64-test I am running a version of debathena-alpine-config that hardcodes po15, and uses an undebathenified alpine, which is the config we intend to deploy once the other POs support krb5.
If I try to send mail (which wants a sent-mail folder) or manually create a Spamscreen folder, it fails because stock alpine can't parse mit.edu/hesiod/imap.
This config only appears in my own .pinerc:
amd64-test:~ geofft$ grep hesiod /etc/pine.conf amd64-test:~ geofft$ grep hesiod .pinerc folder-collections="MIT Mail" {mit.edu/hesiod/imap}INBOX.[],
So we're going to need to figure out how to override or overwrite the local user's folder-collections when we deploy the krb5 debathena-alpine-config.
Change History
comment:2 Changed 16 years ago by andersk
- Priority changed from major to minor
- Summary changed from ~/.pinerc refers to mit.edu/hesiod/imap to ~/.pinerc sometimes refers to mit.edu/hesiod/imap?
The folder-collections configuration usually lives in the global /etc/pine.conf. It is only copied into your ~/.pinerc if you’ve modified that value, or manually edited ~/.pinerc.
comment:4 Changed 15 years ago by geofft
- Owner set to geofft
- Status changed from new to accepted
Lots of people do that. See -c consult.
comment:5 Changed 15 years ago by geofft
- Status changed from accepted to proposed
r24286 makes the wrapper frob your .pinerc to update away from mit.edu/hesiod/imap.
If/when the po15 config gets deployed, we'll still need the functionality to set the ~/mail directory private, which is presumably best accomplished with a wrapper (if we're no longer patching alpine). Such a wrapper could also frob .pinerc as necessary.