#3977: Something unexpected with account-hook
---------------------+-----------------
  Reporter:  mario   |      Owner:
      Type:  defect  |     Status:  new
  Priority:  major   |  Milestone:
 Component:  mutt    |    Version:
Resolution:          |   Keywords:
---------------------+-----------------

Comment (by kevin8t8):

 It's better to email mutt-users with configuration questions like this,
 unless you are absolutely sure there is a bug in mutt.

 Some points to consider:
 * The account hook specifies a regular expression to match against a
 connection URL.  '''All''' matching account hooks will execute, not just
 the first match.  Be sure the regular expression is not matching more (or
 less) than intended.

 * An account hook executes any time a connection needs to be made:
 including for mailbox polling, the folder browser, fcc's, etc.  The values
 of imap_user and imap_pass are not reset afterwards.  In your first
 example, you don't have an initial default account-hook such as
 {{{
 account-hook . 'unset imap_user; unset imap_pass'
 }}}
   Which means any connection to imapserverB could interfere with
 subsequent imapserverA connection attempts.

--
Ticket URL: <https://dev.mutt.org/trac/ticket/3977#comment:1>
Mutt <http://www.mutt.org/>
The Mutt mail user agent

Reply via email to