Active
Project:
Signup
Version:
5.x-2.7
Component:
Email
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
9 Sep 2009 at 04:19 UTC
Updated:
4 Feb 2013 at 13:16 UTC
When a user signs up, they are not receiving the confirmation emails. Is there any log that the module rights to, or is there a way I can set it up to do logging so I can figure out what's going wrong?
Comments
Comment #1
dwwYes. You can install the devel module and there's an option for it to write all emails to the watchdog log instead of trying to send them.
You should also make sure your site is configured to send *any* emails -- e.g. do password reset emails work?
Are you sure the node the user is signing up for is configured to send confirmation emails?
Did you change the site-wide defaults and assume that that's going to retroactively change the per-node settings on all your existing nodes?
I know the module itself works, so this isn't a bug, but a support request about some misconfiguration on your site. I'm assuming one of the above questions will lead you to fixing the problem yourself. If not, you can set this back to active with a lot more detail about how to reproduce your problem, how your site is configured, etc.
Comment #2
fireman137 commentedDo you know where it generates it's "from" address? I finally found someone at my ISP who could talk sensibly, and he saw the return address and said that's why it was getting marked as spam. The return path starts with "_www@".
Comment #3
fireman137 commentedThe devel module may be able to write the messages to a log and not send them, but I need to know what happens once a message is sent and if it's bounced back. I know for a fact a certain ISP is bouncing my Signup confirmation emails back, but without the headers of a bounced message they won't unblock my IP. I know with PHP you can specify a bounce address, I'm just looking for where I can insert that into the signup module's code.
Comment #4
duaelfrThis version of Signup is not supported anymore. The issue is closed for this reason.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.
This issue has been automagically closed by a script.
Comment #5
simon georges commentedReverting recent closing.