help with XFER

[Andrew Morgan]

On Mon, 2 Oct 2006, Sebastian Schäfer wrote:

> one more try... here is the imapd.conf file...
>
> configdirectory: /var/lib/imap
> partition-default: /var/spool/imap
> admins: mailadmin
> sievedir: /var/lib/imap/sieve
> sendmail: /usr/sbin/sendmail
> sasl_pwcheck_method: saslauthd
> sasl_mech_list: PLAIN
> allowusermoves: 1
>
> allowplaintext: 1
> allowapop: 0
> imapidresponse: 0
> lmtp_downcase_rcpt: 1
> lmtp_over_quota_perm_failure: 1
> quotawarn: 90
> singleinstancestore: 1
> username_tolower: 1
> virtdomains: off
> servername: mail4be.dungeon-network.com
>
> mupdate_server: mail4.dungeon-network.com
> mupdate_authname: mupdate
> mupdate_username: mupdate
> mupdate_password: ***
>
> proxyservers: mupdateproxy
> lmtp_admins: mupdateproxy
>
> annotation_db: skiplist
> duplicate_db: skiplist
> mboxlist_db: skiplist
> seenstate_db: skiplist
> subscription_db: flat
> tlscache_db: skiplist
>
> tls_cert_file: /etc/pki/cyrus-imapd/cert.pem
> tls_key_file: /etc/pki/cyrus-imapd/key.pem
> tls_ca_file: /etc/pki/tls/certs/ca.pem

You're missing the proxy_authname: and proxy_password: options which tell 
each backend the credentials to use to connect to each other.  You 
probably already have these defined on your frontend server, but you also 
need them on the backends so they can talk to each other.

 	Andy