Bob Dodds wrote:
Bob Dodds wrote:
Keith Ivey wrote:
Bob Dodds wrote:
That doesn't help, so it must be the use of '=>' instead
of a comma in $transaction->header->add(). perldoc
Mail::Header says to use commas there.
The => is equivalent to a comma in that context. And it has nothing
to do with whatever you're doing with at signs, either. The error
message "can't call method add on undef" is saying that
$transaction->header is undefined and thus doesn't have an add()
method. Is the test message you're using invalid, or is there
something weird about it?
All mail was logging that "Fatal Error...can't call add on undef val".
It's not the @.
$result and $comment are defined. They log the usual "result was pass:
qp.mta.com: domain of [EMAIL PROTECTED] designates n.n.n.n as permitted
sender". Then in the next line, something is seen as undefined. It
wouldn't be saying there's no header defined? What could it be that
doesn't show
in the log line just before adding the spf header?
-Bob
$transaction->header->add('Received-SPF' , 'OK' ) ;
will produce the error. Does that mean that there's
no header hash to add to? What's the undef value?
-Bob
$transaction->header->print;
"can't call method print on an undefined value"
no header yet at data hook?
-Bob
