Thanks. We understood that the white space was at least the largest part of the issue, but since this setup was a replacement "mail router" for different mail system, which tolerated the white space, we were looking to make this change over as transparent to end users, even programmers, as painless as possible.
Since we inflicted this burden on the apps community we were attempting to be as fraternal as possible. Seems to require a certain masochism on our part. <g> As you say, tho, there are limits. joe a. >>> Wietse Venema <wie...@porcupine.org> 08/21/14 2:36 PM >>> Joe Acquisto-j4: > Well, I can tell you it is SuSe 10, postfix 2.5 (mumble). Beyond > that, I cannot divulge much more without running afoul of local > security concerns. > > The author of the reporting scripts is reluctant, but willing, to > correct the known issues, but I was hoping for some simple change > that would ignore any syntax problem in the from address of email, > from local/trusted sources, as this is likely to surface again as > time goes on. Postfix tolerates many mistakes, but it won't parse an address with unquoted whitespace. There is a limit to what I consider reasonable. People who run Postfix 2.8 or later can use smtpd_command_filter (http://www.postfix.org/postconf.5.html#smtpd_command_filter) to make minor corrections before Postfix parses command input. The documentation shows some examples. Something like: /^RCPT\s+TO:<([^"[:space:]]+ .+)@([^[:space:]]+>.*)/ RCPT TO:<"$1"@$2 would deal with unquoted spaces in an address. One can make it more precise if needed; that's left as an exercise for the reader. Wietse
