Alright, I am going to be gun-barrel straight about the specific facility inside Emacs as a mail client and that is called Mu4E1. There are others, and I do use them too, but that is not what I sho…

seen from United States
seen from France
seen from Malaysia
seen from China

seen from Türkiye
seen from United States

seen from Canada
seen from South Korea

seen from United States

seen from United States

seen from Singapore

seen from United States

seen from Malaysia
seen from United Arab Emirates

seen from Malaysia
seen from Romania

seen from Australia
seen from United States

seen from Philippines
seen from Taiwan
Alright, I am going to be gun-barrel straight about the specific facility inside Emacs as a mail client and that is called Mu4E1. There are others, and I do use them too, but that is not what I sho…

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
Email with notmuch and astroid
via https://asynchronous.in/2017/04/21/Email-with-notmuch-and-astroid/
Индикатор почты в Emacs mode line
Совсем недавно я перешел на mbsync + mu4e для почты и пока очень доволен. Есть очень подробный мануал и исчерпывающая документация описывающая их настройку и я не буду повторяться. Единственное чего не хватало - это значка показывающего наличие непрочитанных писем. Нету так напишем. Код пока сырой, многое стоит вынести в настройки и т.д. и т.п.
Вот как он включается:
(require 'inbox) (display-inbox-mode +1)
Для настройки используй M-x customize-group RET inbox
Ты захочешь задать команду для получения количества писем и, возможно, как часто проверять.
Я проверяю так:
#!/bin/bash - echo -n $( mu find date:1w..now maildir:/gmail/INBOX flag:unread 2>/dev/null | wc -l )
А вот и сам inbox.el
Telling auth-source (and smtpmail-send-it) about my changed email password
I recently had to change my email password, as properly dictated by work's IT policies. I use offlineimap to get my mail, mu4e to read it, and smtpmail-send-it to send it.
(setq message-send-mail-function 'message-send-mail-with-sendmail message-send-mail-function 'smtpmail-send-it smtpmail-stream-type 'starttls smtpmail-default-smtp-server "pod51019.outlook.com" smtpmail-smtp-server "pod51019.outlook.com" smtpmail-smtp-user "[email protected]" smtpmail-smtp-service 587)
Offlineimap manages its password stuff from a config file at ~/.offlineimaprc. I updated that file and I was able to continue retrieving my mail with no hiccoughs. I then updated my ~/.authinfo file as well with the new password, but I continued to get the authentication failed error.
Sending failed: 535 5.7.3 Authentication unsuccessful in response to base64-encoded-password
That was pretty odd, considering that I changed the source file and all. I tried digging through smtpmail.el a little bit, looking for occurences of password or auth or something. I happened to see a defun called auth-source-search which got me into auth-source.el. Doing an apropos-command for "auth" led me to auth-source-forget-all-cached.
Apparently the auth sources like ~/.authinfo are cached for a customizable length of time, so I just had to clear the cache and everything is back in running order!
Telling auth-source (and smtpmail-send-it) about my changed email password
I recently had to change my email password, as properly dictated by work's IT policies. I use offlineimap to get my mail, mu4e to read it, and smtpmail-send-it to send it.
(setq message-send-mail-function 'message-send-mail-with-sendmail message-send-mail-function 'smtpmail-send-it smtpmail-stream-type 'starttls smtpmail-default-smtp-server "pod51019.outlook.com" smtpmail-smtp-server "pod51019.outlook.com" smtpmail-smtp-user "[email protected]" smtpmail-smtp-service 587)
Offlineimap manages its password stuff from a config file at ~/.offlineimaprc. I updated that file and I was able to continue retrieving my mail with no hiccoughs. I then updated my ~/.authinfo file as well with the new password, but I was continued to get the authentication failed error.
Sending failed: 535 5.7.3 Authentication unsuccessful in response to base64-encoded-password
That was pretty odd, considering that I changed the source file and all. I tried digging through smtpmail.el a little bit, looking for occurences of password or auth or something. I happened to see a defun called auth-source-search which got me into auth-source.el. Doing an apropos-command for "auth" led me to auth-source-forget-all-cached.
Apparently the auth sources like ~/.authinfo are cached for a customizable length of time, so I just had to clear the cache and everything is back in running order!

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming