Hi,
Noticed with latest v2.3.3 some new warning in logs, for example:
dovecot: auth: Warning: Event 0x80a6fc0 leaked (parent=(nil)):
auth-client-connection.c:338: 1 Time(s)
dovecot: auth: Warning: Event 0x80aa1c8 leaked (parent=(nil)):
auth-client-connection.c:338: 1 Time(s)
dovecot: auth: Warni
Hi,
But this harmless is spamming logs, so how to disable it:
grep auth-client-connection.c:338 maillog | wc -l
1259
Aki Tuomi wrote:
> > On 03 November 2018 at 12:12 Mart Pirita < sysad...@e-positive.ee
> > <mailto:sysad...@e-positive.ee>> wrote:
> >
> &
Hi,
I'm not using rsyslog and instead of hiding, this event leak should be
fixed.
Michael Slusarz wrote:
>> On November 3, 2018 at 9:41 AM Mart Pirita wrote:
>>
>>
>> Hi,
>>
>>
>> But this harmless is spamming logs, so how to disable it:
>&
Hi,
Build options - --sysconfdir=/etc/dovecot
doveconf -Pn > dovecot-new.conf
doveconf: Fatal: open(/etc/dovecot/dovecot/dovecot.conf) failed: No such
file or directory
I can make a symlink, but first I'd like to know is this a bug or
misconfiguration.
--
Mart
Hi,
You are right, recompiled with correct path.
Hajo Locke wrote:
> Hello,
>
>
>
> Am 07.11.2018 um 14:04 schrieb Mart Pirita:
>> Hi,
>>
>>
>>
>> Build options - --sysconfdir=/etc/dovecot
> you should use --sysconfdir=/etc
> sysconfig is pa
dovecot: auth: Warning: Event 0x80d71e0 leaked
(parent=(nil)): auth-client-connection.c:338
Nov 23 16:03:53 xxx dovecot: auth: Warning: Event 0x80c3220 leaked
(parent=(nil)): auth-client-connection.c:338
...
Aki Tuomi wrote:
> It will be fixed.
>
> Aki
>
> On 6.11.2018 8.57, Mart Piri
}
service pop3-login {
inet_listener pop3 {
port = 110
}
inet_listener pop3s {
port = 995
ssl = yes
}
}
ssl_ca = On 3 Nov 2018, at 17.41, Mart Pirita wrote:
>> Hi,
>>
>>
>> But this harmless is spamming logs, so how to disable it:
>>
>> grep auth-clien
Sirainen wrote:
> On 26 Nov 2018, at 13.16, Mart Pirita wrote:
>> Hi,
>>
>> Auth process is not constantly being shutdown and/or restarted and Dovecot
>> is used for SMTP authentication (Postfix).
>>
>> Checked few servers logs, they are running v2.3.3, for
Hello.
So far I have successfully built Dovecot until v2.3.14 on Centos 4-6 (yes I
know, they are old, but as they are remote servers, distros can't upgraded),
and sometimes I have also met compilation issues, but after highlighting them,
Timo have fixed the code.
Found from similar thread (Do
Hi,
This is very bad news.
I don't think that disto is old, if I can compile almost every software with it.
So at the moment I have two choices, newer upgrade Dovecot or rollback the
buffer_t changes and use latest version?
Mart
Timo Sirainen wrote:
> On 29. Jul 2021, at 7.21, Mar
got also same result with GCC 4.6.4.
Please advise?
Mart
Timo Sirainen wrote:
> On 29. Jul 2021, at 7.21, Mart Pirita <mailto:m...@e-positive.ee>> wrote:
>>
>> Hello.
>>
>> So far I have successfully built Dovecot until v2.3.14 on Centos 4-6 (yes I
>>
make[3]: *** [db-checkpassword.lo] Error 1
Due GCC segmentation faults during compilation, so far I'm unable to compile
any newer GCC, but got also same result with GCC 4.6.4.
Please advise?
Mart
Timo Sirainen wrote:
> On 29. Jul 2021, at 7.21, Mart Pirita <mailto:m...@e-positive.ee>>
Hi,
For some reason I've never been able to build x64 dovecot rpm package,
no matter how I try, I'm still getting lib64 errors, first tried few
years on centos 5, ok I know this is old distro, then few years tried
with centos 6 (and wrote here also - CentOS x64 compilation fails),
supported distro
want
> to try them?
>
> Aki
>> On 15/12/2019 13:01 Mart Pirita < m...@e-positive.ee
>> <mailto:m...@e-positive.ee>> wrote:
>>
>>
>> Hi,
>>
>> For some reason I've never been able to build x64 dovecot rpm package,
>> no mat
enssh, bind etc,
so they are in top shape and working well.
So official EOL is just for dummies. :)
Mart
@lbutlr wrote:
> On 15 Dec 2019, at 15:19, Alexander Dalloz wrote:
>> Am 15.12.2019 um 21:08 schrieb Mart Pirita:
>>> Well, but not for centos 5 and also these rpm ar
How this will fix x64 rpm build issues? Please stay in topic.
Mart
Benny Pedersen wrote:
> Mart Pirita skrev den 2019-12-16 09:32:
>
>> So official EOL is just for dummies. :)
>
> maybe upgrade to gcc 9.x.x first ?
>
> or drop precompiled distros !
>
Hello.
Few days ago upgraded from v2.2.26.0 >v2.2.27 and now windows 10, with
any outlook version (2007,2010,2013,2016) doesn't connect IMAP SSL:
Dec 12 12:29:35 server dovecot: imap-login: Debug: SSL: elliptic curve
secp384r1 will be used for ECDH and ECDHE key exchanges
Dec 12 12:29:35 server
Aki Tuomi wrote:
>
> Can you do
>
> doveconf -a | grep auth_mech
>
auth_mechanisms = plain login
P.S. Seems this 2.2.24 is the last win10 compatible version (as my
testserver doesn't have win10 users and thunderbird works well), any
never version gives an error. However I didn't find any hint fro
Hello.
Due win10 issue I had to downgrade 2.2.27 > 2.2.24 and now some gettings
errors for some users:
Dec 12 14:42:17 server dovecot: imap(user): Panic: file
mail-index-sync-keywords.c: line 227 (keywords_update_records):
assertion failed: (data_offset >= sizeof(struct mail_index_record))
Dec 12
Aki Tuomi wrote:
> Hi!
>
> Did you get a core file? Can you install debugging symbols and send
>
> gdb /path/to/bin /path/to/core
> bt full
>
> to us?
>
Seems no cores, atleast in /usr/sbin/ ( binary is in /usr/sbin/dovecot)
is none.
--
Mart
Aki Tuomi wrote:
> https://wiki2.dovecot.org/Debugging/Rawlog
>
> can you try this to get rawlogs to find out what happens?
>
> Aki
I'm bit confused, how this rawlog works. I did:
doveadm user -u kaka
userdb: kaka
user : kaka
system_groups_user: kaka
uid : 566
gid : 566
Edit: When using win8, then logs started appear in dovecot.rawlog. But
as win10 gives error in ssl level, before user authentication, then no
debug logs will be written into user dovecot.rawlog folder.
So how to debug this ssl issue?
Aki Tuomi wrote:
> https://wiki2.dovecot.org/Debugging/Rawlog
Edit: Maybe it's the DH file issue (like
https://i-mscp.net/index.php/Thread/10005-Notice-SSL-for-services-with-Courier-Windows-10-issue/),
so added to the conf:
ssl_dh_parameters_length = 2048
removed old file /usr/var/lib/dovecot/ssl-parameters.dat and dovecot
generated new file. Still same err
Aki Tuomi wrote:
> This sounds like issue with SSL itself. Is your certificate self-signed
> or issued by some trusted CA?
>
Self-signed.
--
Mart
Eric Broch wrote:
>
> Also, Outlook doesn't allow storage of a certificate like Thunderbird
> but it does allow you to accept it (every time one opens Outlook) and open.
Install certificate to the trusted root and no pop-ups -s anymore:).
--
Mart
Aki Tuomi wrote:
>
> Or spend 10 minutes to get one from LetsEncrypt for free? =)
>
>
Yes and no. It requires after every 3 months renewing and hasse with
dns, certbot etc. Sometimes, in own company, long and self-signed is
more usable:).
--
Mart
Hello.
I cant build 2.2.30*, but I can build fine version 2.2.29* with same
options:
RedHat based customized distro, 2.6.28.10 kernel
Build options:
export CPPFLAGS
export LDFLAGS
CPPFLAGS=-I/usr/local/ssl/include
LDFLAGS=-L/usr/local/ssl/lib
./configure \
--prefix=/usr \
--
Andrey Jr. Melnikov wrote:
> Mart Pirita wrote:
>> Hello.
>> I cant build 2.2.30*, but I can build fine version 2.2.29* with same
>> options:
>> RedHat based customized distro, 2.6.28.10 kernel
> [...]
>
>> Build error:
>> ltest_lib-test-bits.o: In f
Andrey Jr. Melnikov wrote:
> Mart Pirita wrote:
>> Hello.
>> I cant build 2.2.30*, but I can build fine version 2.2.29* with same
>> options:
>> RedHat based customized distro, 2.6.28.10 kernel
> [...]
>
>> Build error:
>> ltest_lib-test-bits.o: In f
Timo Sirainen wrote:
> On 21 Jun 2017, at 16.03, Mart Pirita wrote:
>>>> ltest_lib-test-bits.o: In function `bits_required64':
>>>> /usr/src/redhat/BUILD/dovecot-2.2.30/src/lib/bits.h:33: undefined
>>>> reference to `__builtin_clzll'
> This can
Timo Sirainen wrote:
> On 21 Jun 2017, at 16.42, Mart Pirita wrote:
>> Timo Sirainen wrote:
>>> On 21 Jun 2017, at 16.03, Mart Pirita wrote:
>>>>>> ltest_lib-test-bits.o: In function `bits_required64':
>>>>>> /usr/src/redhat/BUILD/dove
Dudi Goldenberg wrote:
> Hello list.
>
> I am running dovecot v2.2.13 on debian 8.8;
>
> I tried to add a "address =" statement for only localhost and one private IP,
> but then I got a complaint from system:
>
> dovecot[20515]: Error: systemd listens on port 143, but it's not configured
> in Dov
Hi,
I'm confused about FTS. https://wiki.dovecot.org/Tools/Doveadm/Index say's:
"Messages can also be added automatically to full text search index using:
plugin {
...
fts_autoindex = yes
}"
So I added "fts_autoindex = yes" into dovecot.conf (I'm using single
config file). That's it? How t
Hello.
I cant build 2.2.25, but I can build fine version 2.2.24 with same options:
RedHat based customized distro, 2.6.28.10 kernel
Build options:
export CPPFLAGS
export LDFLAGS
CPPFLAGS=-I/usr/local/ssl/include
LDFLAGS=-L/usr/local/ssl/lib
./configure \
--prefix=/usr \
--wi
Alexander Dalloz wrote:
> Am 02.07.2016 um 17:56 schrieb Mart Pirita:
>> Hello.
>>
>> I cant build 2.2.25, but I can build fine version 2.2.24 with same options:
>>
>> RedHat based customized distro, 2.6.28.10 kernel
> http://dovecot.org/pipermail/dovecot/2016-J
aki.tu...@dovecot.fi wrote:
>> art
> We are considering stopping support for old distros because maintaining
> support for them is becoming increasingly difficult.
>
> Please consider upgrading your distribution instead? It is rather old.
>
Well, don't do it on the middle of the v2.2, this is not
Aki Tuomi wrote:
> This has been now fixed in master-2.2 with
>
> https://github.com/dovecot/core/commit/20e802d6bbf4ddad3a2140a2f7812d01de0ec2ef
> https://github.com/dovecot/core/commit/d9c865ce774aae9f2f17b89e7e94c3cfca29dea7
>
> Our testings indicate that you can compile 2.2.25.1 on CentOS5 with
Hello.
Since I upgraded few months ago from version 1.0 to 1.1 (right now
using v1.1.rc4) in logs for some users only (but in different servers) I
noticed errors:
dovecot: Fatal: IMAP(user2): write(event_pipe) failed: Bad file descriptor
dovecot: Fatal: IMAP(user3): write(event_pipe) failed:
Tere.
Recently just migrated from Sendmail 8.14.3 to Postfix 2.5.6 and
switched from Cyrus-sasl 2.1.22 to Dovecot 1.1.13 sasl, all are compiled
from source and I have used Dovecot for a long time, since alpha versions.
Everything worked well for Outlook Express, Outlook and Thunderbird
clients, b
Tere.
>
> Are you saying that EHLO doesn't return anything when using Dovecot
> SASL?
Yes.
> Something's very broken then.
>
>
Hmm, but what?
Dovecot is compiled with options:
./configure \
--prefix=/usr \
--with-ssl=/usr/local/ssl \
--with-ssldir=/etc/ssl \
Tere.
But you said that other clients would still work? I don't see how
that's possible if Postfix doesn't reply to EHLO.
Well, I compiled postfix again and somehow now I can see more data using
dovecot sasl, no idea, why I didn't see this before:
Escape character is '^]'.
220 my.domain.e
Tere.
BTW. Is it possible that all other clients are using STARTTLS (or no
encryption) and only Entourage is trying to use smtps port?
No, all clients are using same settings. And all clients work with
cyrus-sasl, but with Dovecot, Entourage won't work.
--
Mart
Tere.
I think it is mostly a Entourage problem. I just decided to switch to
Apple Mail since it works much better with IMAP than Entourage.
I'm pretty sure, this is Entourage problem, as Apple Mail (IPhone -s
too) works well, but as a lot clients using Entourage as calendar, etc,
they jus
Tere.
Then it should show up.. Post dovecot -n output instead, that'll show
what exactly Dovecot is reading from config file.
Please:
dovecot -n
# 1.1.13: /etc/dovecot.conf
# OS: Linux 2.6.24.2 i686 Red Hat Linux release 8.0 (Psyche)
protocols: imaps pop3 pop3s
ssl_parameters_regenerate: 0
Tere.
On Thu, 2009-04-16 at 21:39 +0300, Mart Pirita wrote:
250-AUTH PLAIN
250-AUTH=PLAIN
You're missing LOGIN here, which is required by some MS clients
(although I thought Outlook belonged to that category too).
Yes, I noticed that too, as same test with cyrus-sasl shows:
Tere.
If you had changed the mechanisms=plain default, it would have shown
up here (and you can see that also with dovecot -a). So something's
wrong in that setting.
Hmm, You are right, postfix install inserted into config lines:
# Postfix - suggested configuration taken from SASL_README
Timo Sirainen kirjutas:
RedHat 9 based distro, 2.6.24.2 kernel, OpenSSL 1.0.0a 1 Jun 2010
Hmm. v1.0.0a, really?..
Yes - compiled manually from openssl-1.0.0a.tar.gz and I'm pointing in
dovecot.spec dovecot to use it:
export CPPFLAGS
export LDFLAGS
CPPFLAGS=-I/usr/local/ssl/include/openssl
Timo Sirainen kirjutas:
/usr/src/redhat/BUILD/dovecot-1.2.16/src/login-common/ssl-proxy-openssl.c:950:
undefined reference to `OpenSSL_add_all_algorithms'
I just hate OpenSSL. You can comment out that line from the code until I figure
out what to do about this. That function was supposed to h
Timo Sirainen kirjutas:
/usr/src/redhat/BUILD/dovecot-1.2.16/src/login-common/ssl-proxy-openssl.c:950:
undefined reference to `OpenSSL_add_all_algorithms'
I just hate OpenSSL. You can comment out that line from the code until I figure
out what to do about this. That function was supposed to h
Timo Sirainen kirjutas:
I wonder if this is the reason for all your trouble.. Are there some old
OpenSSL versions still installed? Maybe it's mixing headers of old OpenSSL with
libs of new, or vice versa.
Yes. But strange, why until 1.2.16 all went fine? I'll try to compile
older SSL, maybe
Timo Sirainen kirjutas:
I wonder if this is the reason for all your trouble.. Are there some old
OpenSSL versions still installed? Maybe it's mixing headers of old OpenSSL with
libs of new, or vice versa.
I did some tests, dovecot 1.2.15 compiles fine withh latest OpenSSL, but
doesn't allo
Tom Talpey kirjutas:
I built 1.2.16 against openssl-0.9.8p just last week; it linked
and is running fine for me. Have you tried any version after 0.9.8l?
Tested with openssl-0.9.8m, 0.9.8q, 1.0.0a, 1.0.0c, config options are
simple:
./config --prefix=/usr/local/openssl &&
make &&
make insta
David Ford kirjutas:
openssl < 0.9.8o and <1.0.0b are vulnerable to exploits.
Yes I know, but ANY software is good until someone finds a bug in it.
Theoretically some may trying exploit it, but I'm pretty sure there are
a lot more interesting places to do that:).
--
Mart
Mart Pirita kirjutas:
./config --prefix=/usr/local/openssl &&
make &&
make install
And linked in spec:
export CPPFLAGS
export LDFLAGS
CPPFLAGS=-I/usr/local/ssl/include/openssl
LDFLAGS=-L/usr/local/ssl/lib
Las message included typo, the real path is /usr/local/ssl, so this
Timo Sirainen kirjutas:
The only change to SSL code I've done for almost a year has been adding that
OpenSSL_add_all_algorithms() call, because without it some other OpenSSL
installations failed.
Hmm, but if I'm comping Dovecot with special made OpenSSL, then if even
RedHat -s old OpenSSL is
Tom Talpey kirjutas:
I assume that you re-ran configure in dovecot-1.2.16 and verified that
it actually picked up the openssl libs from /usr/local afterwards?
Beyond that, I guess I don't have a further suggestion.
Yes, I did it multile times, and config.log seems also OK, so I also
have no clu
Timo Sirainen kirjutas:
Here's a way to find out for sure. Apply the attached patch, compile and check
the resulting imap-login binary:
Done:
strings imap-login | grep OpenSSL
[m...@tibu imap-login]# strings imap-login | grep OpenSSL
OpenSSL 0.9.6b [engine] 9 Jul 2001
OpenSSL malloc() fai
Timo Sirainen kirjutas:
This looks messed up. Some part of OpenSSL is from 0.9.6b and some part
is from 0.9.8l.
Noticed too, seems dovecot doesn't fully trust export CPPFLAGS/LDFLAGS
paths?
BTW, why dovecot uses "export CPPFLAGS/LDFLAGS" and not typical
--with-ssl=/usr/local/ssl etc style
Timo Sirainen kirjutas:
Or there are some other parameters that conflict with it. Show the gcc
command line when compiling ssl-proxy-openssl.c and when linking
imap-login binary? If there is -I/usr/include that could explain it..
Can't find anything:
[m...@tibu dovecot-1.2.16]# grep imap-logi
Timo Sirainen kirjutas:
Still, it's increasingly looking like some kind of conflict between two OpenSSL
versions and really nothing to do with Dovecot itself. Can't you just upgrade
to a non-ancient OS with a newer OpenSSL?
Actually this OS is quite a lot manually updated and so far all works
Timo Sirainen kirjutas:
CPPFLAGS=-I/usr/local/ssl/include/openssl
Try -I/usr/local/ssl/include
Well, Timo - You did it again, small thing, but nobody, except You noticed.
With:
export CPPFLAGS
export LDFLAGS
CPPFLAGS=-I/usr/local/ssl/include
LDFLAGS=-L/usr/local/ssl/lib
1.2.16 from original
Hello.
I cant build 2.2.2, but I can build fine version 2.1.16 with same options:
RedHat based customized distro, 2.6.28.10 kernel
Build options:
export CPPFLAGS
export LDFLAGS
CPPFLAGS=-I/usr/local/ssl/include
LDFLAGS=-L/usr/local/ssl/lib
./configure \
--prefix=/usr \
--with
Timo Sirainen kirjutas:
On 22.5.2013, at 20.31, Mart Pirita wrote:
I cant build 2.2.2, but I can build fine version 2.1.16 with same options:
RedHat based customized distro, 2.6.28.10 kernel
What gcc version?
gcc -v
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.3.6/specs
Timo Sirainen kirjutas:
gcc -v
gcc version 3.3.6
Hmh. Does the attached patch help?
Yes, it does, thanks!
--
Mart
Hello.
I have problems to compile Dovecot2.2.13 with rpmbuild using options:
./configure \
--prefix=/usr \
--with-ssl=openssl \
--with-ssldir=/etc/ssl \
--sysconfdir=/etc \
--without-vpopmail \
--with-pam \
--without-bsdauth \
--wi
Tere.
Using the latest v1.0.rc30, I'm trying to convert all users mbox -s to maildir with Dovecot
-s convert plugin (setup from http://wiki.dovecot.org/Plugins/Convert). But seems Dovecot
can't create the needed maildir folder into users homedir, as I'm getting the error:
dovecot: Apr 06 15:1
Tere.
Is the '/' really missing from test/Maildir or did you just break it
when copy&pasting?
It's a typo from copy&paste correct is - dovecot: Apr 06 15:16:13 Error:
POP3(spam): Mailbox conversion: Failed to create destination storage
with data: maildir:/home/test/Maildir
No.
Ok.
--
Ma
Tere.
On 6.4.2007, at 15.36, Mart Pirita wrote:
dovecot: Apr 06 15:16:13 Error: POP3(spam): Mailbox conversion:
Failed to create destination storage with data:
maildir:/home/testMaildir
This should fix it:
http://dovecot.org/list/dovecot-cvs/2007-April/008619.html
Pathed the v1.30
Tere.
I use:
log_path = /var/log/maillog
info_log_path = /var/log/maillog
And into /var/log are:
maillog
maillog.1
maillog.2
maillog.3
Now when log files are rotating at 04:00 (maillog > maillog.1) dovecot
still keeps login into maillog.1 and not into maillog, where sendmail,
etc writes lo
Tere.
Have dovecot log via syslog instead of to a file, and the problem goes
away.
Prr, how did I miss this? So, uncommenting all:
#log_path = /var/log/maillog
#info_log_path =
/var/log/maillog
Tere.
I'm using Debian, postfix & dovecot, with system quotas and settings in
dovecot.conf:
default_mail_env =
maildir:%h/Maildir:INDEX=/var/spool/dovecot/index/%u:CONTROL=/var/spool/dovecot/control/%u
But if system quota is full, users won't get new messages but won't get
also any kind inform
Hello.
Tried search, no luck, sorry, if this is already answered, but I'm still
looking a solution using pam_auth how to define in dovecot which user
can access which protocol, for example, default is:
protocols = pop3 pop3s imap imaps
I'd like to use something like this:
exclude_using_pop
Tere.
http://wiki.dovecot.org/Authentication/RestrictAccess
Thisone - authrequiredpam_listfile.so item=user sense=allow
file=/etc/imapusers onerr=fail
Ok, that is close, but how to allow some users use only imaps and not
imap? Same question about pops/pop also. Or is it possible
Tere.
Does anyone know what this is? Or someone I could ask?
Normal dictionary attack?
--
Mart
Tere.
%c expands to "secured" or empty. So you could use eg.
passdb pam {
args = %s%c
}
and create imap, imapsecured, pop3, pop3secured
More better, so for example user1 can access only imaps, using Yous
suggestion, I have to list all users, except user1 in imap, pop3,
pop3secured.
But i
Tere.
Second time - does anybody have any idea what is wrong, btw I downgraded to
1.0.2, and
getting from time to time same errors:
I'm running 1.0.3 in RedHat for some time, few days ago also upgraded
1.0.0 to 1.0.3 on Debian Sarge, 64 machine.
But now message log runs like crazy (about 10 GB
Tere.
> can you tell us more about your config? what backends are you using?
>
>
Debian Sarge, 64, reiser, dovecot -a:
# 1.0.2: /etc/dovecot.conf
base_dir: /var/run/dovecot/
log_path:
info_log_path:
log_timestamp: %b %d %H:%M:%S
syslog_facility: mail
protocols: imap imaps pop3 pop3s
listen: *
s
Tere.
Your PAM modules are getting stuck. Probably has nothing to do with
Dovecot itself.
But I haven't change/install/upgrade anything, but the Dovecot. And
version 1.0.3 gives errors like crazy, 1.0.2 from time to time and older
versions none? Seems something in new Dovecot versions drive
Tere.
The only changes to dovecot-auth between 1.0.2 and 1.0.3 were for LDAP
code, which you aren't using. So I think the problem has more to do
with the binary getting compiled a bit differently, causing random
problems in a buggy PAM module.
Ok.
So where do PAM and passwd do the lookups
Tere.
I had impression, that Dovecot does cache the Maildir status, new and
old messages and so checking (finding the new messages) the new emails
is fast. But what is the truth? Latelly noticed, that using latest
Thunderbird, 1 mb line, osx or xp, imap and maildir, if mailbox includes
for ex
Tere.
Tried search, no luck, does the Dovecot include push imap/imap notify support?
--
Mart
Tere.
If you're looking for something iPhone-compatible, then "no." Theirs is
a proprietary system which from what I've read, seems to use SMS in
combination with IMAP. Wacky.
Yep, thats wacky.
(If you aren't talking about iPhone compatibility, I'm less
knowledgeable, but dovecot does suppo
Tere.
> I think we're getting closer to v1.1 RCs.
>
>
I'm a little bit confused. Right now I'm using v.1.0.7, but I tried
compile v1.1.beta8 with same options as v.1.0.7 and seems it's working
fine like stable version does.
But if v1.1 is beta then what is/will be v2? And what version should I
83 matches
Mail list logo
