March 2019 - dovecot - dovecot.org

Assistance with doveadm backup...
by SH Development 11 Mar '19

11 Mar '19

I am having trouble locating examples of how to use doveadm backup. All the examples I see are for sync. I simply want to create a backup to a network volume of the email server's vmail folders. The goal here is to have a reasonably current backup should the main drive on the email server go south. We currently authenticate our users from a mysql database. User’s mailboxes are stored as domainname/username/Maildir I assume what I will wind up on the network volume is a duplicate directory structure as the vmail folder on the email server? Can someone help get me started here? Jeff

7 13

readonly archive folders using squashfs
by Natu 11 Mar '19

11 Mar '19

I have a dovecot server running under CentOS using maildir format. Due to the issue with minimum blocksize for files I would like to offer some kind of readonly archive using something like the compressed squashfs where I would move messages to be archived to a maildir folder and then convert "cur" directory into a squashfs and mount it in place of the original directory so my biggest users could have readonly access to older messages without it using so much disk space. Has anyone tried anything like this before and is dovecot likely to complain about the readonly cur directory? If the complaints are minimal and didn't cause other problems it might be ok. Any better ideas to implement something like this? Thank You, Natu

2 2

Re: Auto MX Email Client configuration, the right way?
by Davide Marchi 10 Mar '19

10 Mar '19

> Now I've seen the new RFC 6186 specification > (https://tools.ietf.org/html/rfc6186) that describe a "DNS way" to > achieve the same goal. > > [..] > again: > [..] > When a user identifier is required, MUAs MUST first > use the full email address provided by the user, and if that > results > in an authentication failure, SHOULD fall back to using the "local- > part" extracted from the email address. This is in line with the > guidance outlined in Section 5. If both these user identifiers > result in authentication failure, the MUA SHOULD prompt the user > for > a valid identifier. > [..] > > here I have the biggest doubt, in fact Thunderbird often uses only the > username and not the whole email address, both for incoming and > outgoing > server... > Is any of you using this second way? And possibly, do you kniw if it > works with different clients (desktop and mobile)? I've made some tests and this solution seems very serviceable, for the only exception for the user name on Thunderbird. Unlike what is stated in this RFC, Thunderbird "takes" only the name and not the entire email address as the username. Anyone knows if is it possible to communicate the username type via RFC? Many thanks again! Davide

2 1

GSSAPI and usernames, not Kerberos ticket names
by Dmitry Donskih 09 Mar '19

09 Mar '19

