From: physiculus <physiculus@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: info-gnus-english@gnu.org
Subject: Re: Problem splitting (nnimap-inbox "[Gmail]/Alle Nachrichten")
Date: Sun, 17 Jan 2021 15:17:49 +0100 [thread overview]
Message-ID: <87y2grve9e.fsf@googlemail.com> (raw)
In-Reply-To: <87a6t8a9gr.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Sat, 16 Jan 2021 12:54:44 -0800")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
Hello,
yes thanks i know that.
But unfortunately after changing it, the problem remains.
For a further detailed look i will describe a bit more.
Usually i use folders on my gmail imap account to split incoming mails.
Currently most splitting works in that way, that the article is shown in
the new folder. Therefore i think, that initial splitting works.
BUT
After the split, a look inside gmail All Mails shows the original message
AND the same message exists in the new folder.
So i think, that gnus not move the message, gnus copy the message.
Therefore i had to press B DEL inside the all mails folder to delete
this message.
BUT after a new refresh pressing g the message is there again
(sometimes).
Finally i think, that something inside gnus splitting process is not
completely move the message.
Hope my problem is described a bit clearer now.
PS: I use emacs 28 on fedora 32.
Regards
Poul
> physiculus <physiculus@gmail.com> writes:
>
>> Hello,
>> i reconfigured my gmail account from splitting INBOX to All Mails.
>> The reason was duplicated mails in folder INBOX IMPORTANT STARRED.
>> I read about it and one solution should be the change from folder INBOX
>> to All Mails.
>> But after that change splitting is not working properly anymore.
>> Most mail are not splitted automatic. If i respool, it works ?? Strange.
>>
>> I dont know what to do. Perhaps someone has an idea.
>>
>> here is my config:
>> (setq gnus-secondary-select-methods '(
>> (nnimap "GMail"
>> (nnimap-address "imap.gmail.com")
>> (nnimap-server-port "imaps")
>> (nnimap-user "xxx@googlemail.com")
>> (nnimap-stream ssl)
>> (nnimap-inbox "[Gmail]/Alle Nachrichten")
>> (nnimap-expunge 'immediately)
>> ;;(nnimap-record-commands t)
>> (nnimap-split-methods default)
>
> If you've got split methods set to `default', won't it ignore your fancy
> splitting? I thought this was supposed to be set to `nnimap-split-fancy'.
>
>
> _______________________________________________
> info-gnus-english mailing list
> info-gnus-english@gnu.org
> https://lists.gnu.org/mailman/listinfo/info-gnus-english
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2021-01-17 14:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 18:51 physiculus
2021-01-16 20:54 ` Eric Abrahamsen
2021-01-17 14:17 ` physiculus [this message]
2021-01-18 4:53 ` Bob Newell
2021-01-18 13:42 ` Lars-Johan Liman
2021-01-18 18:17 ` Bob Newell
2021-01-19 9:24 ` Lars-Johan Liman
2021-01-19 18:46 ` Jeffrey DeLeo
2021-01-20 20:06 ` Bob Newell
2021-01-21 7:37 ` physiculus
2021-01-21 20:20 ` Bob Newell
2021-01-21 11:43 ` Lars-Johan Liman
2021-01-21 21:43 ` Jeffrey DeLeo
2021-01-22 2:43 ` Bob Newell
2021-01-19 9:43 ` physiculus
2021-01-19 10:52 ` Lars-Johan Liman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2grve9e.fsf@googlemail.com \
--to=physiculus@gmail.com \
--cc=eric@ericabrahamsen.net \
--cc=info-gnus-english@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).