BUG? Problem with subscribing to a list via web.
![](https://secure.gravatar.com/avatar/e7fff69de8c25f6450e72c5685c6fd8a.jpg?s=120&d=mm&r=g)
I've installed 2.0 beta 6 and I am using the web interface to subscribe to a list. I've noticed the following problem:
The server is ale.ftc.agilent.com and the list is "test"...
If I subscribe to the list and enter "user@ftc.agilent.com" the message sent to confirm the subscription has the headers: From: test-request@ftc.agilent.com To: user@ftc.agilent.com Reply-To: test-request@ftc.agilent.com
The problem here is that ftc.agilent.com does not understand "test-request" and won't route the message to ale.ftc.agilent.com.
If I subscribe with the address "user@ale.ftc.agilent.com" the Confirmation message shows:
From: test-request@ale.ftc.agilent.com To: user@ale.ftc.agilent.com Reply-To: test-request@ale.ftc.agilent.com
If I subscribe with the address "first_last@agilent.com" the Confirmation message shows:
From: test-request@ale.ftc.agilent.com To: first_last@agilent.com Reply-To: test-request@ale.ftc.agilent.com
In the above cases, the reply-to gets routed properly (because it has the full hostname.)
So, is the first case by design? or is there a bug here?
-- Ray Frush "Either you are part of the solution, T:970.288.6223 or part of the precipitate." -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- Agilent Technologies IT | Consumer and Site Services | Fort Collins Site
participants (1)
-
Ray Frush