Re: OT lightweight IMAP client
On Fri, Sep 08, 2017 at 06:29:40PM -0600, @lbutlr wrote: > Figured someone on the list would have an opinion on a very > lightweight feature-poor IMAP client. It doesn't need to do > much else but access a single IMAP account and be able to > forward emails as attachments. Search would be good, but not > required. Searching for queueIDs in the Received header > would be fantastic. > > Primary considerations are fast and as light on memory use > as possible and usable from a Mac (command-line is fine). I > know mutt can do IMAP but I don't think it can forward > messages as attachments though I am probably wrong. Correct, you are incorrect. :) Forwarding as MIME attachment is default behavior when forwarding mail in mutt. I don't know about searching Received: headers, but I suspect in mutt, most things are possible. They do have a user community providing help. > Windows 10 might be useful, but not required. putty + mutt -- http://rob0.nodns4.us/ Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
Throttling bursts of connections at postscreen? More to do here?
Every few hours I get bursts of these from random addresses -- always at "poneytelecom.eu" (online.net) Communicating with abuse@ online.net/poneytelecom.eu is a lost cause. They're completely useless. Is postscreen doing its "best" job here at reducing load? It's clearly not passing the attempts through. I'm just wondering if there's any throttling or something else to here? Sep 6 03:22:20 cont03 postfix/postscreen[35432]: CONNECT from [62.210.140.7]:53039 to [192.0.2.1]:25 Sep 6 03:22:20 cont03 postfix/dnsblog[35436]: addr 62.210.140.7 listed by domain zen.spamhaus.org as 127.0.0.4 Sep 6 03:22:20 cont03 postfix/postscreen[35432]: PREGREET 14 after 0.14 from [62.210.140.7]:53039: EHLO mdb3Fue\r\n Sep 6 03:22:20 cont03 postfix/postscreen[35432]: DISCONNECT [62.210.140.7]:53039 Sep 6 03:22:21 cont03 postfix/postscreen[35432]: CONNECT from [62.210.140.7]:65108 to [192.0.2.1]:25 Sep 6 03:22:21 cont03 postfix/dnsblog[35434]: addr 62.210.140.7 listed by domain zen.spamhaus.org as 127.0.0.4 Sep 6 03:22:21 cont03 postfix/postscreen[35432]: PREGREET 14 after 0.15 from [62.210.140.7]:65108: EHLO lO0RVZU\r\n Sep 6 03:22:21 cont03 postfix/postscreen[35432]: DISCONNECT [62.210.140.7]:65108 Sep 6 03:22:21 cont03 postfix/postscreen[35432]: CONNECT from [62.210.140.7]:61166 to [192.0.2.1]:25 Sep 6 03:22:21 cont03 postfix/dnsblog[35437]: addr 62.210.140.7 listed by domain zen.spamhaus.org as 127.0.0.4 Sep 6 03:22:21 cont03 postfix/postscreen[35432]: PREGREET 15 after 0.16 from [62.210.140.7]:61166: EHLO w2z7WmCG\r\n Sep 6 03:22:21 cont03 postfix/postscreen[35432]: DISCONNECT [62.210.140.7]:61166 Sep 6 03:22:22 cont03 postfix/postscreen[35432]: CONNECT from [62.210.140.7]:62585 to [192.0.2.1]:25 Sep 6 03:22:22 cont03 postfix/dnsblog[35437]: addr 62.210.140.7 listed by domain zen.spamhaus.org as 127.0.0.4 Sep 6 03:22:22 cont03 postfix/postscreen[35432]: PREGREET 16 after 0.15 from [62.210.140.7]:62585: EHLO dtcgZI6oA\r\n Sep 6 03:22:22 cont03 postfix/postscreen[35432]: DISCONNECT [62.210.140.7]:62585 Sep 6 03:22:22 cont03 postfix/postscreen[35432]: CONNECT from [62.210.140.7]:58322 to [192.0.2.1]:25 ... MANY HUNDREDS MORE ... Sep 6 03:24:02 cont03 postfix/postscreen[35432]: PREGREET 17 after 0.16 from [62.210.140.7]:65061: EHLO O0uHWZVJd5\r\n Sep 6 03:24:02 cont03 postfix/postscreen[35432]: DISCONNECT [62.210.140.7]:65061 Sep 6 03:24:02 cont03 postfix/postscreen[35432]: CONNECT from [62.210.140.7]:64305 to [192.0.2.1]:25 Sep 6 03:24:02 cont03 postfix/dnsblog[35433]: addr 62.210.140.7 listed by domain zen.spamhaus.org as 127.0.0.4 Sep 6 03:24:02 cont03 postfix/postscreen[35432]: PREGREET 16 after 0.14 from [62.210.140.7]:64305: EHLO FG3aXs6pz\r\n Sep 6 03:24:02 cont03 postfix/postscreen[35432]: DISCONNECT [62.210.140.7]:64305 Sep 6 03:24:02 cont03 postfix/postscreen[35432]: CONNECT from [62.210.140.7]:64252 to [192.0.2.1]:25 Sep 6 03:24:02 cont03 postfix/dnsblog[35438]: addr 62.210.140.7 listed by domain zen.spamhaus.org as 127.0.0.4 Sep 6 03:24:03 cont03 postfix/postscreen[35432]: PREGREET 15 after 0.15 from [62.210.140.7]:64252: EHLO cGD5sIof\r\n Sep 6 03:24:03 cont03 postfix/postscreen[35432]: DISCONNECT [62.210.140.7]:64252 Sep 6 03:24:03 cont03 postfix/postscreen[35432]: CONNECT from [62.210.140.7]:59911 to [192.0.2.1]:25 Sep 6 03:24:03 cont03 postfix/dnsblog[35436]: addr 62.210.140.7 listed by domain zen.spamhaus.org as 127.0.0.4 Sep 6 03:24:03 cont03 postfix/postscreen[35432]: PREGREET 16 after 0.15 from [62.210.140.7]:59911: EHLO 9D4ZAcsJk\r\n Sep 6 03:24:03 cont03 postfix/postscreen[35432]: DISCONNECT [62.210.140.7]:59911 Sep 6 03:24:03 cont03 postfix/postscreen[35432]: CONNECT from [62.210.140.7]:61102 to [192.0.2.1]:25
Re: Throttling bursts of connections at postscreen? More to do here?
yodel...@yepmail.net: > Every few hours I get bursts of these from random addresses -- always at > "poneytelecom.eu" (online.net) > > Communicating with abuse@ online.net/poneytelecom.eu is a lost cause. > They're completely useless. > > Is postscreen doing its "best" job here at reducing load? It's clearly not > passing the attempts through. So, postscreen is doing its job. > I'm just wondering if there's any throttling or something else to here? Why bother? It's doing exactly what it was meant to do; one postscreen process keeps the zombies away from Postfix SMTP server processes. Wietse
Re: OT lightweight IMAP client
On Sat, Sep 09, 2017 at 11:28:02AM -0500, /dev/rob0 wrote: > > Primary considerations are fast and as light on memory use > > as possible and usable from a Mac (command-line is fine). I > > know mutt can do IMAP but I don't think it can forward > > messages as attachments though I am probably wrong. > > Correct, you are incorrect. :) Forwarding as MIME attachment is > default behavior when forwarding mail in mutt. For mutt: add "set mime_forward=yes" to .muttrc For Apple's Mail.app: "Forward as Attachment" from the "Message" menu. -- Viktor.
Re: OT lightweight IMAP client
On 09 Sep 2017, at 10:28, /dev/rob0 wrote: > On Fri, Sep 08, 2017 at 06:29:40PM -0600, @lbutlr wrote: >> Figured someone on the list would have an opinion on a very >> lightweight feature-poor IMAP client. It doesn't need to do >> much else but access a single IMAP account and be able to >> forward emails as attachments. Search would be good, but not >> required. Searching for queueIDs in the Received header >> would be fantastic. >> >> Primary considerations are fast and as light on memory use >> as possible and usable from a Mac (command-line is fine). I >> know mutt can do IMAP but I don't think it can forward >> messages as attachments though I am probably wrong. > > Correct, you are incorrect. :) Forwarding as MIME attachment is > default behavior when forwarding mail in mutt. I'll double check this, but as I recall when i tried to do this in mutt last it would only forward the body of the email and if I wanted to include all of the attachments (including HTML parts) I had to select them, and then the message received was a series of MIME encapsulations and not the original message in its entirety. OTOH, it was a while ago. Possibly a decade. -- Apple broke AppleScripting signatures in Mail.app, so no random signatures.
Re: OT lightweight IMAP client
> On Sep 9, 2017, at 9:12 PM, @lbutlr wrote: > > I'll double check this, but as I recall when i tried to do this in mutt last > it would only forward the body of the email and if I wanted to include all of > the attachments (including HTML parts) I had to select them, and then the > message received was a series of MIME encapsulations and not the original > message in its entirety. > > OTOH, it was a while ago. Possibly a decade. "mime_forward = yes" is not a new Mutt feature, it has been around for at least a decade, however, it is likely still not the default, you have to turn it on. -- Viktor.
