Are you talking about a seperate email to every registered user of your forum, every time a post is added? If it is going to be part of the script, where the user adds the post, you need to fork even if you use a local mailer. As your user list grows, you could be generating quite a few emails. Not something your user is going to want to wait for just to reply to a comment.

Another approach you might want to consider: instead of having it part of the script were the user adds the post, have a seperate maintenance script run at intervals in the background. The maintenance script could check to see if new post had been made (a central file with new post numbers or something else). When the maintenance script finds new posts, it could notify the users by email. This would not only free the poster from waiting for the script to generate mails for everyone on your user list, but the users could get a single email with notification of the posts within a time period instead of several emails as each post is made. I would also suggest that your users be given some way to opt-in or opt-out of your mailings. Registering on a forum that fills your mailbox without warning can be very annoying.

Chuck

In reply to Re: Re: forking() to send e-mail in CGI?? by wazoo
in thread forking() to send e-mail in CGI?? by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.