Re: What does Solr index do and how to handle its high avaliablity?

2019-06-16 Thread luckydog xf via dovecot
Thanks a lot.

On Sat, Jun 15, 2019 at 11:33 AM Shawn Heisey via dovecot <
dovecot@dovecot.org> wrote:

> On 6/14/2019 2:11 AM, luckydog xf via dovecot wrote:
> >And based on
> https://dovecot.org/pipermail/dovecot/2019-April/115575.html
> > I'm going to use an VIP to host 2 mail servers. Currently, it works in
> > fail over and fail back test except solr index, so how to resolve this?
>
> Solr has high availability options.  Probably the easiest is SolrCloud,
> because the legacy master-slave replication option basically has the
> master as a single point of failure.  Switching a slave to master is a
> very manual job.  SolrCloud is a true cluster -- no masters and no slaves.
>
> Normally I would suggest a load balancer in front of Solr, but with
> SolrCloud and this usage, you could have a VIP switch between two hosts.
>   You will need at least three servers for a redundant SolrCloud
> install, because ZooKeeper absolutely requires three servers for
> redundancy.  SolrCloud is Solr+ZooKeeper.  Only two of the servers would
> need to run Solr, though.  The third server would only need to run
> ZooKeeper, and normally the system requirements for that are very low.
>
> > Is it possible to put dovecot index on shared storage like NFS?
>
> Solr does not do well on network file systems.  They usually don't offer
> the file locking capability that Lucene wants.  Solr is written using
> the Lucene API.
>
> And you can't have two running Solr servers using the same index
> directory even if you disable file locking so that NFS works.  Each
> server needs its own copy of the index.
>
> > How to rebuild if I don't put index data on shared storage in case of
> > fail over?
>
> Building and rebuilding is accomplished by dovecot.  Here's a wiki page
> for rebuilding Solr indexes.  Admittedly it falls into the "not all that
> helpful" category:
>
> https://wiki.apache.org/solr/HowToReindex
>
> Thanks,
> Shawn
>


Re: What does Solr index do and how to handle its high avaliablity?

2019-06-14 Thread luckydog xf via dovecot
Just read docs, solr in dovecot seems as index of emails to accelarate the
speed of mail searching.

On Fri, Jun 14, 2019 at 4:11 PM luckydog xf  wrote:

> Hi, guys,
>
>Can you give me an example of solr usage in dovecot?  As far as I know,
> you can search email easily by MUA like outlook, so which role does solr
> play?
>
>   And based on
> https://dovecot.org/pipermail/dovecot/2019-April/115575.html
>
> I'm going to use an VIP to host 2 mail servers. Currently, it works in
> fail over and fail back test except solr index, so how to resolve this?
>
> Is it possible to put dovecot index on shared storage like NFS?
>
> How to if it's a yes.  It seems it's under /var/solr/data/dovecot/data/
>
> How to rebuild if I don't put index data on shared storage in case of fail
> over?
>
> Thanks,
>
>
>
>


What does Solr index do and how to handle its high avaliablity?

2019-06-14 Thread luckydog xf via dovecot
Hi, guys,

   Can you give me an example of solr usage in dovecot?  As far as I know,
you can search email easily by MUA like outlook, so which role does solr
play?

  And based on https://dovecot.org/pipermail/dovecot/2019-April/115575.html

I'm going to use an VIP to host 2 mail servers. Currently, it works in fail
over and fail back test except solr index, so how to resolve this?

Is it possible to put dovecot index on shared storage like NFS?

How to if it's a yes.  It seems it's under /var/solr/data/dovecot/data/

How to rebuild if I don't put index data on shared storage in case of fail
over?

Thanks,


Re: Sis to deduplicate attachments does not work?

2019-04-28 Thread luckydog xf via dovecot
Thanks for your sharing, Daniel.

On Wed, Apr 24, 2019 at 4:12 PM Daniel Miller  wrote:

