login failure "reason" not returned (dovecot-2.2.32)
Hello,
In the past (older dovecot versions) I've tuned the SQL "password_query"
of our mail server so that when the user has the account blocked for
some reason (expired, need password change, etc.) the query returns
nologin=1 and a verbose reason like reason="Your account is expired
please change the password" and it worked very well with IMAP clients.
I'm now seeing that despite the message returned by the SQL, the IMAP
server always returns a generic error "NO [AUTHENTICATIONFAILED]
Authentication failed."
I've setup an "always fail" query in a test installation (see below) and
with that, a simple openssl/telnet login simulation fails without
reporting the "ERRORDEBUG" reason.
password_query = SELECT '%n' AS username, '%d' AS domain, 'ERRORDEBUG'
AS reason, '1' AS nologin, CONCAT('{PLAIN}',RAND()) AS password;
Tested with:
imapsrv# openssl s_client -connect imap2:993
---
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE
IDLE AUTH=PLAIN] IPLNet IMAP ready.
a login "someouser@dom" "password"
a NO [AUTHENTICATIONFAILED] Authentication failed.
Also using doveadm auth:
imapsrv# doveadm auth test someuser@dom
Password:
passdb: someuser@dom auth failed
extra fields:
user=someuser@dom
I've already done some source digging without conclusions, the code to
return the reason seem to be in place in the function
"imap_client_auth_result" at src/imap-login/client-authenticate.c
What am I doing wrong?
Should the behaviour now be done in another way?
Best regards, keep the good work in this fine software!
--
Best regards,
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Pedro Ribeiro
Politécnico de Lisboa, Serviços da Presidência
Departamento de Sistemas de Informação e Comunicações
Phone: +351 210 464 700 (general) / VoIP: 80100
Helpdesk: helpd...@net.ipl.pt / https://www.net.ipl.pt
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Re: Questions about SPECIAL-USE IMAP extension
Is this what you are looking for? https://wiki2.dovecot.org/Plugins/MailboxAlias It seems already be implemented... regards. On 2018/01/12 14:25, Tanstaafl wrote: On Fri Jan 12 2018 01:29:37 GMT-0500 (Eastern Standard Time), Steffen Kaiser wrote: On Thu, 11 Jan 2018, Joseph Tam wrote: I'd like to configure my dovecot service to use the IMAP SPECIAL-USE well, in my experience SPECIAL-USE is just a suggestions to clients. Check RFC 6154 for MUSTs, you'll find only few. Hence, how the client (or the server) behaves in a special case is implementor-defined. I do expect that any client supporting SPECIAL-USE honors the server setting (first time it connects to the server or everytime, but at least once) and creates the mailboxes it uses itself. Otherwise, Dovecot can autocreate the mailboxes regardless of its use: https://wiki2.dovecot.org/MailboxSettings There was a similar discussion about this on list some time ago, about whether or not Dovecot could utilize special use 'aliases' that your clients may want to use by default, and Dovecot would automatically map those requests to a single mailbox. E.g.: Outlook clients would see/use 'Sent Items' Thunderbird would see/use 'Sent' But both would be mapped to a single mailbox 'Sent' (or whatever you had defined as the actual mailbox). Personally I would love to see this implemented. -- Best regards, =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Pedro Ribeiro IPLNet, Redes de dados e comunicações Departamento de Sistemas de Informação e Comunicações Instituto Politécnico de Lisboa Telefone: +351 210 464 701 VoIP: sip:80...@voip.ipl.pt =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Specifying other mail_attachment_dir for namespace
Hello,
I have a Dovecot setup where I need to allow users to access a snapshot
of their messages (when they complain about missing messages/folders
deleted by mistake).
From time to time the system does a LVM snapshot of the volume holding
the mailboxes and sis storage and that messages are available via a
"special" namespace.
The problem is the messages that references attachments in the single
attachment storage cause the file in some cases (when all the references
were delete), the attachment itself is missing from the current SIS.
Is there any option to reference a specific SIS folder for the namespace
like I do for the messages as below?
namespace arquivo {
type = private
separator = /
prefix = "@ARQUIVO/"
subscriptions = yes
list = yes
inbox = no
hidden = no
ignore_on_failure = yes
location = mdbox:/mail-snap/domains/%d/%-2.2n/%n
}
TIA.
--
Best regards,
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Pedro Ribeiro
Politécnico de Lisboa, Serviços da Presidência
Departamento de Sistemas de Informação e Comunicações
Phone: +351 210 464 700 (general) / VoIP: 80100
Helpdesk: helpd...@net.ipl.pt / https://www.net.ipl.pt
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
IMAP ALERT on reason/nologin
Hello everyone, Some dovecot versions (years!) ago. I've made a rather complicated SQL query that verified some conditions during the SQL passdb checking and returned the usual parameters or "nologin" field signalling some account problem and a text on the "reason" field that were shown to the user telling him the reason of being rejected the login. Common "reasons" are blocked accounts, suspected brute-force to the user account, historic problems from his IP address, etc. In the current versions I've found that despite the attributes being set by the SQL query, dovecot no longer seems to signal that to the client application and it ends with some generic "wrong password" causing a lot of confusion and user complains. I can't find any reference to that (nologin/reason) logic in the current Dovecot documentation. Is this feature deprecated/removed? Were that logic changed and documented elsewhere? regards! stay safe! Note: running Dovecot 2.3.10.1 -- Best regards, =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Pedro Ribeiro Politécnico de Lisboa, Serviços da Presidência Departamento de Sistemas de Informação e Comunicações Phone: +351 210 464 700 (general) / VoIP: 80100 Helpdesk: helpd...@net.ipl.pt / https://www.net.ipl.pt =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= smime.p7s Description: S/MIME Cryptographic Signature
Don't count namespace space in quota
Hello everyone!
I'm trying to figure a solution for this scenario.
I have the Dovecot IMAP using MDBOX (SIS) storage for the daily usage email.
For long term storage I'm preparing a namespace with MBOX storage.
I'm not using the altstorage logic because as far as I know it needs to
have the same format as the base one and for archival I prefer to have
the attachments inside the messages in an old/well known format
supported by near any email software.
The problem at the moment is with quotas.
If the user has 5GB in his mailboxes and the long term "historico"
namespace has another 5GB, the storage used becomes 10GB and I want the
users to only see their "active" usage (5GB).
I have that space to be ignored (as defined in the wiki and dovecot
documentation - my quota_rule5 ) but it doesn't seem to influence the
usage reported by IMAP.
What am I doing wrong?
If I put the "historico"namespace with disabled = yes and do a "doveadm
quota recalc" the values become correct but I need the namespace
available so the users can recover their old messages if needed.
The relevant settings (AFAIK) I'm using are:
plugin {
quota = dict:FileQuota:ns=:file:%h/dovecot-quota
quota2 = dirsize:HistQuota:ns=@HISTORICO/
quota_clone_dict = proxy::quota
quota_grace = 10%%
quota_rule = *:storage=24G
quota_rule2 = Trash:storage=+128M
quota_rule3 = Junk:storage=+64M
quota_rule4 = INBOX:storage=+128M
quota_rule5 = ns=@HISTORICO:ignore
}
namespace historico {
disabled = no
hidden = no
ignore_on_failure = yes
inbox = no
list = no
location =
mbox:/mnt/mail-hist/historic/%d/%-2.2n/%n:SUBSCRIPTIONS=.imap/dovecot-subscriptions:LAYOUT=maildir++
order = 0
prefix = @HISTORICO/
separator = /
subscriptions = yes
type = private
}
namespace inbox {
disabled = no
hidden = no
ignore_on_failure = no
inbox = yes
list = yes
location =
order = 0
prefix =
separator = /
subscriptions = yes
type = private
}
userdb {
args = /etc/dovecot/dovecot-sql.conf.ext
auth_verbose = default
default_fields = home=/data/domains/%d/%-2.2n/%n lport=%{lport}
driver = sql
}
best regards to all the Dovecot community, stay safe!
--
Best regards,
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Pedro Ribeiro
Politécnico de Lisboa, Serviços da Presidência
Departamento de Sistemas de Informação e Comunicações
Phone: +351 210 464 700 (general) / VoIP: 80100
Helpdesk: helpd...@net.ipl.pt / https://www.net.ipl.pt
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
smime.p7s
Description: S/MIME Cryptographic Signature
Re: Don't count namespace space in quota
Thanks for the suggestion.
That wasn't enough, finally found it!
The quota dict wasn't properly configured and were including all
namespaces in the counting.
Instead of:
quota = dict:FileQuota:ns=:file:%h/dovecot-quota
I now have:
quota = dict:FileQuota::ns=:file:%h/dovecot-quota
The namespace selector were in the wrong parameter due to a missing :
delimiter
Thanks!
On 3/24/21 07:28, Aki Tuomi wrote:
1
On 23/03/2021 21:33 Pedro Ribeiro wrote:
Hello everyone!
I'm trying to figure a solution for this scenario.
I have the Dovecot IMAP using MDBOX (SIS) storage for the daily usage email.
For long term storage I'm preparing a namespace with MBOX storage.
I'm not using the altstorage logic because as far as I know it needs to have
the same format as the base one and for archival I prefer to have the
attachments inside the messages in an old/well known format supported by near
any email software.
The problem at the moment is with quotas.
If the user has 5GB in his mailboxes and the long term "historico" namespace has another
5GB, the storage used becomes 10GB and I want the users to only see their "active" usage
(5GB).
I have that space to be ignored (as defined in the wiki and dovecot
documentation - my quota_rule5) but it doesn't seem to influence the usage
reported by IMAP.
What am I doing wrong?
If I put the "historico" namespace with disabled = yes and do a "doveadm quota
recalc" the values become correct but I need the namespace available so the users can recover
their old messages if needed.
The relevant settings (AFAIK) I'm using are:
plugin {
quota = dict:FileQuota:ns=:file:%h/dovecot-quota
quota2 = dirsize:HistQuota:ns=@HISTORICO/
quota_clone_dict = proxy::quota
quota_grace = 10%%
quota_rule = *:storage=24G
quota_rule2 = Trash:storage=+128M
quota_rule3 = Junk:storage=+64M
quota_rule4 = INBOX:storage=+128M
quota_rule5 = ns=@HISTORICO:ignore
}
namespace historico {
disabled = no
hidden = no
ignore_on_failure = yes
inbox = no
list = no
location =
mbox:/mnt/mail-hist/historic/%d/%-2.2n/%n:SUBSCRIPTIONS=.imap/dovecot-subscriptions:LAYOUT=maildir++
order = 0
prefix = @HISTORICO/
separator = /
subscriptions = yes
type = private
}
namespace inbox {
disabled = no
hidden = no
ignore_on_failure = no
inbox = yes
list = yes
location =
order = 0
prefix =
separator = /
subscriptions = yes
type = private
}
userdb {
args = /etc/dovecot/dovecot-sql.conf.ext
auth_verbose = default
default_fields = home=/data/domains/%d/%-2.2n/%n lport=%{lport}
driver = sql
}
best regards to all the Dovecot community, stay safe!
--
Best regards,
I think this should be:
quota2_rule = ns=@HISTORICO:ignore
Aki
--
Best regards,
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Pedro Ribeiro
Politécnico de Lisboa, Serviços da Presidência
Departamento de Sistemas de Informação e Comunicações
Phone: +351 210 464 700 (general) / PBX Ext.: 80100
Helpdesk: helpd...@net.ipl.pt / https://www.net.ipl.pt
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
smime.p7s
Description: S/MIME Cryptographic Signature
Backtrace on UID SORT and UID SEARCH
er_run_internal+0xc7) [0x7f3c6b7d3ed7] /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x50) [0x7f3c6b7d2a30] /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7f3c6b7d2ba0] /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f3c6b74a393] dovecot/imap [someuser@ourdom 192.168.166.58 UID SEARCH](main+0x459) [0x563bbf0571a9] /lib64/libc.so.6(__libc_start_main+0xeb) [0x7f3c6b33182b] regards! -- Best regards, =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Pedro Ribeiro Politécnico de Lisboa, Serviços da Presidência Departamento de Sistemas de Informação e Comunicações Phone: +351 210 464 700 (general) / VoIP: 80100 Helpdesk: helpd...@net.ipl.pt / https://www.net.ipl.pt =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= smime.p7s Description: S/MIME Cryptographic Signature
ZLIB/ZSTD Compressed MBOX in Maildir++ layout
Hello everyone! Our archive namespace is kept in MBOX format with Maildir++ layout due to: * Need to have the email from all users/folders self contained (our base namespace uses MDBOX with single instance storage of attachments) * MBOX/FS layout isn't supported because some folders have messages and subfolders. I'm trying to compress that namespace using zstd/gzip following the informations from Dovecot documentation about the zlib plugin but when the (MBOX/Maildir++) compress and become with .zst/.zstd/.gz suffix (both tested) the system can't read the mailboxes and incorrectly reports the suffix (.zstd/.gz) as a subfolder name (following the Maildir++ file structure). Is there any way to make the MBOX/Maildir++ compatible with the zlib compression? Using Dovecot 2.3.14 on Debian10 Regards. -- Best regards, =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Pedro Ribeiro Politécnico de Lisboa, Serviços da Presidência Departamento de Sistemas de Informação e Comunicações Phone: +351 210 464 700 (general) / VoIP: 80100 Helpdesk: helpd...@net.ipl.pt / https://www.net.ipl.pt =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= smime.p7s Description: S/MIME Cryptographic Signature
Re: ZLIB/ZSTD Compressed MBOX in Maildir++ layout
Hello! Thank you for the suggestion. That solved the problem of using layout FS with MBOX storage format. After copying all the mail of the test user to the namespace in this format I've compressed all the storage files with ZSTD and that changed the name with the additional suffix .zst Dovecot seems to need this to be .zstd so I've fixed the names. But ... it doesn't work. Jun 28 08:56:39 ribble dovecot: imap(pribe...@net.ipl.pt)<82609>: Error: Mailbox @HISTZLIB/IPLNet: stat(/mnt/mail-hist/historic-fs/net.ipl.pt/ro/pribeiro/mailboxes/IPLNet/mBoX-MeSsAgEs) failed: No such file or directory In that directory the filename is: -rw--- 1 vmail vmail 853M Jun 25 17:25 mBoX-MeSsAgEs.zstd What am I doing wrong? regards! On 24/06/2021 14:53, Josef 'Jeff' Sipek wrote: On Thu, Jun 24, 2021 at 10:35:24 +0100, Pedro Ribeiro wrote: Hello everyone! Our archive namespace is kept in MBOX format with Maildir++ layout due to: * Need to have the email from all users/folders self contained (our base namespace uses MDBOX with single instance storage of attachments) * MBOX/FS layout isn't supported because some folders have messages and subfolders. You should be able to use the fs layout if you specify a dirname: https://doc.dovecot.org/configuration_manual/mail_location/mbox/mboxchildfolders/#messages-in-named-file Then, the compression suffix being added shouldn't matter. Jeff. -- Best regards, =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Pedro Ribeiro Politécnico de Lisboa, Serviços da Presidência Departamento de Sistemas de Informação e Comunicações Phone: +351 210 464 700 (general) / VoIP: 80100 Helpdesk:helpd...@net.ipl.pt /https://www.net.ipl.pt =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= smime.p7s Description: S/MIME Cryptographic Signature
Re: ZLIB/ZSTD Compressed MBOX in Maildir++ layout
Hello again and thanks for the quick answer! Our base (inbox) namespace is based on MDBOX with SIS SIS is fantastic optimizing the storage required to the active (daily accessed/moved) email. But for archival and easy recover of some specific user mailbox/folder it isn't practical to rely on the shared attachment storage of SIS, also I think is more universal format in case some legal obligation require us to give the e-mail of some user to the authorities, including all the attachments. I would opt for some tradeoff solution if I find a way to enable the altstorage or additional namespace (also with MDBOX) but without SIS so that I can store the old mails with the attachments included and compressed. (zstd does a great job!) Is there any way to do it? It seems to me SIS can't be enabled/disabled for each namespace. zlib_save would benefit if it could be different for each namespace (eg. lz4 or none for the inbox namespace and zstd for the archival) Regards. On 6/28/21 13:42, Josef 'Jeff' Sipek wrote: On Mon, Jun 28, 2021 at 10:00:59 +0100, Pedro Ribeiro wrote: Hello! Thank you for the suggestion. That solved the problem of using layout FS with MBOX storage format. After copying all the mail of the test user to the namespace in this format I've compressed all the storage files with ZSTD and that changed the name with the additional suffix .zst Dovecot seems to need this to be .zstd so I've fixed the names. But ... it doesn't work. Jun 28 08:56:39 ribble dovecot: imap(pribe...@net.ipl.pt)<82609>: Error: Mailbox @HISTZLIB/IPLNet: stat(/mnt/mail-hist/historic-fs/net.ipl.pt/ro/pribeiro/mailboxes/IPLNet/mBoX-MeSsAgEs) failed: No such file or directory In that directory the filename is: -rw--- 1 vmail vmail 853M Jun 25 17:25 mBoX-MeSsAgEs.zstd What am I doing wrong? Hm. It is possible that it just doesn't work. mbox doesn't get a lot of attention these days - its support is more of a migration tool. Out of curiosity, why do you use mbox? In your earlier email you said that you want a self contained format. Why? What's the goal? Jeff. regards! On 24/06/2021 14:53, Josef 'Jeff' Sipek wrote: On Thu, Jun 24, 2021 at 10:35:24 +0100, Pedro Ribeiro wrote: Hello everyone! Our archive namespace is kept in MBOX format with Maildir++ layout due to: * Need to have the email from all users/folders self contained (our base namespace uses MDBOX with single instance storage of attachments) * MBOX/FS layout isn't supported because some folders have messages and subfolders. You should be able to use the fs layout if you specify a dirname: https://doc.dovecot.org/configuration_manual/mail_location/mbox/mboxchildfolders/#messages-in-named-file Then, the compression suffix being added shouldn't matter. Jeff. -- Best regards, =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Pedro Ribeiro Politécnico de Lisboa, Serviços da Presidência Departamento de Sistemas de Informação e Comunicações Phone: +351 210 464 700 (general) / VoIP: 80100 Helpdesk:helpd...@net.ipl.pt /https://www.net.ipl.pt =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -- Best regards, =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Pedro Ribeiro Politécnico de Lisboa, Serviços da Presidência Departamento de Sistemas de Informação e Comunicações Phone: +351 210 464 700 (general) / PBX Ext.: 80100 Helpdesk: helpd...@net.ipl.pt / https://www.net.ipl.pt =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= smime.p7s Description: S/MIME Cryptographic Signature
[Dovecot] Pigeon Sieve, redirect action and SPF
Since I've upgraded to dovecot 2.0.13 + Pigeonhole 0.2.3 (Gentoo package) I've received a few complains of users about rejected messages. Investigating the problem, I've seen that when the external sender server publishes SPF information, when some message is sent from there to one of my users that has a Sieve redirect action active to another external system (that does SPF validation), the message is rejected because our system only changes the envelope "rcpt to" in the redirection and the "mail from" remains the original. When the end server does the SPF validation it fails because my server isn't in the IP allow list for the domain of the original sender. I never seen this problem in the old Dovecot+CMUSieve. Shouldn't the sender be changed in the envelope "mail from" from the original one to the recipient that made the Sieve redirection? Keep the excellent work with dovecot and related projects! TIA! -- Best regards, =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Pedro Ribeiro IPLNet - Rede de dados e comunicações Instituto Politécnico de Lisboa (IPL) Mail: mailto:pribeiro AT net.ipl.pt VoIP: sip:pribeiro AT net.ipl.pt =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Re: The future of SIS
in: https://youtu.be/s- JYrjCKshA?feature=shared&t=912 --- Original Message --- On Friday, October 13th, 2023 at 17:15, Sebastian Marsching sebast...@marsching.com wrote: Hi, I am currently in the process of planning a new deployment of Dovecot. I was planning to use mdbox or sdbox with “mail_attachment_fs = sis posix”, but I stumbled across the following notice in the documentation for Dovecot 3.0 ___ dovecot mailing list - - dovecot@dovecot.org To unsubscribe send an email to dovecot- le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot- le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org -- Com os melhores cumprimentos, [https://www.net.ipl.pt/ipl_img/logo_ipl_email.png] Pedro Ribeiro Departamento_de_Sistemas_de_Informação_e_Comunicações_-_IPLNet Serviços da Presidência Telf. +351 210 464 700 / Ext. 80101 smime.p7s Description: S/MIME Cryptographic Signature ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: The future of SIS
Hello everyone! I'm reviving the topic just to add that after reconstructing our storage with SIS disabled the occupied space increased from 5.3TB to 9.6TB, almost doubling! It's a feature promoting storage efficiency, I think it demands some ponderation the advantages of keeping or improving the module. I just have to thank all the people involved in this software for the great work and contribution to the community, with or without SIS in the future! regards. On 16/10/2023 14:00, Chris Candreva wrote: On Mon, 16 Oct 2023, Marc wrote: Is this feature really useful? I can imagine if you are twitter or ig and everyone is posting the same video this could be usefull. Are there any stats on this available, so you know what to expect implementing deduplication. In an office where people insist on mailing documents to everyone, and using email as a document storage system, yes, it is very useful. -- Com os melhores cumprimentos, [https://www.net.ipl.pt/ipl_img/logo_ipl_email.png] Pedro Ribeiro Departamento_de_Sistemas_de_Informação_e_Comunicações_-_IPLNet Serviços da Presidência Telf. +351 210 464 700 / Ext. 80101 smime.p7s Description: S/MIME Cryptographic Signature ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