Hi all, I've got a Dovecot v2.3.3 IMAP with GSSAPI auth set up. This server is in main domain, 'contoso.com'. I also have several subdomains. My problem is usernames with GSSAPI authentication: When I try to login as 'user' or as 'user(a)CONTOSO.COM' - everything works. But, 'user(a)contoso.com' auth fails. But when I try to login as subdomain user, 'user2' - it fails to login. 'user2(a)sub.contoso.com' fails also. However, 'user2(a)SUB.CONTOSO.COM' works ok. It looks like PAM uses domain part of login as Kerberos realm name, regardless of Kerberos domain-realm mapping. Also, if domain part is not specified, PAM (Kerberos?) fails to determine non-default realm. What am I missing? Is there a way to use traditional 'user@domain' login names with PAM/GSSAPI, instead of Kerberos ticket names? Or maybe to tell PAM module to convert domain part of username to uppercase before using? Thanks on any help or advice. ===== dovecot.conf: ===== auth_mechanisms = gssapi plain login external auth_gssapi_hostname = "$ALL" auth_krb5_keytab = /etc/krb5.keytab auth_default_realm = passdb { driver = pam args = cache_key=%d%r%n failure_show_msg=yes dovecot } userdb { driver = static args = uid=502 gid=502 home=/var/vmail/%L{auth_domain}/%L{auth_username} mail=maildir:/var/vmail/%L{auth_domain}/%L{auth_username}/Maildir allow_all_users=yes } ===== ===== pam.d/dovecot: ===== auth sufficient pam_krb5.so use_first_pass account [default=bad success=ok user_unknown=ignore] pam_krb5.so password sufficient pam_krb5.so use_authtok session optional pam_krb5.so ===== ===== krb5.conf: ===== [libdefaults] default_realm = CONTOSO.COM dns_lookup_realm = true dns_lookup_kdc = true [realms] CONTOSO.COM = { kdc = dc.contoso.com:88 admin_server = dc.contoso.com:749 } [domain_realm] contoso.com = CONTOSO.COM .contoso.com = CONTOSO.COM sub.contoso.com = CONTOSO.COM .sub.contoso.com = CONTOSO.COM SUB.CONTOSO.COM = CONTOSO.COM .SUB.CONTOSO.COM = CONTOSO.COM [appdefaults] pam = { ticket_lifetime = 36000 renew_lifetime = 36000 forwardable = true krb4_convert = false } ===== klist server ==== Default principal: imap/mail2.contoso.com(a)CONTOSO.COM ===== klist client ==== Default principal: user2(a)SUB.CONTOSO.COM ===== Logging in with user2(a)SUB.CONTOSO.COM - OK: ===== auth: Debug: client in: AUTH 1 GSSAPI service=imap secured=tls session=.... auth: Debug: gssapi(?,192.168.....,<MR1yvq6DftfAqAoP>): Using all keytab entries auth: Debug: client passdb out: CONT 1 auth: Debug: client in: CONT<hidden> auth: Debug: gssapi(user2(a)sub.contoso.com,192.168....,<MR1yvq6DftfAqAoP>): security context state completed. auth: Debug: client passdb out: CONT 1 YIGVB.... auth: Debug: client in: CONT<hidden> auth: Debug: gssapi(user2(a)sub.contoso.com,192.168.....,<MR1yvq6DftfAqAoP>): Negotiated security layer auth: Debug: client passdb out: CONT 1 BQQF/..... auth: Debug: client in: CONT<hidden> auth: Debug: pam(user2(a)sub.contoso.com,192.168.....,<MR1yvq6DftfAqAoP>): passdb doesn't support credential lookups auth: Debug: gssapi(user2(a)sub.contoso.com,192.168.....,<MR1yvq6DftfAqAoP>): skipping passdb: mechanism filtered auth: Debug: client passdb out: OK 1 user=user2(a)sub.contoso.com original_user=user2(a)SUB.CONTOSO.COM ===== Logging in with user2(a)sub.contoso.com - FAIL: ===== auth: Debug: client in: AUTH 1 GSSAPI service=imap secured=tls session=... auth: Debug: gssapi(?,192.168....,<Hgh4zq6DhNfAqAoP>): Using all keytab entries auth: Debug: client passdb out: CONT 1 auth: Debug: client in: CONT<hidden> auth: Debug: gssapi(user2(a)sub.contoso.com,192.168....,<Hgh4zq6DhNfAqAoP>): security context state completed. auth: Debug: client passdb out: CONT 1 YIGVB..... auth: Debug: client in: CONT<hidden> auth: Debug: gssapi(user2(a)sub.contoso.com,192.168....,<Hgh4zq6DhNfAqAoP>): Negotiated security layer auth: Debug: client passdb out: CONT 1 BQQF/..... auth: Debug: client in: CONT<hidden> auth: Debug: pam(user2(a)sub.contoso.com,192.168.....,<Hgh4zq6DhNfAqAoP>): passdb doesn't support credential lookups auth: Debug: gssapi(user2(a)sub.contoso.com,192.168.....,<Hgh4zq6DhNfAqAoP>): skipping passdb: mechanism filtered auth: Debug: client passdb out: FAIL 1 user=user2(a)sub.contoso.com original_user=user2(a)SUB.CONTOSO.COM

1 0

Auto MX Email Client configuration, the right way?
by Davide Marchi 09 Mar '19

09 Mar '19