> On April 23, 2019 10:54:38 PM luckydog xf  wrote:
>
>> Is it worthwile to use dbox? seeing from
>> http://www.linuxmail.info/mbox-maildir-mail-storage-formats/ it may
>> cause file lock and easy to corrupt.
>>
>> As with everything - it depends. You're asking me so these are *my*
> opinions - and I do not claim to be anything more than a hobbyist/tinkerer
> when the comes to this.
>
> mbox has potential use for long term read-only archives - I see no reason
> to use it for live mailboxes.
>
> maildir is undoubtedly the least susceptible to corruption. It's also the
> slowest format for reading. How slow is "slow" depends on your hardware -
> it may be imperceptible with enough RAM and SSD's - or it may result in
> user complaints with large mailboxes.
>
> dbox is Dovecot's preferred format. I know Timo has put a lot of effort
> into it. sdbox is similar to maildir in that each mail is a separate file.
> mdbox significantly reduces the number of files which can make file-based
> backups faster. Both dbox formats are dependent on their index files.
>
> If you've got good hardware, including a proper UPS, I'd recommend dbox
> (my server is presently using sdbox). With large mailboxes and file-based
> backups you'll benefit from mdbox. When reliability is the #1 concern above
> anything else - use maildir. Depending on your use SIS can have significant
> impact on storage requirements - but storage these days is relatively cheap.
>
> I haven't seen much feedback from users actively using SIS - I'd love to
> hear from high traffic sites with SIS experience to know if the corruption
> issues have been resolved. In my case there was at least a 30% reduction in
> space but I had too many errors - admittedly it's been a couple years since
> I last tried it.
>
> --
> Daniel
>


Re: Sis to deduplicate attachments does not work?

2019-04-24 Thread luckydog xf via dovecot
It seems Maildir is the safest mail format right now, as long as you could
accept little performance and disk cost penalty.



On Wed, Apr 24, 2019 at 9:01 PM Tanstaafl via dovecot 
wrote:

> On Wed Apr 24 2019 04:12:30 GMT-0400 (Eastern Standard Time), Daniel
> Miller via dovecot  wrote:
> > If you've got good hardware, including a proper UPS, I'd recommend dbox
> > (my server is presently using sdbox). With large mailboxes and
> > file-based backups you'll benefit from mdbox. When reliability is the #1
> > concern above anything else - use maildir. Depending on your use SIS can
> > have significant impact on storage requirements - but storage these days
> > is relatively cheap.
>
> My plan when I roll out my new server this year is to use mdbox, but put
> the indexes and other important meta data on a smallish volume using
> either ZFS or BTRFS, for the automatic self-healing capabilities (and
> the ability to expand it if necessary).
>
> This pretty much eliminates the worry about data loss from index file
> corruption.
>
> > I haven't seen much feedback from users actively using SIS - I'd love to
> > hear from high traffic sites with SIS experience to know if the
> > corruption issues have been resolved. In my case there was at least a
> > 30% reduction in space but I had too many errors - admittedly it's been
> > a couple years since I last tried it.
>
> I never tried it because of the problems with respect to backup/restore,
> and if I'm not mistaken, those problems have not been resolved.
>
> Maybe its a design issue...
>
> Or maybe it just isn't a high enough priority, like the missing
> x-original-to header in the LMTP code that will still prevent me from
> being able to use the otherwise much better LMTP delivery agent.
>


Sis to deduplicate attachments does not work?

2019-04-23 Thread luckydog xf via dovecot
Hi, I use sis to deduplicate attachments, here is my `doveconf -n`

