I assume that they are
forking because they are
actually delivering the mail, rather than queueing
it to the mailer on the machine.
If they were using Net::SMTP, and using the
smtpsend method, the CGI script would have to do the
appropriate DNS lookups, connect to remote MTA ( mail
transport agent ), and deliver the mail.
Since this process can take quite a while, you usually
don't want your web browser user to have to wait for
it. The fork would allow the mailing to run as a separate process, and the web user wouldn't have to wait.
Supposing there's a usable mailer on the web server, I would
just queue it there. No need for fork, and you have an
intelligent mailer that can retry, etc. See Mail::Mailer or look around for another module
that fits your needs.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.