489 reputation
414
bio website porkmail.org/era/unix/…
location
age
visits member for 3 years, 3 months
seen 14 hours ago

There is probably an anecdote from the Bell Labs from the early 1970s which either solves your problem or improves your understanding of it.

http://www.unix.org/license-plate.html


Apr
25
comment How to use procmail to get a message into a variable
Sorry for the multiple edits; I had a couple of false starts.
Apr
25
revised How to use procmail to get a message into a variable
Actually, just plain `MESSAGE=|` does not work
Apr
25
revised How to use procmail to get a message into a variable
Restore curl part of the original answer in somewhat improved form, too
Apr
25
answered How to use procmail to get a message into a variable
Apr
20
awarded  Scholar
Apr
20
accepted Understanding ulimit -u
Apr
20
comment Understanding ulimit -u
I guess @MichaelHampton was on to the same idea, and I was too dense to get it ...
Apr
20
comment Understanding ulimit -u
@CharlesDuffy: Ah, that sorts it out. If you want to post your remark as a separate answer, I'll be happy to accept it.
Apr
18
comment postfix adding garbage characters in the mail
Is this reproducible? If you resend an identical message, does it undergo identical corruption?
Apr
18
revised postfix adding garbage characters in the mail
Formatting fix for examples
Apr
18
comment postfix adding garbage characters in the mail
Decoding the payloads reveals that it's not "random garbage"; it has repeated a part of the text for some reason. The first difference is that dding: 0.6em;vertical-align: middle;border-color: #d4 is repeated at approximately byte offset 300.
Apr
18
suggested approved edit on postfix adding garbage characters in the mail
Apr
2
revised procmail recipe to forward email is rejected by recipient
Don't muck with DEFAULT; simplify regex before \/
Apr
2
comment procmail recipe to forward email is rejected by recipient
If SENDER is an acceptable envelope sender, just replace ${env+-f "$env"} with -f "$SENDER" and you're done (modulo the syntax error changes which will have to be undone, of course).
Apr
2
answered procmail recipe to forward email is rejected by recipient
Apr
2
comment procmail recipe to forward email is rejected by recipient
You cannot have two actions, so the double exclamation marks in your edited recipe are a syntax error. If there isn't a Return-Path: header in the incoming message, then of course, you cannot extract it, so the error is never reached anyway.
Apr
2
comment procmail recipe to forward email is rejected by recipient
Using a global lock file with LOCKFILE=.procmaillock serves no useful purpose here, as far as I can discern. Running multiple Procmail instances should be safe unless (for example) you have replaced your real Sendmail with a hack of your own which tries to save something to a database with exclusive write access or something like that.
Mar
30
comment prevent procmail from adding Return-path
Check that the whitespace in [ ] and [^ ] is a space and a tab. Copy/pasting from a web page might not work correctly, as indicated already in the original answer.
Mar
30
comment prevent procmail from adding Return-path
No match could mean either that there is no Return-Path: header, or that you mistyped the regex somehow.
Mar
25
comment Understanding ulimit -u
These commands were executed as a regular user.