auth_cache_size = 10 M
auth_failure_delay = 5 secs
auth_mechanisms = plain login
auth_socket_path = /var/run/dovecot/auth-userdb
auth_ssl_username_from_cert = yes
auth_username_format = %Ln
default_vsz_limit = 512 M
lmtp_rcpt_check_quota = yes
mail_attachment_detection_options = add-flags-on-save
mail_attachment_dir = /var/mail/mail_attachment/
mail_debug = yes
mail_gid = vmail
mail_location = maildir:/var/mail/%n/Maildir
mail_plugins = quota fts fts_solr
mail_privileged_group = vmail
mail_uid = vmail
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope encoded-character
vacation subaddress comparator-i;ascii-numeric relational regex imap4flags
copy include variables body enotify environment mailbox date index ihave
duplicate mime foreverypart extracttext
namespace inbox {
  inbox = yes
  location =
  mailbox Drafts {
special_use = \Drafts
  }
  mailbox Junk {
auto = subscribe
special_use = \Junk
  }
  mailbox Sent {
auto = subscribe
special_use = \Sent
  }
  mailbox Trash {
auto = subscribe
special_use = \Trash
  }
  prefix =
}
passdb {
  args = /etc/dovecot/dovecot-ldap.conf.ext
  driver = ldap
}
plugin {
  fts = solr
  fts_autoindex = yes
  fts_autoindex_exclude = \Junk
  fts_autoindex_exclude2 = \Trash
  fts_solr = break-imap-search url=http://localhost:8983/solr/dovecot/
  quota = maildir:User quota
  quota_grace = 10%%
  quota_max_mail_size = 5M
  quota_over_flag_lazy_check = yes
  quota_over_flag_value = TRUE
  quota_rule = *:storage=100M
  quota_warning = storage=65%% quota-warning 65 %u
  quota_warning2 = storage=60%% quota-warning 60 %u
  sieve = file:~/sieve;active=~/.dovecot.sieve
}
protocols = imap lmtp sieve
service auth-worker {
  user = $default_internal_user
}
service auth {
  unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0640
user = postfix
  }
  unix_listener auth-userdb {
mode = 0777
user = $default_internal_user
  }
  user = $default_internal_user
}
service imap-login {
  inet_listener imap {
port = 0
  }
  inet_listener imaps {
port = 993
ssl = yes
  }
}
service managesieve-login {
  inet_listener sieve {
port = 4190
  }
  process_min_avail = 0
  service_count = 1
  vsz_limit = 128 M
}
service pop3-login {
  inet_listener pop3 {
port = 0
  }
  inet_listener pop3s {
port = 0
  }
}
service quota-warning {
  executable = script /usr/local/bin/quota-warning.sh
  unix_listener quota-warning {
user = vmail
  }
  user = vmail
}
service stats {
  unix_listener stats-writer {
mode = 0666
  }
}
service submission-login {
  inet_listener submission {
port = 0
  }
}
ssl = required
ssl_cert = 

Re: SolrCore 'dovecot' is not available due to init failure: fieldType 'text_general' not found in the schema

2019-04-23 Thread luckydog xf via dovecot
Thanks, I used solr-config-7.7.0.xml as a replacment, it works.

I'll compare solr-schema-7.7.0.xml with dovecot-2.3.5.2/doc/solr-schema.xml
and find out the difference.

Thanks.

On Tue, Apr 23, 2019 at 11:46 AM Shawn Heisey via dovecot <
dovecot@dovecot.org> wrote:

> On 4/22/2019 9:31 PM, luckydog xf via dovecot wrote:
> > https://wiki.dovecot.org/Plugins/FTS/Solr
> > Only offers a solr-7.7.0 solrconfig.xml, does it apply to solr-8.0.0?
>
> If the config was actually designed for 7.7, then it will work in 8.0.
> If it was designed for 5.x or 6.x, there's a chance it won't work.
>
> It sounds like you have a solrconfig.xml file and a schema file that are
> not matched to each other.
>
> The schema file found here looks to me like it will work in 8.0:
>
>
> https://raw.githubusercontent.com/dovecot/core/master/doc/solr-schema-7.7.0.xml
>
> I think instead of using a solrconfig.xml that comes with Solr, you
> should be using the one made for dovecot:
>
>
> https://raw.githubusercontent.com/dovecot/core/master/doc/solr-config-7.7.0.xml
>
> I do see a potential problem with that config, though ... there is
> config that sets the df parameter (default field) to a field named
> "_text_" (with underscores) ... this field does not exist in the schema.
>
> Thanks,
> Shawn
>


Re: SolrCore 'dovecot' is not available due to init failure: fieldType 'text_general' not found in the schema

2019-04-22 Thread luckydog xf via dovecot
https://wiki.dovecot.org/Plugins/FTS/Solr

Only offers a solr-7.7.0 solrconfig.xml, does it apply to solr-8.0.0?


On Tue, Apr 23, 2019 at 11:18 AM luckydog xf  wrote:

