Reputation
578
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
6 16
Impact
~29k people reached

Feb
2
comment SSH remote execute command with special chars
If you don't need double quotes, using single quotes around the command will simplify things a great deal. Though you'll still need to escape some things from the remote shell.
Feb
2
answered how to run multiple commands (nested control statements) on remote machines with sudo?
Feb
2
comment Sending mail from a user supplied email address
Repeat: There are too many unspecified circumstances. Show us the mail you are sending "before" and "after" and we can judge whether it looks sane.
Feb
2
comment Sending mail from a user supplied email address
I mean forgery in the technical sense that you are putting in a From: address which is not yours.
Feb
2
comment Transport rule disclaimer in new emails before sending
Disclaimers on emails are extremely silly in the vast majority of cases.
Feb
2
comment Sending mail from a user supplied email address
There are too many unspecified circumstances. On the face of it, if the user supplied their own address and authorized you to send email on their behalf, everything should be fine. However, if they mistyped it, and/or if their domain admin has set a draconian SPF policy, and/or if the recipient is paranoid about forgeries, and/or your forgery is very clumsy, it might not work as you hope.
Jan
28
comment Where does an unconfigured procmail put incoming mails?
They probably went somewhere - Postfix would be configured to catch any error from Procmail, and Procmail should certainly raise one if it didn't know where to write a message. But I'm not able to guess where that might be.
Jan
1
comment Where does an unconfigured procmail put incoming mails?
There is no well-defined standard answer to this; it depends entirely on your virtual user architecture, and in particular, how Postfix invokes Procmail in this situation (if at all). We can speculate that it runs as user postfix (or mail, sendmail, what have you); does this user have a mailbox?
Dec
28
answered Where does an unconfigured procmail put incoming mails?
Nov
30
comment Email, forwarded by procmail, rejected by Gmail
And it goes without saying, really; there is no reason Gmail could not start blocking any particular sender at any point in time, regardless of their local configuration or the content of their email. Their network, their policy, their rules.
Nov
10
awarded  Notable Question
Oct
30
comment find command + enable Exit status to be diff then 0 when not match
The trailing * on the egrep regex is completely redundant. Since you are not using egrep regular expression syntax, plain old grep might be a few microseconds faster.
Oct
19
comment How to reconnect to a disconnected ssh session
@kbyrd Ideally, the OP could switch to this answer instead. Less ideally, it doesn't really matter; the accept mark is just one of several signals to future visitors. But this answer should get a lot more upvotes to properly signal it as "really the correct answer". In the meantime, of course, you are free to edit your own answer, either to point to this one, or to include this information in yours.
Sep
20
comment rt-mailgate not making tickets with fetchmail and procmail
As always, a trailing .* on a regular expression is useless.
Sep
20
comment rt-mailgate not making tickets with fetchmail and procmail
--no-verify-ssl is not doing anything when you are not connecting to a https URL.
Sep
20
comment rt-mailgate not making tickets with fetchmail and procmail
The /usr/bin/perl is harmless (provided this is a valid path) but the fact that no log file is being created indicates that Fetchmail is not running Procmail at all (or perhaps Fetchmail is not running!). How do you invoke it? Do you get a Fetchmail log?
Sep
7
comment Emails corrupt and a winmail.dat file attachment added for only one mail box
If the user's client is doing something to the messages after they arrive, the ones delivered to Procmail should still be fine. Adding a simple .procmailrc to save a copy of every incoming message to a temporary location (:0c (newline) /tmp/safety where obviously the destination has to exist and be writable) might help narrow the scope of the problem, at least.
Sep
5
awarded  Constituent
Aug
28
awarded  Caucus
Aug
27
comment Postfix, procmailrc, SpamAssassin letting some but not all spam messages through
Yes, you need to set LOGFILE to a file you have write access to, and capture the log from one of these events which you want to troubleshoot. You should probably also set VERBOSE=yes, perhaps only selectively (inside the condition you want to debug?), perhaps with output to a separate log file.