I am still having mail issues on my dedicated server regarding mail being discarded because it is being sent as "nobody@host.domain.com". I have discussed this with my server support team and they claim it is being sent that way from the script, to which I agree. I just installed version 3.0.8 and am doing some tests to see if the script can get me around this dilema. Many ISP's including AOL, Yahoo, Hotmail, Earthlink, sbcglobal and many more are tossing our customer's receipts into the trash becasue of this. Any help is appreciated....Alex?
It looks like the default method (PHP) sends mail as nobody. The second option, SMTP does work, but you must enter the SMTP host as: username: password@mail.domain.com This way I get a return path that matches the domain and this should be accepted by most spam filters as legit mail. My question is this: Is there a risk of someone hacking the account username and password? I have tried to get Sendmail to work with the path /usr/sbin/sendmail, but it does nothing.
Looks like I'm talking ot my self here... I did an identical install on a different domain (a dot info domain) but on the same dedicated server. The .com domain install allows SMTP mail sending, but the .info only allows tests to email addresses on the same server. Anything else fails. Any ideas on that one? Probably not...
Idea is that it is hosting configuration question, just contact your webhosting support or system administrator.
Alex: The script is sending mail as "nobody". I already contacted my server tech support. They say the script must send using SMTP to avoid sending as nobody. Can you improved the section of documenation regarding the three mail sending methods? The format for the SMTP is not in the manual. Finally, can the PHP mailer be modified to use SMTP? A bit of documentatin on that would also be nice.
aMember Pro v.3 allows you to change e-mail method and use SMTP server. You can use SMTP server that requires authentication - use the following format for SMTP server name at aMember CP->Setup->E-Mail usernameassword@smtp.host.name
Sorry to bump an old thread, but something HAS to be done about the SMTP authentication in amember. Due to new spam laws, is this topic finally relevant enough for a fix for all amember versions??? Your SMTP authentication method you provided is a fault in the amember application. Here is why: 1) Using the format mentioned for SMTP authentication can leave you vulnerable. 2) No ability to define a port. 3) What about bounces??? Please finally provide a FIX (not an UPGRADE) for all "recent" amember versions on this issue.