Hi Friends! An opinion. I would like to facilitate the configuration of one's mail client (desktop or mobile) to my users server. Some time ago I asked the same question and you suggested me to use "Automx". So I started of good will and I looked for the Automx documentation. And here the problems started as I found several inconsistencies, even parameters (in official documentation) that produce Apache errors.. to complicate things, different path between deb packages and official version :-) Now I've seen the new RFC 6186 specification (https://tools.ietf.org/html/rfc6186) that describe a "DNS way" to achieve the same goal. [..] 4. Guidance for MUAs By using SRV records as above, MUAs need initially only to prompt the user for their email address [RFC5322]. The "local-part" and "domain" portions are then extracted from the email address by the MUA. The MUA uses the "domain" portion as the service domain to perform SRV lookups for the services it wants to configure. If the SRV lookup is successful, the target FQDN and port for the service can be determined and used to complete MUA configuration. If an SRV record is not found, the MUA will need to prompt the user to enter the FQDN and port information directly, or use some other heuristic. In the case of multiple SRV records returned for a particular service, the MUA MUST use the priority and weight fields in the record to determine which one to use (as per [RFC2782]). [..] again: [..] When a user identifier is required, MUAs MUST first use the full email address provided by the user, and if that results in an authentication failure, SHOULD fall back to using the "local- part" extracted from the email address. This is in line with the guidance outlined in Section 5. If both these user identifiers result in authentication failure, the MUA SHOULD prompt the user for a valid identifier. [..] here I have the biggest doubt, in fact Thunderbird often uses only the username and not the whole email address, both for incoming and outgoing server... Is any of you using this second way? And possibly, do you kniw if it works with different clients (desktop and mobile)? Many many thanks! Davide

3 2

Dovecot v2.3.5 released
by Aki Tuomi 08 Mar '19

08 Mar '19

Hi! We are happy to release dovecot v2.3.5. Please find sources at https://dovecot.org/releases/2.3/dovecot-2.3.5.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.5.tar.gz.sig You can find precompiled binaries at https://repo.dovecot.org/ NEWS: + Lua push notification driver: mail keywords and flags are provided in MessageNew and MessageAppend events. + submission: Implement support for plugins. + auth: When auth_policy_log_only=yes, only log what the policy server response would do without actually doing it. + auth: Always log policy server decisions with auth_verbose=yes - v2.3.[34]: doveadm log errors: Output was missing user/session - lda: Debug log lines could have shown slightly corrupted - login proxy: Login processes may have crashed in various ways when login_proxy_max_disconnect_delay was set. - imap: Fix crash with Maildir+zlib if client disconnects during APPEND - lmtp proxy: Fix potential assert-crash - lmtp/submission: Fix crash when SMTP client transaction times out - submission: Split large XCLIENT commands to 512 bytes per command, so Postfix accepts them. - submission: Fix crash when client sends invalid BURL command - submission: relay backend: VRFY command: Avoid forwarding 500 and 502 replies back to client. - lib-http: Fix potential assert-crash when DNS lookup fails - lib-fts: Fix search query generation when one language ignores a token (e.g. via stopwords). --- Aki Tuomi Open-Xchange Oy

3 5

Re: Removing a mailbox from a dovecot cluster
by Francis 08 Mar '19

08 Mar '19

Le mar. 26 févr. 2019 à 22:58, David Myers <david.myers.24j74(a)gmail.com> a écrit : > Hello Francis, > > I wonder if this is due to how a cluster is configured to function > internally. > > Tell us more about the cluster, is it one of those ‘fancy pants’ high > availability, auto backup heart beat things, or is it more a traditional > multi server (master slave style) setup. > > Either way you may need to disconnect the servers from one another and > delete the offending files / directories either via dove or or via the os > (although reading your original email it sounds like you are already > attempting this). > > If you have a fancy cluster this may actually be more difficult than it > sounds and have interesting (unwanted) side effects, also the underlying > database (if you are storing emails that way) may have a method to remove > data > > I assume you are keeping back up copies of all those emails somewhere, > just in case you need them in the future. > > See this wiki article to better understand what I mean by the ‘fancy > pants’ clusters : > https://en.m.wikipedia.org/wiki/High-availability_cluster > They sound very cool, but I suspect are overkill for a mail server, unless > your database is already inside one then it would make sense I guess. > > Hello, I just use the cluster/replication functionality integrated into dovecot, nothing more. There is no database involved. I use LDAP for the authentication. The mails are stored locally on each server and replicated with the replication feature of dovecot. I followed this wiki article: https://wiki.dovecot.org/Replication Thanks! -- Francis

2 8

imap segfault in libc.so with CLucene FTS backend enabled
by Alexander Miroshnichenko 08 Mar '19

08 Mar '19

Steps to reproduce: - Enable CLucene FTS in Dovecot; - Open mailbox with MUA; - Search for message with any text; - IMAP session crash. OS: Gentoo Base System release 2.6 Version: FTS: dev-cpp/clucene-2.3.3.4-r6 IMAP: net-mail/dovecot-2.3.2.1 LIBC: sys-libs/musl-1.1.21 Dovecot FTS config: plugin { fts = lucene fts_lucene = whitespace_chars=@. normalize no_snowball fts_autoindex=yes fts_autoindex_max_recent_msgs=80 fts_index_timeout=90 } dmesg: [260150.192294] imap[18221]: segfault at 6578772cca98 ip 000063e7f1b10397 sp 00007945d5822970 error 6 in libc.so[63e7f1ae8000+a4000] [260150.192316] Code: 0f 84 44 02 00 00 48 39 ca 0f 84 62 02 00 00 48 8b 43 08 48 89 4a 10 48 89 51 18 48 89 c2 48 83 e0 fe 48 83 ca 01 48 89 53 08 <48> 83 0c 03 01 41 8b 07 48 8d 6b 10 85 c0 0f 84 68 ff ff ff 31 c0 bt full: Core was generated by `dovecot/imap'. Program terminated with signal SIGSEGV, Segmentation fault. #0 unbin (i=0, c=0x1908553de10) at src/malloc/malloc.c:195 195 src/malloc/malloc.c: No such file or directory. (gdb) bt full #0 unbin (i=0, c=0x1908553de10) at src/malloc/malloc.c:195 No locals. #1 malloc (n=<optimized out>, n@entry=4) at src/malloc/malloc.c:320 mask = <optimized out> c = 0x1908553de10 i = 0 j = 0 #2 0x000063e7f1b4984f in wcsdup (s=0x63e7ed7d0c58 L"") at src/string/wcsdup.c:7 l = 0 d = <optimized out> #3 0x000063e7eda98308 in lucene::index::Term::Term (this=0x1908553df80) at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/index/Term.cpp:26 No locals. #4 0x000063e7edad5f25 in lucene::index::SegmentTermEnum::readTerm(lucene::index::Term*) () at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/index/SegmentTermEnum.cpp:351 start = 1 length = 4 totalLength = 5 field = <optimized out> fieldname = 0x1908553d180 L"\142\157\144\171" #5 0x000063e7edad5f7c in lucene::index::SegmentTermEnum::next (this=0x19085524460) at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/index/SegmentTermEnum.cpp:180 tmp = <optimized out> this = 0x19085524460 tmp = <optimized out> tmp = <optimized out> #6 0x000063e7edad5be9 in lucene::index::SegmentTermEnum::scanTo (this=this@entry=0x19085524460, term=term@entry=0x7945d5822dc0) at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/index/SegmentTermEnum.cpp:218 No locals. #7 0x000063e7edad959c in lucene::index::TermInfosReader::scanEnum (this=<optimized out>, term=term@entry=0x7945d5822dc0) at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/index/TermInfosReader.cpp:422 enumerator = 0x19085524460 #8 0x000063e7edad96a4 in lucene::index::TermInfosReader::get (this=<optimized out>, term=term@entry=0x7945d5822dc0) at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/index/TermInfosReader.cpp:246 enumerator = <optimized out> #9 0x000063e7edab9071 in lucene::index::SegmentReader::docFreq (this=0x19085500ae0, t=0x7945d5822dc0) at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/index/SegmentReader.cpp:518 ti = <optimized out> #10 0x000063e7edae2620 in lucene::search::Similarity::idf (this=0x19085526e60, term=0x7945d5822dc0, searcher=0x190855007a0) at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/search/Similarity.cpp:184 No locals. #11 0x000063e7edaeda51 in lucene::search::TermWeight::TermWeight(lucene::search::Searcher*, lucene::search::TermQuery*, lucene::index::Term*) () at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/search/TermQuery.cpp:117 No locals. #12 0x000063e7edaeda99 in lucene::search::TermQuery::_createWeight(lucene::search::Searcher*) () at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/search/TermQuery.cpp:240 No locals. #13 0x000063e7edafa2dc in lucene::search::BooleanWeight::BooleanWeight(lucene::search::Searcher*, lucene::util::CLVector<lucene::search::BooleanClause*, lucene::util::Deletor::Object<lucene::search::BooleanClause> >*, lucene::search::BooleanQuery*) () at /usr/lib/gcc/x86_64-gentoo-linux-musl/8.2.0/include/g++-v8/bits/stl_vector.h:930 i = 1 i = <optimized out> #14 0x000063e7edafa351 in lucene::search::BooleanQuery::_createWeight(lucene::search::Searcher*) () at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/search/BooleanQuery.cpp:66 No locals. #15 0x000063e7edaef926 in lucene::search::Query::weight (this=this@entry=0x7945d5822da0, searcher=searcher@entry=0x190855007a0) at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/search/SearchHeader.cpp:121 query = <optimized out> weight = <optimized out> sum = <optimized out> norm = <optimized out> #16 0x000063e7edaf0cd7 in lucene::search::IndexSearcher::_search(lucene::search::Query*, lucene::search::Filter*, int) () at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/search/IndexSearcher.cpp:222 weight = <optimized out> scorer = <optimized out> bits = <optimized out> hq = <optimized out> totalHits = <optimized out> hitCol = {<lucene::search::HitCollector> = {<lucene::debug::LuceneVoidBase> = {_vptr.LuceneVoidBase = 0x2}, <No data fields>}, minScore = -1.75304399e+30, bits = 0x30, hq = 0xffffffffffffffff, nDocs = 40, totalHits = 0x63e7eda6f2cc <lucene::util::Compare::WChar::operator()(wchar_t const*, wchar_t const*) const+20>} scoreDocsLength = <optimized out> scoreDocs = <optimized out> totalHitsInt = <optimized out> wq = <optimized out> #17 0x000063e7edaf4344 in lucene::search::Hits::getMoreDocs(unsigned long) () at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/search/Hits.cpp:120 _min = <optimized out> n = <optimized out> topDocs = 0x0 scoreDocs = <optimized out> scoreDocsLength = <optimized out> scoreNorm = <optimized out> ---Type <return> to continue, or q <return> to quit--- #18 0x000063e7edaf443e in lucene::search::Hits::Hits (this=0x1908553a1a0, s=0x190855007a0, q=<optimized out>, f=<optimized out>, _sort=<optimized out>) at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/search/Hits.cpp:60 No locals. #19 0x000063e7edaef7fc in lucene::search::Searcher::search(lucene::search::Query*, lucene::search::Filter*) () at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/search/SearchHeader.cpp:188 No locals. #20 0x000063e7edd7edf0 in lucene_index_search(lucene_index*, array__lucene_query&, fts_result*, array__seq_range*) () at lucene-wrapper.cc:1361 hits = <optimized out> last_uid = <optimized out> score = <optimized out> ret = 0 query = {<lucene::search::Query> = {<lucene::util::NamedObject> = {_vptr.NamedObject = 0x63e7edd6e970 <vtable for lucene::search::BooleanQuery+16>}, boost = 1}, clauses = 0x190855007e0, static maxClauseCount = 1024, static allowDocsOutOfOrder = false, disableCoord = false, minNrShouldMatch = 0} mailbox_term = {<lucene::debug::LuceneBase> = {_vptr.LuceneBase = 0x63e7edd68e80 <vtable for lucene::index::Term+16>, __cl_refcount = 2}, cachedHashCode = 0, _field = 0x190854bd7c0 L"\142\157\170", _text = 0x1908553a0a0 L"\142\146\064\141\067\066\061\060\146\062\070\143\063\142\065\143\066\145\060\062\060\060\060\060\065\143\146\143\061\141\061\064", textLenBuf = 32, textLen = 32, internF = true} mailbox_query = {<lucene::search::Query> = {<lucene::util::NamedObject> = {_vptr.NamedObject = 0x63e7edd6d918 <vtable for lucene::search::TermQuery+16>}, boost = 1}, term = 0x7945d5822dc0} #21 0x000063e7edd7ff54 in lucene_index_lookup (index=0x190854ee8e0, args=args@entry=0x1908553b468, flags=flags@entry=(unknown: 0), result=result@entry=0x7945d5823000) at lucene-wrapper.cc:1421 uids_arr = <optimized out> arg = 0x0 def_queries = {arr = {buffer = 0x190854b2438, element_size = 16}, v = 0x190854b2438, v_modifiable = 0x190854b2438} have_definites = true maybe_queries = {arr = {buffer = 0xc, element_size = 18446744073709551612}, v = 0xc, v_modifiable = 0xc} have_maybies = <optimized out> #22 0x000063e7edd7c0d4 in fts_backend_lucene_lookup () at fts-backend-lucene.c:489 _data_stack_cur_id = 5 backend = 0x190854ee780 ret = <optimized out> #23 0x000063e7f09a85dd in fts_backend_lookup (backend=0x190854ee780, box=0x190854fc148, args=args@entry=0x1908553b468, flags=flags@entry=(unknown: 0), result=result@entry=0x7945d5823000) at fts-api.c:353 No locals. #24 0x000063e7f09acd92 in fts_search_lookup_level_single (and_args=<optimized out>, args=0x1908553b468, fctx=0x190854f5520) at fts-search.c:50 flags = (unknown: 0) level = <optimized out> result = {box = 0x0, definite_uids = {arr = {buffer = 0x19085528378, element_size = 8}, v = 0x19085528378, v_modifiable = 0x19085528378}, maybe_uids = {arr = {buffer = 0x190855284b8, element_size = 8}, v = 0x190855284b8, v_modifiable = 0x190855284b8}, scores = {arr = {buffer = 0x190855285f8, element_size = 8}, v = 0x190855285f8, v_modifiable = 0x190855285f8}, scores_sorted = false} flags = <optimized out> level = <optimized out> result = <optimized out> #25 fts_search_lookup_level () at fts-search.c:210 _data_stack_cur_id = 4 ret = <optimized out> #26 0x000063e7f09ad32c in fts_search_lookup_level () at fts-search.c:220 ret = 0 #27 0x000063e7f09ad48e in fts_search_lookup () at fts-search.c:360 last_uid = 622 seq1 = 544 seq2 = 807 __func__ = "fts_search_lookup" #28 0x000063e7f09af460 in fts_mailbox_search_init () at fts-storage.c:250 ft = 0x19085511e60 fbox = <optimized out> flist = <optimized out> ctx = 0x190854f5240 fctx = 0x190854f5520 #29 0x000001905d983992 in imap_search_start () at imap-search.c:586 cmd = 0x190854e9628 __func__ = "imap_search_start" #30 0x000001905d9753e5 in cmd_search (cmd=<optimized out>) at cmd-search.c:48 ctx = 0x190854e9830 sargs = 0x1908553b308 args = 0x19085527620 charset = 0x190854f3860 "utf-8" ret = 1 #31 0x000001905d97cad4 in command_exec () at imap-commands.c:201 hook = 0x1905db9cda0 finished = <optimized out> __func__ = "command_exec" #32 0x000001905d97b262 in client_command_input () at imap-client.c:1152 client = 0x190854e89c8 command = <optimized out> __func__ = "client_command_input" #33 0x000001905d97b305 in client_command_input () at imap-client.c:1215 client = 0x190854e89c8 command = <optimized out> __func__ = "client_command_input" ---Type <return> to continue, or q <return> to quit--- #34 0x000001905d97b6cd in client_handle_next_command (remove_io_r=<synthetic pointer>, client=0x190854e89c8) at imap-client.c:1257 No locals. #35 client_handle_input () at imap-client.c:1271 _data_stack_cur_id = 3 ret = <optimized out> remove_io = false handled_commands = false ret = <optimized out> remove_io = <optimized out> __func__ = "client_handle_input" client = 0x190854e89c8 handled_commands = <optimized out> _data_stack_cur_id = <optimized out> ret = <optimized out> remove_io = <optimized out> __func__ = "client_handle_input" _data_stack_cur_id = <optimized out> #36 0x000001905d97bb9e in client_input () at imap-client.c:1317 cmd = 0x190854cfba0 output = 0x190854e9440 bytes = 80 __func__ = "client_input" #37 0x000063e7f14f8c58 in io_loop_call_io () at ioloop.c:674 ioloop = 0x63e7f1ae7f20 t_id = 2 __func__ = "io_loop_call_io" #38 0x000063e7f14fa116 in io_loop_handler_run_internal () at ioloop-epoll.c:222 ctx = 0x1905db9cfc0 events = <optimized out> event = 0x190854bc360 list = 0x190854bd1a0 io = <optimized out> tv = {tv_sec = 1799, tv_usec = 999332} events_count = <optimized out> msecs = <optimized out> ret = <optimized out> i = 0 j = <optimized out> call = <optimized out> __func__ = "io_loop_handler_run_internal" #39 0x000063e7f14f8cfa in io_loop_handler_run () at ioloop.c:726 __func__ = "io_loop_handler_run" #40 0x000063e7f14f8e68 in io_loop_run () at ioloop.c:699 __func__ = "io_loop_run" #41 0x000063e7f1480dbb in master_service_run (service=0x63e7f1ae7de0, callback=callback@entry=0x1905d987e60 <client_connected>) at master-service.c:767 No locals. #42 0x000001905d96dfc4 in main () at main.c:521 set_roots = {0x1905db9aa20 <smtp_submit_setting_parser_info>, 0x1905db9a740 <imap_setting_parser_info>, 0x0} login_set = {auth_socket_path = 0x190854b2060 "\003", postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = 0x1905d9886b0 <login_client_connected>, failure_callback = 0x1905d987f28 <login_client_failed>, request_auth_token = true} service_flags = <optimized out> storage_service_flags = MAIL_STORAGE_SERVICE_FLAG_NO_NAMESPACES username = 0x0 auth_socket_path = <optimized out> c = <optimized out> error = 0x4cd0 <error: Cannot access memory at address 0x4cd0> #43 0x000063e7f1b0506b in libc_start_main_stage2 (main=0x1905d96dc80 <main>, argc=1, argv=0x7945d5823688) at src/env/__libc_start_main.c:94 envp = 0x7945d5823698 #44 0x000001905d96e168 in _start_c () at imap-client.c:1433 No symbol table info available. #45 0x0000000000000000 in ?? () No symbol table info available. (gdb) -- Alexander Miroshnichenko

1 0

Re: rsync /old/server new/server ?
by Aki Tuomi 08 Mar '19

08 Mar '19

On 8.3.2019 14.07, Voytek Eymont wrote: > On Fri, March 8, 2019 10:45 pm, Aki Tuomi via dovecot wrote: >> On 8.3.2019 13.44, Voytek Eymont via dovecot wrote: >> >>> I have Centos 7 with dovecot/postfix/mysql Maildir >>> >>> >>> I want to bring in a new server, new server will have same hostname as >>> current, but, different IP >>> >>> I was intending to >>> rsync -avzhe ssh vmail@oldserver:/var/vmail/vmail1 /var/vmail/vmail1 >>> >>> and, then, re run as necessary when/if mail still arrives on old server >>> >>> >>> is that "a good plan" ...? >>> >>> TIA, V >>> >>> >> Yeah, it's ok as long as you haven't switched to new server. > Aki, thanks > > I'm not certain I understand your comment properly > > I currently have server 'geko' > > intention was to change A record to assign geko to new IP/server, assign > new hostname to oldserver A record > > I guess I;ll still get some emails delivered to oldserver with new > hostname/old ip for 24 hours or so after aA record change ? > > so, I was going to re run rsync 2 or 3 times over the first 24 hours or so ? > > are you saying NOT to rsync once A record changed ? > > sorry for being slow > > You could configure old server's MTA to deliver mail to new server's MTA instead? After there has been activity on the new server, running rsync from old server can cause problems. Aki

2 1

Re: rsync /old/server new/server ?
by Voytek Eymont 08 Mar '19

08 Mar '19

On Fri, March 8, 2019 10:45 pm, Aki Tuomi via dovecot wrote: > > On 8.3.2019 13.44, Voytek Eymont via dovecot wrote: > >> I have Centos 7 with dovecot/postfix/mysql Maildir >> >> >> I want to bring in a new server, new server will have same hostname as >> current, but, different IP >> >> I was intending to >> rsync -avzhe ssh vmail@oldserver:/var/vmail/vmail1 /var/vmail/vmail1 >> >> and, then, re run as necessary when/if mail still arrives on old server >> >> >> is that "a good plan" ...? >> >> TIA, V >> >> > Yeah, it's ok as long as you haven't switched to new server. Aki, thanks I'm not certain I understand your comment properly I currently have server 'geko' intention was to change A record to assign geko to new IP/server, assign new hostname to oldserver A record I guess I;ll still get some emails delivered to oldserver with new hostname/old ip for 24 hours or so after aA record change ? so, I was going to re run rsync 2 or 3 times over the first 24 hours or so ? are you saying NOT to rsync once A record changed ? sorry for being slow (sorry for sending not to list...)

1 0