Lewis Perin <[email protected]> writes:
> Matthew Vernon <[email protected]> writes:
>>What it might be worth doing is snaffling a copy of the stunnel
>>configuration file that VM creates, and running stunnel by hand to check
>>it's managing to connect OK.
>
> Not sure how to get this configuration file.
If you have VM running, it'll be in your filesystem. On linux, a file in
/tmp beginning "vm", e.g. /tmp/vm296676064
> Might I have a look at your .vm, by the way? De-identified to be
> sure... And which version of vm are using, may I ask?
8.2.0a. Excerpts from my .vm:
(setq vm-spool-file "/var/spool/mail/matthew")
(setq vm-imap-refer-to-inbox-by-account-name t)
(setq vm-stunnel-program "stunnel4")
(setq vm-folder-directory "~/VMMail")
;speeds up folder loading, in theory...
(setq vm-index-file-suffix "idx")
; need this for imap-FCC to work
(add-hook 'mail-send-hook 'vm-imap-save-composition)
(setq mail-default-headers "IMAP-FCC: Sent")
(setq vm-imap-account-alist
'(
("imap-ssl:mymobilemail.domain:993:inbox:login:username:*" "warwick")
)
)
(setq vm-imap-default-account "warwick")
> By the way, the trace of my IMAP session does say this before I run
> into trouble:
>
> * OK The Microsoft Exchange IMAP4 service is ready.
Hm, that makes me think that stunnel is working.
Regards,
Matthew
--
`O'-----0 `O'---. `O'---. `O'---.
\___| | \___|0-/ \___|/ \___|
| | /\ | | \ | |\ | |
The Dangers of modern veterinary life
