Calendar Manager Multiple "Email Addresses to Notify When There is a New Event"?

[websissy]

Hello...

I'm running vb3.0.8 on two sites and having the same problem with both licensed copies. In setting up our 45 community events calendars, I defined no moderators for any of those calendars. But I did specify two email addresses that should be notified when a new event is posted.

The Calendar Manager setup screen specifically states that when entering multiple recipients to be notified:

(Separate each address with a SPACE)

But when I do that, and post a new event afterwards, I immediately get a bounced email that strongly suggests the two email addresses are getting run together when the Calendar update program tries to send to them. Here's a live example of the error message I receive (with domain names masked out):

The original message was received at Tue, 14 Feb 2006 15:11:09 -0600
from nobody@localhost

   ----- The following addresses had permanent fatal errors -----
[email protected] [email protected]
    (reason: 550 Host unknown)

   ----- Transcript of session follows -----
550 5.1.2 [email protected] [email protected]... 
Host unknown (Name server: [COLOR="Red"]domain1.com.harry[/COLOR]: host not found)

Notice particularly the part highlighted in red. It certainly looks to me like the Calendar Manager in passing these two email addys to sendmail, is running them together and as a result, sendmail is treating them as one address.

I also tried putting a semi-colon (";") between the names and essentially the same thing happened.

Is this a known bug? Or am I just doing something wrong here?

If it IS a bug, is there a patch somewhere to correct this problem?

Thanks!

[Marco van Herwaarden]

I don't know if you have edited your message, but once you have domain1, and once domaine1.

Anyhow it seems that your server can not resolve the domain names of the receipants, so he don't know where to sent to.

You could try to troubleshoot this by first testing with the first mail address, then the second. If they both work correct, try combining them again.

[websissy]

I don't know if you have edited your message, but once you have domain1, and once domaine1.

(with domain names masked out)

Yes. I did edit the message to remove the domain names. The typo was mine. Sorry. I've edited the original post and fixed the error now. Also, please note that in the error message there is a period between domain1.com and harry (domain1.com.harry). That is NOT a typo. That's exactly the way the error message appears.

Furthermore, when I tried putting a semicolon between the names as an experiment to see what happened, I got this:

   ----- Transcript of session follows -----
550 5.1.2 [email protected]; [email protected]... 
Host unknown (Name server: domain1.com;harry: host not found)

The fact that the spurious "period" that was there in the first case clearly disappears in this situation (to be replaced by the semi-colon) is what lead me to conclude that perhaps there IS a bug in the code that processes those two separate email addresses which causes the addresses to become "joined at the hip" with something the browser at least interprets as a "period" when more than one name is entered in the field.

In answer to your other question, there's no problem with either of the email addresses. I use them throughout the server in the same manner. I have no specified moderators anywhere. But both I and the site owner are listed as administrators to be notified when things change in several of our forums and I don't see the problem there at all. Only in the calendar manager do I have this issue.

That's why I asked if there was a known bug in this area. I wonder if anyone else running 3.0.8 can replicate this problem? As I've said, I confirmed that the same problem occurs here on both my licensed copies of vBulletin 3.0.8.

Thanks.

[websissy]

Since you made the suggestion, I did test this further. It works fine with either email address alone. But as soon as I put two email addresses into the list, the message never gets through. I get the error message instead.

I'm now convinced it's a documentable bug. But it's sure be nice if someone else running 3.0.8 could try to replicate the problem.

And now for the obvious question... Where does one report bugs around here and are they providing ANY bug-fix support for 3.0.8 now anyway?

Thanks.

[Steve Machol]

You cannot report bugs for older versions. You need to upgrade to at least 3.0.12, then if you have the same issue with that version and you have not applied any hacks, you can report this in the 3.0 Bug Tracker.