search for: hostdomain

Hi all, Preparing for a replication setup, I read (at the bottom of <http://wiki2.dovecot.org/Replication>) that `dovecot --hostdomain` should give a different output on the two servers. This is not the case for me: both give "localhost". I'm trying to change my configuration to set the hostdomain to another value, but I can't find how to do this. I tried: ? setting the environment variable DOVECOT_HOSTDOMAI...

I am on a server I called "email. But dovecot says i am on sunfire.outputservices.com ------------------------------------ dovecot --hostdomain sunfire.outputservices.com ------------------------------------ I would like to at least get it to say email.outputservices.com. But what I really want it to say is posta.outputservices.com. First where does --hostdomain get it's information so I can clear that up? Then how can I get it...

...uct stack_frame_block *) 0x7fffffffb4e0 #1 0x000000080086a5ec in master_service_env_clean () at master-service.c:534 _data_stack_cur_id = 32767 value = 0x801471056 "TZ CORE_OUTOFMEM CORE_ERROR" #2 0x000000000040df88 in service_process_setup_environment (service=0x8014b11e0, uid=58537, hostdomain=0x801419960 ?mta3.xxx.net") at service-process.c:234 No locals. #3 0x000000000040dd6d in service_process_create (service=0x8014b11e0) at service-process.c:322 uid_counter = 58537 process = (struct service_process *) 0x8008eb2f3 uid = 58537 hostdomain = 0x801419960 ?mta3.xxx.net" pid...

Well, I tried setting the following in /etc/environment and restarting the server: DOVECOT_HOSTDOMAIN="mail.domain.test" After doing so, I verified that the command "dovecot --hostdomain" returned "mail.domain.test" and not "appserver4.domain.com"; however, the email received header still shows: Received: from mail.domain.test by appserver4.domain.com (Dove...

...http://wiki2.dovecot.org/Replication -Enabled SSL for both servers - Dovecot version: 2.2.13 (Debian 8.6) I couldn't find an option to specify the certificate that doveadm should use when connecting to the other server. Both servers have hostnames that are different, as verified by dovecot --hostdomain(as per the instructions) but use a common certificate when emailclients connect to them (high availability setup). Yes, single server login works as expected, been working for the past few years :-). Setting up a custom ssl_client_ca_file doesn't work, since doveadm doesn't know which...

...000, 0x00000000) = 1 55440: Incurred fault #6, FLTBOUNDS %pc = 0xFEC84490 55440: siginfo: SIGSEGV SEGV_MAPERR addr=0xD89CDB4E 55440: Received signal #11, SIGSEGV [default] 55440: siginfo: SIGSEGV SEGV_MAPERR addr=0xD89CDB4E I saw the note in the wiki about "dovecot --hostdomain" so I made sure they do not match. The new target (z-imap2) was built using a zfs clone from the source (z-imap1). I changed the 'hostname', 'instance_name", and 'mail_replica' fields but otherwise they are identical. Did I miss something? Thanks, Tony # 2.2.33....

I have noticed that the name of my private server running dovecot appears in email headers rather than the public-friendly name of my server. Is there a method to specify an alternate server name for the dovecot server to use for itself in the dovecot configuration files? I performed a few Google searches and was not able to find the answer to my question. ------- user at server1:~$ dovecot