447 reputation
314
bio website partmaps.org/era/unix/…
location
age
visits member for 3 years, 2 months
seen Dec 10 at 7:56

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


Dec
11
comment What is the difference between content-language and accept-language headers in Outlook? How/when are these added?
To the best of my knowledge, these are not properly standardized for email, and only used (or more like abused) by Microsoft. To add insult to injury, it appears that Exchange sets Accept-Language: based on the server's settings, and does not offer a per-user override.
Dec
3
comment Fixing intermittent file locking issue in Procmail
And you know about the limited support for large files? How large is the file you are writing to, and how large are the other large files which do not exhibit this problem?
Dec
2
comment Fixing intermittent file locking issue in Procmail
Is the file you are locking mounted locally? Procmail is basically NFS-compatible but there are some network outages you simply cannot completely guard against. If you are on NFS, which version?
Sep
10
comment Decrypt incoming pgp mail with procmail
let us continue this discussion in chat
Sep
10
comment Decrypt incoming pgp mail with procmail
See above. But also fix the decrypt.pl script to pass through message headers and MIME headers.
Sep
10
comment Decrypt incoming pgp mail with procmail
However, you should probably use a filtering recipe instead, i.e. :0fw -- a delivering recipe which fails to actually deliver the message anywhere will cause that message to be lost.
Sep
10
comment Decrypt incoming pgp mail with procmail
If your recipe lacks a pipe character, Procmail will use the file as an mbox folder, and append to the end of it. Make sure you use the correct syntax.
Sep
10
comment Decrypt incoming pgp mail with procmail
Iterate over the array and print each item, or simply print(join("",@{$arrayref})).
Sep
9
comment Procmail (permission related) - delivery fails: “process exited returning 77”
Sounds like you are attempting to treat //var/mail/root (sic) as an mbox file when in fact it is a directory?
Jul
25
comment forward all mail on a specified domain to script
+1 Procmail is enabled by default in most MTAs these days, you just have to make sure Procmail is installed and create a $HOME/.procmailrc. At least Exim and Postfix usually have this configured already. Procmail offers some clear benefits over directly forwarding to a script of your own, especially when it comes to robust error handling. If your script fails for whatever reason, the email is not entirely lost (and it's easy to put in security mechanisms like a safety copy of each incoming message to a directory in /tmp until you have a good, working, properly tested configuration).
May
14
comment Procmail to delete mail from senders
The trailing .* is superfluous, albeit mostly harmless. Do you really intend to allow exactly one arbitrary character between From: and root@?
Apr
25
comment Configuring Postfix, Spamassassin and Procmail to put spam in a dedicated folder
Wild guess, wrong permissions for the rc file?
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
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
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
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
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.