From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6163487219372785664 X-Received: by 10.112.189.131 with SMTP id gi3mr31243745lbc.6.1435049522895; Tue, 23 Jun 2015 01:52:02 -0700 (PDT) X-BeenThere: supmua@googlegroups.com Received: by 10.180.89.3 with SMTP id bk3ls888448wib.26.canary; Tue, 23 Jun 2015 01:52:02 -0700 (PDT) X-Received: by 10.180.105.226 with SMTP id gp2mr541964wib.1.1435049522551; Tue, 23 Jun 2015 01:52:02 -0700 (PDT) Return-Path: Received: from mail-la0-f42.google.com (mail-la0-f42.google.com. [209.85.215.42]) by gmr-mx.google.com with ESMTPS id wf6si867895lbb.2.2015.06.23.01.52.01 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 Jun 2015 01:52:01 -0700 (PDT) Received-SPF: neutral (google.com: 209.85.215.42 is neither permitted nor denied by best guess record for domain of eg@gaute.vetsj.com) client-ip=209.85.215.42; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 209.85.215.42 is neither permitted nor denied by best guess record for domain of eg@gaute.vetsj.com) smtp.mail=eg@gaute.vetsj.com Received: by laka10 with SMTP id a10so2191363lak.0 for ; Tue, 23 Jun 2015 01:52:01 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:subject:to:references:in-reply-to :user-agent:message-id:mime-version:content-type :content-transfer-encoding; bh=F0V1rboapJcodKjV9YPc0V455QZ6pqVB8TOUj5Z9Mao=; b=HyVFpTTvo///4vbkNpOEumWbNuVf6cpx6DXf32tGQ52cyatIwDCm0kinpQayXLT9B9 7S6oNKS2/DVoIRJ6SmqoMAdDqdhiErRfd1QU3gmWRyahbPwPi0Taz4LCuGmJ035CUGW4 HnVETRCnBMcTUSE4mZoXq0ZsiGZobNhgKAFJcZiQ8yryIlROrhtYjWqkdIrteYU6xFeq +aKwNqUp7Fgl/7UqVM5zdWNvOrWpFcdj3hC5j9Sp6LMJAYwQVBJWf/dg9ZQOfifXkNmh ccBjiNQMZ0qDaSmluM68Z9UZPOcuzicMGgLOxPBrm+t81x96Glh0mhfUeeH48L+Fcq2j VHKw== X-Gm-Message-State: ALoCoQmyR7q/88we+kowPC5JRFoZ4BzIlNZS/gY5fjqA95o5A3XXyjM2w4MTaX56q5ofgOPuIzUU X-Received: by 10.152.20.228 with SMTP id q4mr34923380lae.12.1435049521703; Tue, 23 Jun 2015 01:52:01 -0700 (PDT) Return-Path: Received: from localhost ([128.39.46.106]) by mx.google.com with ESMTPSA id ja1sm5356178lbc.38.2015.06.23.01.52.00 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 Jun 2015 01:52:00 -0700 (PDT) Date: Tue, 23 Jun 2015 08:51:59 +0000 From: Gaute Hope Subject: Re: [sup] How to move mails to trash on the server after deleting them in sup? To: Siwen Yu , supmua@googlegroups.com References: <448b29ee-ba83-47a0-8540-7e058c5f64c8@googlegroups.com> In-Reply-To: <448b29ee-ba83-47a0-8540-7e058c5f64c8@googlegroups.com> User-Agent: astroid/vv0.3-22-ge8533103 (https://github.com/gauteh/astroid) Message-Id: <1435048998-astroid-5-ay83go9694-1761@strange> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Siwen Yu writes on June 23, 2015 10:38: > I've recently switched to SUP from MUTT.=20 >=20 > I've followed the 'Complete gmail configuration' wiki post and set my gma= il=20 > account with offlineimap & sup successfully. But when I delete some mails= =20 > in the INDEX view with 'd' key, they just disappeared but still on the=20 > server. After flushing changes and polling manually, they were still ther= e.=20 > How could I move them to the Trash on the server after deleting them in s= up? >=20 > ps. My sup & offlineimap setting is the same as the wiki post. Hi, sup does not do this for you. It can probably be best done with an addon-script that loops over deleted messages, or a script that looks for the trash (T) flag (if you have maildir-syncback enabled). Maybe what you want to achieve is actually to add the trash flag? In that case check out maildir-syncback in the wiki [0]. Some earlier discussion: https://github.com/sup-heliotrope/sup/issues/175 Regards, gaute [0] https://github.com/sup-heliotrope/sup/wiki/Using-sup-with-other-clients =