Displaying 12 results from an estimated 12 matches similar to: "dovecot --hostdomain issue"
2016 Sep 25
2
Setting 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
2014 Sep 18
1
LDAP and dovecot
At my company I have users who are now becoming remote and using their mobile devices for email. I use Solaris 10 10/09 s10x_u8wos_08a X86 as an operating system and I now need a more secure email solution than the generic sendmail / imap solution.
I want to use dovecot and postfix because I have read good reports on these products for ease of setup and use. I need to use both with SSL
2023 Oct 10
17
[Bug 3627] New: openssh 9.4p1 does not see RSA keys in know_hosts file.
https://bugzilla.mindrot.org/show_bug.cgi?id=3627
Bug ID: 3627
Summary: openssh 9.4p1 does not see RSA keys in know_hosts
file.
Product: Portable OpenSSH
Version: 9.4p1
Hardware: SPARC
OS: Solaris
Status: NEW
Severity: major
Priority: P5
Component: ssh
2016 Aug 23
2
Change dovecot hostname
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
2015 May 22
0
v2.2.18 released
On 05/22/15 12:24, James wrote:
> On 22/05/2015 16:27, dovecot at outputservices.com wrote:
>> I am just starting out and trying to get dovecot and postfix working in Solaris 10 environment.
>>
>> Went from 2.2.15 to 2.2.17, then to 2.2.18
>>
>> Both version 2.2.17 & 2.2.18 gave this same error. 2.2.15 does not.
>>
>>
2014 Dec 09
1
Required SSL with exceptions
On 12/08/14 23:50, SATOH Fumiyasu wrote:
> Hi,
>
> At Mon, 08 Dec 2014 16:01:43 -0600,
> List wrote:
>> Essentially we would like to host IMAP with SSL enforced for any connections coming from anywhere except the subnet where our other mail servers reside. The idea is to not install a local instance of dovecot on the webmail/carddav/caldav servers to reduce the number of
2015 May 22
1
v2.2.18 released
I am just starting out and trying to get dovecot and postfix working in Solaris 10 environment.
Went from 2.2.15 to 2.2.17, then to 2.2.18
Both version 2.2.17 & 2.2.18 gave this same error. 2.2.15 does not.
-----------------------------------
May 15 09:27:37 master: Info: Dovecot v2.2.18 starting up for imap
May 15 09:27:37 ssl-params: Info: Generating SSL parameters
May 15 09:27:37
2016 Aug 19
3
Change dovecot hostname
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
2016 Mar 03
2
Dovecot 2.2.21 - segfault
pid 31943 (dovecot), uid 0: exited on signal 11 (core dumped)
dovecot --version
2.2.21 (5345f22)
uname -a
FreeBSD 10.3-BETA2 #0 r295966M: amd64
bt full
#0 0x00000008008eb037 in t_push (marker=0x0) at data-stack.c:133
133 data-stack.c: No such file or directory.
in data-stack.c
(gdb) bt full
#0 0x00000008008eb037 in t_push (marker=0x0) at data-stack.c:133
frame_block = (struct
2016 Oct 26
0
Replication with SSL
Hello,
- Set up a pair of servers according to 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
2019 Jul 10
1
dsync crash
Hello,
I am getting a persistent seg fault while trying to sync our server to a new location.
We are on 2.2.33.2, due for an upgrade but we have used dsync successfully in the past. In fact, we used it to populate this same instance. So I hope this is just a configuration issue.
My logs are being filled with these errors::
2019-07-10T08:29:53-04:00 localhost dovecot: [ID 583609 mail.crit]
2015 May 18
0
v2.2.18 released
I am just starting out and trying to get dovecot and postfix working in Solaris 10 environment.
Went from 2.2.15 to 2.2.17, then to 2.2.18
Both version 2.2.17 & 2.2.18 gave this same error. 2.2.15 does not.
-----------------------------------
May 15 09:27:37 master: Info: Dovecot v2.2.18 starting up for imap
May 15 09:27:37 ssl-params: Info: Generating SSL parameters
May 15 09:27:37