On Sunday 08 July 2018 09.56:07 Gene Heskett wrote: > fetchmail feeds procmail, who proceeds to check incoming for viri and > spam, and sends several phony illegits to /dev/null, the spam gets > graded by spamassassin but still comes into kmail by being placed > in /var/mail/me. procmail can also generate other names depending on who > its from. Where mailwatcher comes into play is it launches an instance > of inotifywait to watch /var/mail, returning the name of the file that > the mail was written to when its closed. That triggers a dbus msg to > kmail to go get the mail, and it relaunches another instance of > inotifywait to replace the one that died returning the filename. Well, I'll sound as a noob, but what exactly does this (to me) very complicated way of doing bring? I mean, for 20 years almost I've been "simply" downloading my mail with kmail, using a few filters to post the messages to directories for clarity. I used to run spam filters, but since i got modern and also read my mail on a smartphone I had to hire an external service for that. Thierry -- Who is General Failure, and why is he reading my disk? --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-users-help@xxxxxxxxxxxxxxxxxxxxxxxxxx Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
