Re: Header parsing

> > * when the script is processing a file at the same time the > > mail-server is delivering to it (causing processing of an unfinished > > message at the end of the file) > > * rewinding/truncating the file at the end of processing at the same > > time the mail-server is delivering to it (not

Re: Header parsing

On Wed, Apr 19, 2017 at 05:05:31PM +0300, Rowan Thorpe wrote: > > On my server this is currently no problem, as I kill the process only at > > times > > when it is not yet starting the next fetch. Still it would be better of > > course. > > The race-conditions I mention are not about the script

Re: Header parsing

What about using Maildir on the email server? Then you don't have any issues with parsing and locking the spool file. -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Header parsing

Hi Rowan, If it makes you feel better, I get all your emails because I've created a Gmail filter that makes sure picolisp mail list mails always go through the filters. On Wed, Apr 19, 2017 at 11:57 AM, Rowan Thorpe wrote: > BTW: I receive DMARC reports about

Re: Header parsing

If people are currently working on improving the mailing list. I would be very pleased not receive automated emails about thanking people for joining or leaving. Has anybody else strong opinions about that? 2017-04-19 22:16 GMT+02:00 Henrik Sarvell : > Hi Rowan, > > If it

RE: Header parsing

> If people are currently working on improving the mailing list [...] I would like to stop receiving binary junk at the end of plain-text emails.

Unsubscribe

Re: Header parsing

On Wed, Apr 19, 2017 at 12:41:41PM +0300, Rowan Thorpe wrote: > PS: Even when using (peek) I think [A] the second patch (for not > chomping the final "^J") may still be applicable (at least for the > last email that appears in the spool file), and also *perhaps* [B] the > first line of the main

Re: your mail

Ooops! On Wed, Apr 19, 2017 at 08:12:11AM +0200, a...@software-lab.de wrote: > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe Rowan, are you sure? I tried your fix, but now it seems the mail body is lost? Any idea? ♪♫ Alex -- UNSUBSCRIBE:

Header parsing

Hi Rowan, > On Wed, Apr 19, 2017 at 08:12:11AM +0200, a...@software-lab.de wrote: > Rowan, are you sure? I tried your fix, but now it seems the mail > body is lost? Any idea? OK, so I tried a different approach. According to "a CRLF may be inserted before any WSP", I simply use (peek) to see if

[no subject]

-- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Header parsing

On 19 April 2017 at 10:45, Alexander Burger wrote: > Hi Rowan, > > > On Wed, Apr 19, 2017 at 08:12:11AM +0200, a...@software-lab.de wrote: > > Rowan, are you sure? I tried your fix, but now it seems the mail > > body is lost? Any idea? > > OK, so I tried a different

Re: Header parsing

BTW: I receive DMARC reports about bounced/quarantined mails spoofing my address, and just received one from fastmail which matches the quarantined deliveries vukini reported (they failed validation due to the accidentally forwarded SPF and DKIM headers, as I predicted). ..so it seems my posts to