next »

[rob]

I have been using Calendarscript with Emailnotify for some time without issues but one of the recipients mail servers has just been updated.  They no longer accept "0" in the "to" field in the header.  Emailnotify (at least as I have it configured" does just that.  I've looked until my eyes are sore to try to figure out how to change that but without success.  I'd appreciate any help anyone is able to give.

Rob

------------------

[DanO]

*  "0" in the "to" field in the headed *

I can't see why that would be there, it has to be the email address of the intended recipient. Were the mails being sent? What where the received email headers like?

If I get a chance over the weekend, maybe I'll try and look into it.

Dan O.

------------------

[Tanus]

Was this problem solved by anyone?
I do experience the same...     

The "To:"- field in the recieved email looks like this 0@domain.com, instead of meaningful@domain.com.  The email does however arrive my account and when I look at the (low-level) header details I am not able to get any clues for this to happen, except that I see the mentiond "To:"-field...  

I have looked a bit more into it and it seems that the 0@domain.com is entirely wrong, even the part after @ is wrong, in my case it should be anotherdomain.com...  but it seems still to be sent to the meaningful@domain.com address.

[Tanus]

Finally I have localized the problem, although I am really not sure what happens (due to a limited knowledge to all constructs in perl).

However, I localized the problem to be in the subroutine "send" in the email.pm file.
By replacing the line

Code:

my $header = "To: " . join ';', @{$self->{to}} . "\n";

with

Code:

my $header = "To: " . $self->{to} . "\n";

the problem is solved (at least in my case).

Yes, I know that my replacement does not take into account that $self-{to} might be an array as some comments in the code suggest. However as the emailNotify2 is build, the plugin does not use that option anyway...

[DanO]

Thanks for the suggestion. Maybe someone else that has experienced the stated problem will try it out and let us know how your solution worked for them?

Dan O.