Topic awaiting preservation: asp.net form2email seen as spam (Page 1 of 1) $Pages that link to <a href="https://ozoneasylum.com/backlink?for=28296" title="Pages that link to Topic awaiting preservation: asp.net form2email seen as spam (Page 1 of 1)" rel="nofollow" >Topic awaiting preservation: asp.net form2email seen as spam <span class="small">(Page 1 of 1)</span>\$

Boudga Maniac (V) Mad Scientist From: Jacks raging bile duct.... Insane since: Mar 2000	posted 08-03-2006 22:54 There is prolly something really silly I'm forgetting to do...perhaps someone can enlighten me. I created an asp.net form that emails on submit. It emails just fine and I get it but two other email addresses it is sent to threw it in the spam/junk folders immediately upon receipt. What can I do to prevent that? I believe it has something to do with authentication. Right now I am using the clients email address as the FROM address in the form. Should I be using an address located on my smtp server that I am sending from instead to prevent the appearance that it is spam? Nevermind: I ended up making the FROM addy an account located on the SMTP server I was sending from and that resolved the spam problem...the new email ended up in the INBOX as it should... (Edited by Boudga on 08-03-2006 23:00)

Topic awaiting preservation: asp.net form2email seen as spam (Page 1 of 1) $Pages that link to <a href="https://ozoneasylum.com/backlink?for=28296" title="Pages that link to Topic awaiting preservation: asp.net form2email seen as spam (Page 1 of 1)" rel="nofollow" >Topic awaiting preservation: asp.net form2email seen as spam <span class="small">(Page 1 of 1)</span>\$

Boudga
Maniac (V) Mad Scientist

From: Jacks raging bile duct....
Insane since: Mar 2000

posted 08-03-2006 22:54

There is prolly something really silly I'm forgetting to do...perhaps someone can enlighten me. I created an asp.net form that emails on submit. It emails just fine and I get it but two other email addresses it is sent to threw it in the spam/junk folders immediately upon receipt. What can I do to prevent that? I believe it has something to do with authentication. Right now I am using the clients email address as the FROM address in the form. Should I be using an address located on my smtp server that I am sending from instead to prevent the appearance that it is spam?

Nevermind: I ended up making the FROM addy an account located on the SMTP server I was sending from and that resolved the spam problem...the new email ended up in the INBOX as it should...

(Edited by Boudga on 08-03-2006 23:00)