Displaying 20 results from an estimated 4000 matches similar to: "2.3.1 from ghettoforge-testing causes auth failures"
2017 Dec 28
5
dovecot-pigeonhole problems after upgrade to v2.3.0
December 28, 2017 2:52 PM, "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote:
> December 28, 2017 1:21 PM, "Aki Tuomi" <aki.tuomi at dovecot.fi> wrote:
>
>>> On December 28, 2017 at 7:43 PM "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote:
>>>
>>> December 28, 2017 12:14 PM, "Aki
2017 Dec 10
0
hosting emails at home
On December 10, 2017 5:25:46 PM EST, Stephan H <herker at gmail.com> wrote:
>Which part? Hosting the email server at home or the relay in the
>cloud?
>
>On Dec 10, 2017 14:53, "Fabian A. Santiago"
><fsantiago at garbage-juice.com>
>wrote:
>
>> On December 10, 2017 3:39:05 PM EST, Stephan H <herker at gmail.com>
>wrote:
>> >I have
2017 Dec 10
2
hosting emails at home
Which part? Hosting the email server at home or the relay in the cloud?
On Dec 10, 2017 14:53, "Fabian A. Santiago" <fsantiago at garbage-juice.com>
wrote:
> On December 10, 2017 3:39:05 PM EST, Stephan H <herker at gmail.com> wrote:
> >I have dovecot postfix setup on my home server as well. I use a
> >virtual
> >server in the cloud as my mx record
2017 Dec 28
0
dovecot-pigeonhole problems after upgrade to v2.3.0
December 28, 2017 12:43 PM, "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote:
> December 28, 2017 12:14 PM, "Aki Tuomi" <aki.tuomi at dovecot.fi> wrote:
>
>>> On December 28, 2017 at 7:07 PM "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote:
>>>
>>> Hello,
>>>
>>> After
2017 Dec 28
0
2.3.0 upgrade from 2.2.x
On December 27, 2017 8:07:18 PM EST, "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote:
>Question; So after updating to 2.3.0 and following the recommended
>warnings / changes from running doveconf -n and then doing that same
>command > "a new conf file", and then renaming the conf files and
>restarting dovecot, I should be good to go with my old
2017 Dec 28
0
dovecot-pigeonhole problems after upgrade to v2.3.0
December 28, 2017 12:14 PM, "Aki Tuomi" <aki.tuomi at dovecot.fi> wrote:
>> On December 28, 2017 at 7:07 PM "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote:
>>
>> Hello,
>>
>> After upgrading to dovecot 2.3.0, my sieve filtering is broken. I managed it via roundcube's
>
> managesieve plugin. my emails are not
2017 Dec 10
0
hosting emails at home
On December 10, 2017 3:39:05 PM EST, Stephan H <herker at gmail.com> wrote:
>I have dovecot postfix setup on my home server as well. I use a
>virtual
>server in the cloud as my mx record and mail relay and have my home
>record
>on dynamic dns. It's really effective.
>
>On Dec 10, 2017 2:37 PM, "Fabian A. Santiago"
><fsantiago at
2017 Dec 27
2
Package repository now available
> On December 27, 2017 at 6:05 PM "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote:
>
>
> December 27, 2017 10:53 AM, aki.tuomi at dovecot.fi wrote:
>
> > Small amendment...
> >
> > if you ran
> >
> > gpg --export > /etc/apt/trusted.gpg.d/dovecot.gpg
> >
> > please run
> >
> > gpg --export
2017 Dec 27
0
Package repository now available
> On December 27, 2017 at 6:11 PM Aki Tuomi <aki.tuomi at dovecot.fi> wrote:
>
>
>
> > On December 27, 2017 at 6:05 PM "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote:
> >
> >
> > December 27, 2017 10:53 AM, aki.tuomi at dovecot.fi wrote:
> >
> > > Small amendment...
> > >
> > > if you ran
2017 Dec 10
4
hosting emails at home
I have dovecot postfix setup on my home server as well. I use a virtual
server in the cloud as my mx record and mail relay and have my home record
on dynamic dns. It's really effective.
On Dec 10, 2017 2:37 PM, "Fabian A. Santiago" <fsantiago at garbage-juice.com>
wrote:
> On December 10, 2017 2:49:35 PM EST, "Andr? Rodier" <andre at rodier.me>
>
2018 Apr 23
0
question about using cram-md5 login passwords
> On 23 April 2018 at 16:14 "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote:
>
>
> hello dovecot community,
>
> question; if my user database and dovecot installation is currently setup to use plain login passwords, and i want to convert to cram-md5, after i configure dovecot accordingly and reset passwords into cram-md5, if anyone uses plain login
2017 Dec 29
0
dovecot-pigeonhole problems after upgrade to v2.3.0
December 28, 2017 6:38 PM, "Peter" <peter at pajamian.dhs.org> wrote:
> On 29/12/17 10:00, Fabian A. Santiago wrote:
>
>> i've now completely uninstalled all traces of dovecot and reinstalled
>> from your repo and still the same issue persists with the same
>> errors.
>
> I'd be interested to know if the dovecot23* packages in GhettoForge
2017 Dec 28
2
2.3.0 upgrade from 2.2.x
Question; So after updating to 2.3.0 and following the recommended warnings / changes from running doveconf -n and then doing that same command > "a new conf file", and then renaming the conf files and restarting dovecot, I should be good to go with my old config updated to the new config spec? Just confirming. Thanks.
What I mean is doing the -n to a new file hasn't changed or
2015 Nov 15
0
usage of recipient delimiters
Hi,
Am 15. November 2015 01:46:29 MEZ, schrieb fsantiago at garbage-juice.com:
>Hello,
>
>I have a forum system which can potentially have users send email to it
>
>for posting purposes that arrives addressed to a particular user
>account
>with a recipient delimiter:
>
>user+1a2b3c4d5e6f at domain.com
>
>The forum server is supposed to check the "user"
2017 Dec 28
7
dovecot-pigeonhole problems after upgrade to v2.3.0
Hello,
After upgrading to dovecot 2.3.0, my sieve filtering is broken. I managed it via roundcube's managesieve plugin. my emails are not being filtered accordingly into their folders and when i attempt to access the filter interface in roundcube, my maillog reports:
Dec 28 12:05:07 mail roundcube: <gs7miohh> PHP Error: Unable to connect to managesieve on 127.0.0.1:4190 in
2017 Dec 29
2
dovecot-pigeonhole problems after upgrade to v2.3.0
Am 29.12.2017 um 15:08 schrieb Fabian A. Santiago:
> December 28, 2017 6:38 PM, "Peter" <peter at pajamian.dhs.org> wrote:
>
>> On 29/12/17 10:00, Fabian A. Santiago wrote:
>>
>>> i've now completely uninstalled all traces of dovecot and reinstalled
>>> from your repo and still the same issue persists with the same
>>> errors.
2014 Dec 09
0
GhettoForge links in http://wiki.centos.org/AdditionalResources/Repositories
GhettoForge seems to be using new software for their wiki.
http://GhettoForge.org/ redirects to
http://GhettoForge.org/index.php/Main_Page which is probably adequate.
http://GhettoForge.org/wiki/Usage returns a 404. It appears
http://GhettoForge.org/index.php/Usage is the replacement. I will make the
appropriate change in my copy of
http://wiki.centos.org/AdditionalResources/Repositories.
Also
2017 Dec 15
2
ot: 2.2 ghettoforge install systemctl Q
I've installed new Centos 7 with Dovecot 2.2 from ghettoforge and, used
/etc/dovecot from current Centos 6 Dovecot 2.1
I can start/stop Dovecot with dovecot / doveadm stop
BUT when I tried 'systemctl' I get
# systemctl status dovecot
? dovecot.service - Dovecot IMAP/POP3 email server
Loaded: loaded (/usr/lib/systemd/system/dovecot.service; disabled;
vendor preset: disabled)
2017 Dec 16
0
ot: 2.2 ghettoforge install systemctl Q
> On December 16, 2017 at 1:59 AM voytek at sbt.net.au wrote:
>
>
> I've installed new Centos 7 with Dovecot 2.2 from ghettoforge and, used
> /etc/dovecot from current Centos 6 Dovecot 2.1
>
> I can start/stop Dovecot with dovecot / doveadm stop
>
> BUT when I tried 'systemctl' I get
>
> # systemctl status dovecot
> ? dovecot.service - Dovecot
2017 Dec 16
1
ot: 2.2 ghettoforge install systemctl Q
On 16/12/17 20:45, Aki Tuomi wrote:
>> I've installed new Centos 7 with Dovecot 2.2 from ghettoforge and, used
>> /etc/dovecot from current Centos 6 Dovecot 2.1
>>
>> I can start/stop Dovecot with dovecot / doveadm stop
>>
>> BUT when I tried 'systemctl' I get
>>
>> # systemctl status dovecot
>> ? dovecot.service - Dovecot IMAP/POP3