Strange subscribe behavior
I use a form to allow folks to sign up for my mailing lists. One user is having trouble using the form and I think it might be a problem with smartlist. Whenever he sends a subscribe request, the following error is generated: X-Diagnostic: Mail coming from a daemon, ignored The domain of the address generating this problem is "@ib.sc.vu.lt" Could it be that smartlist doesn't know how to handle such a domain? Thanks, irwin
On Fri, Apr 26, 2002 at 11:36:14AM -0400, MPLS Resource Center wrote:
I use a form to allow folks to sign up for my mailing lists. One user is having trouble using the form and I think it might be a problem with smartlist. Whenever he sends a subscribe request, the following error is generated:
X-Diagnostic: Mail coming from a daemon, ignored
The domain of the address generating this problem is "@ib.sc.vu.lt"
You need to check the full header of the mail sent by the form. Additionally enable VERBOSE=on from your list. The strings and REGEX's matching the MAILER_DAEMON definition are then visible in the log. Werner
Irwin asked, | One user is | having trouble using the form and I think it might be a problem with | smartlist. Whenever he sends a subscribe request, the following error is | generated: | X-Diagnostic: Mail coming from a daemon, ignored | The domain of the address generating this problem is "@ib.sc.vu.lt" | Could it be that smartlist doesn't know how to handle such a domain? The problem is not likely to be with his domain, but rather with either the local part of his address. Some people insist on using "root" or "admin" or something resembling that as their addresses. I had a user who subscribed from his work address, and his logon was based on his job title ("mkt_admin") rather than his own name. So for everything that looked for ^FROM_DAEMON I had to write in an exception for him.
| X-Diagnostic: Mail coming from a daemon, ignored
| The domain of the address generating this problem is "@ib.sc.vu.lt" | Could it be that smartlist doesn't know how to handle such a domain?
The problem is not likely to be with his domain, but rather with either the local part of his address. Some people insist on using "root" or "admin" or something resembling that as their addresses. I had a user who subscribed from his work address, and his logon was based on his job title ("mkt_admin") rather than his own name. So for everything that looked for ^FROM_DAEMON I had to write in an exception for him.
I think you are right, it seems to be happening with users have the list name in the local part of their address, is there a work around that doesn't involve manually coding exceptions for each user. :-) Irwin
participants (4)
-
David W. Tamkin -
Irwin Lazar -
MPLS Resource Center -
Werner Reisberger