> Here is solrconfig.xml, I removed comments.
> 
>
> 
> 
>   8.0.0
>regex=".*\.jar"/>
>regex="solr-cell-\d.*\.jar"/>
>regex=".*\.jar"/>
>regex="solr-clustering-\d.*\.jar"/>
>regex=".*\.jar"/>
>regex="solr-langid-\d.*\.jar"/>
>regex=".*\.jar"/>
>regex="solr-velocity-\d.*\.jar"/>
>regex="solr-ltr-\d.*\.jar"/>
>   ${solr.data.dir:}
>class="${solr.directoryFactory:solr.NRTCachingDirectoryFactory}"/>
>   
>   
> ${solr.lock.type:native}
>   
>   
>   
> 
>   ${solr.ulog.dir:}
>name="numVersionBuckets">${solr.ulog.numVersionBuckets:65536}
> 
> 
>   ${solr.autoCommit.maxTime:15000}
>   false
> 
> 
>   ${solr.autoSoftCommit.maxTime:-1}
> 
>   
>   
> ${solr.max.booleanClauses:1024}
>  autowarmCount="0"/>
>  autowarmCount="0"/>
>  autowarmCount="0"/>
>  initialSize="0" autowarmCount="10" regenerator="solr.NoOpRegenerator"/>
> true
> 20
> 200
> 
>   
> 
> 
>   
> 
> false
>   
>   
> 
>   
>   
> 
>   explicit
>   10
> 
>   
>   
> 
>   explicit
>   json
>   true
> 
>   
>useParams="query,facets,velocity,browse">
> 
>   explicit
> 
>   
>path="/update/**,/query,/select,/tvrh,/elevate,/spell,/browse">
> 
>   _text_
> 
>   
>class="solr.extraction.ExtractingRequestHandler">
> 
>   true
>   _text_
> 
>   
>   
> text_general
> 
>   default
>   _text_
>   solr.DirectSolrSpellChecker
>   internal
>   0.5
>   2
>   1
>   5
>   4
>   0.01
> 
>   
>   
> 
>   default
>   on
>   true
>   10
>   5
>   5
>   true
>   true
>   10
>   5
> 
> 
>   spellcheck
> 
>   
>   
>   
> 
>   true
> 
> 
>   tvComponent
> 
>   
>   
>   
> 
>   true
>   false
> 
> 
>   terms
> 
>   
>   
> string
>   
>startup="lazy">
> 
>   explicit
> 
> 
>   elevator
> 
>   
>   
> 
>class="solr.highlight.GapFragmenter">
> 
>   100
> 
>   
>   
> 
>   70
>   0.5
>   [-\w ,/\n\"']{20,200}
> 
>   
>class="solr.highlight.HtmlFormatter">
> 
>   
>   
> 
>   
>   
>class="solr.highlight.SimpleFragListBuilder"/>
>class="solr.highlight.SingleFragListBuilder"/>
>class="solr.highlight.WeightedFragListBuilder"/>
>class="solr.highlight.ScoreOrderFragmentsBuilder"/>
>class="solr.highlight.ScoreOrderFragmentsBuilder">
> 
>   
>   
> 
>   
>class="solr.highlight.SimpleBoundaryScanner">
> 
>   10
>   .,!?
> 
> 
>   
>class="solr.highlight.BreakIteratorBoundaryScanner">
> 
>   WORD
>   en
>   US
> 
>   
> 
>   
>   
>name="remove-blank"/>
>name="field-name-mutating">
> [^\w-\.]
> _
>   
>name="parse-boolean"/>
>name="parse-long"/>
>name="parse-double"/>
>name="parse-date">
> 
>   -MM-dd['T'[HH:mm[:ss[.SSS]][z
>   -MM-dd['T'[HH:mm[:ss[,SSS]][z
>   -MM-dd HH:mm[:ss[.SSS]][z
>   -MM-dd HH:mm[:ss[,SSS]][z
>   [EEE, ]dd MMM  HH:mm[:ss] z
>   , dd-MMM-yy HH:mm:ss z
>   EEE MMM ppd HH:mm:ss [z ]
> 
>   
>name="add-schema-fields">
> 
>   java.lang.String
>   text_general
>   
> *_str
> 256
>   
>   true
> 
> 
>   java.lang.Boolean
>   booleans
> 
> 
>   java.util.Date
>   pdates
> 
> 
>   java.lang.Long
>   java.lang.Integer
>   plongs
> 
> 
>   java.lang.Number
>   pdoubles
> 
>   
>default="${update.autoCreateFields:true}"
> processor="uuid,remove-blank,field-name-mutating,parse-boolean,parse-long,parse-double,parse-date,add-schema-fields">
> 
> 
> 
>   
>   
> text/plain; charset=UTF-8
>   
>startup="lazy">
> ${velocity.template.base.dir:}
>  name="solr.resource.loader.enabled">${velocity.solr.resource.loader.enabled:true}
>  name="params.resource.loader.enabled">${velocity.params.resource.loader.enabled:false}
>   
>   
> 5
>   
> 
>
>
>
> On Tue, Apr 23, 2019 at 10:57 AM luckydog xf  wrote:
>
>> Hello, it seems an  mismatch of schema file provided by dovecot-2.3.5.2
>>
>> [root@mail conf]# pwd
>> /var/solr/data/dovecot/conf
>>
>> # Below solrconfig.xml is from Solr-8.0.0.
>>
>> [root@mail conf]# grep text_general solrconfig.xml
>>
>> text_general
>>field types. Text content will be indexed a

Re: SolrCore 'dovecot' is not available due to init failure: fieldType 'text_general' not found in the schema

2019-04-22 Thread luckydog xf via dovecot
Here is solrconfig.xml, I removed comments.




  8.0.0
  
  
  
  
  
  
  
  
  
  ${solr.data.dir:}
  
  
  
${solr.lock.type:native}
  
  
  

  ${solr.ulog.dir:}
  ${solr.ulog.numVersionBuckets:65536}


  ${solr.autoCommit.maxTime:15000}
  false


  ${solr.autoSoftCommit.maxTime:-1}

  
  
${solr.max.booleanClauses:1024}




true
20
200

  


  

false
  
  

  
  

  explicit
  10

  
  

  explicit
  json
  true

  
  

  explicit

  
  

  _text_

  
  

  true
  _text_

  
  
text_general

  default
  _text_
  solr.DirectSolrSpellChecker
  internal
  0.5
  2
  1
  5
  4
  0.01

  
  

  default
  on
  true
  10
  5
  5
  true
  true
  10
  5


  spellcheck

  
  
  

  true


  tvComponent

  
  
  

  true
  false


  terms

  
  
string
  
  

  explicit


  elevator

  
  

  

  100

  
  

  70
  0.5
  [-\w ,/\n\"']{20,200}

  
  

  
  

  
  
  
  
  
  
  

  
  

  
  

  10
  .,!?


  
  

  WORD
  en
  US

  

  
  
  
  
[^\w-\.]
_
  
  
  
  
  

  -MM-dd['T'[HH:mm[:ss[.SSS]][z
  -MM-dd['T'[HH:mm[:ss[,SSS]][z
  -MM-dd HH:mm[:ss[.SSS]][z
  -MM-dd HH:mm[:ss[,SSS]][z
  [EEE, ]dd MMM  HH:mm[:ss] z
  , dd-MMM-yy HH:mm:ss z
  EEE MMM ppd HH:mm:ss [z ]

  
  

  java.lang.String
  text_general
  
*_str
256
  
  true


  java.lang.Boolean
  booleans


  java.util.Date
  pdates


  java.lang.Long
  java.lang.Integer
  plongs


  java.lang.Number
  pdoubles

  
  



  
  
text/plain; charset=UTF-8
  
  
${velocity.template.base.dir:}
${velocity.solr.resource.loader.enabled:true}
${velocity.params.resource.loader.enabled:false}
  
  
5
  




On Tue, Apr 23, 2019 at 10:57 AM luckydog xf  wrote:

> Hello, it seems an  mismatch of schema file provided by dovecot-2.3.5.2
>
> [root@mail conf]# pwd
> /var/solr/data/dovecot/conf
>
> # Below solrconfig.xml is from Solr-8.0.0.
>
> [root@mail conf]# grep text_general solrconfig.xml
>
> text_general
>field types. Text content will be indexed as "text_general" as
>   text_general
>
> # schema is from /usr/share/doc/dovecot/solr-schema.xml
>
> dovecot-2.3.5.2 and the latest solr-8.0.0.
>
> It seems XMLs do not match each other. How can I fix this problem?
>
> Thanks.
>
>
>


SolrCore 'dovecot' is not available due to init failure: fieldType 'text_general' not found in the schema

2019-04-22 Thread luckydog xf via dovecot
Hello, it seems an  mismatch of schema file provided by dovecot-2.3.5.2

[root@mail conf]# pwd
/var/solr/data/dovecot/conf

# Below solrconfig.xml is from Solr-8.0.0.

[root@mail conf]# grep text_general solrconfig.xml

text_general
   field types. Text content will be indexed as "text_general" as
  text_general

# schema is from /usr/share/doc/dovecot/solr-schema.xml

dovecot-2.3.5.2 and the latest solr-8.0.0.

It seems XMLs do not match each other. How can I fix this problem?

Thanks.


Re: High availability of Dovecot

2019-04-11 Thread luckydog xf via dovecot
It seems that  we got 2 solutions.

1. use DNS MX record and dsync plugin of dovecot. No shared storage.
2. use VIP and shared storage.

I'll try both of them, thank you guys.

On Thu, Apr 11, 2019 at 8:45 PM Gerald Galster via dovecot <
dovecot@dovecot.org> wrote:

>
>
> > Am 11.04.2019 um 13:45 schrieb Patrick Westenberg via dovecot <
> dovecot@dovecot.org>:
> >
> > Gerald Galster via dovecot schrieb:
> >
> >> mail1.yourdomain.com  IN A 192.168.10.1
> >> mail2.yourdomain.com  IN A 192.168.20.1
> >>
> >> mail.yourdomain.com   IN A 192.168.10.1
> >> mail.yourdomain.com   IN A 192.168.20.1
> >>
> >>
> >> mail1/mail2 is for direct connection (MTAs)
> >>
> >> Your users (outlook, thunderbird, ...) connect to mail.yourdomain.com
> >>  which returns the two ip addresses.
> >>
> >> In this scenario MUA just connects to mail.yourdomain.com
> >>  and randomly uses one of the two ips. You
> >> can't control which one, but this gives you active/active loadbalancing.
> >> In case one server is down the MUA just uses the other ip.
> >
> > Are you sure that this is working?
>
>
> yes, I'm running a two node dsync cluster in production for a few years
> without issues.
> The system was even working during a whole datacenter outage because the
> nodes reside
> in different, distant locations. I would'nt use a filesystem like ceph
> with distant
> locations due to latency issues. dsync replication is asynchronous, so
> there is no problem.
>
> Most cluster systems that use drbd, ceph, keepalived, pacemaker, whatever
> are operated
> within a single datacenter or datacenter park. If the datacenter goes
> down, your
> cluster is not reachable anymore. This is a rare event but within 10-15
> years it happens
> to a lot of datacenters.
>
> Best regards
> Gerald
>
>
>


High availability of Dovecot

2019-04-11 Thread luckydog xf via dovecot
Hi, list,

 I'm going to deploy postfix + dovecot + CephFS( as Mail Storage).
Basically I want to use two servers for them, which  is kind of HA.

My idea is that using keepalived or Pacemaker to host a VIP, which
could fail over the other server once one is down. And I'll use Haproxy or
Nginx to schedule connections to one of those server based on source IP(
Session stickiness),  I'll use VIP as DNS record.etc, is my plan doable?

   I know MX could be server ones with different priority. But I think it
brings along shortage that DNS couldn't know Email server is up or down, it
just returns results to MUA, right?

   Thanks for any suggestions and ideas.

-


protocols: Unknown protocol: sieve

2019-04-10 Thread luckydog xf via dovecot
Hi, list,

I downloaded dovecot-2.3-pigeonhole-0.5.5.tar.gz and installed it,
after I enabled

#/etc/dovecot/conf.d/20-managesieve.conf
protocols = $protocols sieve

it said " protocols: Unknown protocol: sieve"

What's wrong?"

Thanks,


where shall I enforce sieve and quota plugins

2019-04-02 Thread luckydog xf via dovecot
Hello, guys,

   I'm going to using sieve and quota plugins, but I'm not sure where shall
I enforce against properly?

   I see somebody uses them against 20-imap.conf, 15-lda.conf, or
20-lmtp.conf

   I use LMTP as MDA, so where is the correct location to call these
plugins and why?

   Thanks,


Re: Why is 'sent' folder missing in my MUA(email client)

2019-03-31 Thread luckydog xf via dovecot
I wish I had read some docs, I get the answer.

The reason is that Sent folder should be subscribe.

#  /etc/dovecot/conf.d/15-mailboxes.conf
  auto = subscribe


On Sun, Mar 31, 2019 at 4:09 PM luckydog xf  wrote:

> hello,
>
> I'm successfully send and receive emails by postfix and dovecot, but
> folder name 'Sent' is gone, all sent emails are located in Drafts folder.
>
> Anything wrong? Guess it has something to do with mailbox and location.
>
>Here is `doveconf -n`
> --
> auth_cache_size = 1 M
> auth_debug_passwords = yes
> auth_mechanisms = plain login
> auth_ssl_username_from_cert = yes
> auth_verbose = yes
> auth_verbose_passwords = yes
> import_environment = TZ
> login_trusted_networks = 172.16.0.0/12
> mail_location = maildir:/var/mail/%n/Maildir
> mail_privileged_group = mail
> namespace inbox {
>   inbox = yes
>   location =
>   mailbox Drafts {
> special_use = \Drafts
>   }
>   mailbox Junk {
> special_use = \Junk
>   }
>   mailbox Sent {
> special_use = \Sent
>   }
>   mailbox "Sent Messages" {
> special_use = \Sent
>   }
>   mailbox Trash {
> special_use = \Trash
>   }
>   prefix =
> }
> passdb {
>   args = /etc/dovecot/dovecot-sql.conf.ext
>   driver = sql
> }
> protocols = imap lmtp
> service auth-worker {
>   user = $default_internal_user
> }
> service auth {
>   unix_listener /var/spool/postfix/private/auth {
> mode = 0666
>   }
> }
> service imap-login {
>   inet_listener imap {
> port = 0
>   }
>   inet_listener imaps {
> port = 993
> ssl = yes
>   }
> }
> service lmtp {
>   unix_listener lmtp {
> mode = 0666
>   }
> }
> service pop3-login {
>   inet_listener pop3 {
> port = 110
>   }
> }
> ssl = required
> ssl_cert =  ssl_dh = # hidden, use -P to show it
> ssl_key = # hidden, use -P to show it
> userdb {
>   driver = prefetch
> }
> userdb {
>   args = uid=mail gid=mail home=/var/mail/%u
>   driver = static
> }
> verbose_proctitle = yes
>
> -
>
>   I also checked mail dir, it has /var/mail/XXX/Maildir/.send/
>
>   So anything wrong?
>
> Thanks,
>


Why is 'sent' folder missing in my MUA(email client)

2019-03-31 Thread luckydog xf via dovecot
hello,

I'm successfully send and receive emails by postfix and dovecot, but
folder name 'Sent' is gone, all sent emails are located in Drafts folder.

Anything wrong? Guess it has something to do with mailbox and location.

   Here is `doveconf -n`
--
auth_cache_size = 1 M
auth_debug_passwords = yes
auth_mechanisms = plain login
auth_ssl_username_from_cert = yes
auth_verbose = yes
auth_verbose_passwords = yes
import_environment = TZ
login_trusted_networks = 172.16.0.0/12
mail_location = maildir:/var/mail/%n/Maildir
mail_privileged_group = mail
namespace inbox {
  inbox = yes
  location =
  mailbox Drafts {
special_use = \Drafts
  }
  mailbox Junk {
special_use = \Junk
  }
  mailbox Sent {
special_use = \Sent
  }
  mailbox "Sent Messages" {
special_use = \Sent
  }
  mailbox Trash {
special_use = \Trash
  }
  prefix =
}
passdb {
  args = /etc/dovecot/dovecot-sql.conf.ext
  driver = sql
}
protocols = imap lmtp
service auth-worker {
  user = $default_internal_user
}
service auth {
  unix_listener /var/spool/postfix/private/auth {
mode = 0666
  }
}
service imap-login {
  inet_listener imap {
port = 0
  }
  inet_listener imaps {
port = 993
ssl = yes
  }
}
service lmtp {
  unix_listener lmtp {
mode = 0666
  }
}
service pop3-login {
  inet_listener pop3 {
port = 110
  }
}
ssl = required
ssl_cert =