Re: A sendmail warning

This WebDNA talk-list message is from

2005


It keeps the original formatting.
numero = 63689
interpreted = N
texte = On 27.12.2005, at 14:13, William DeVaul wrote: > I think sendmail only writes to a folder and then another program > trickles the emails out. I guess one trick is to make sure the > email server can handle the rate at which WebDNA sends the emails. I was referring to sendmail as the standard Unix mailserver. "sendmail" is the name of that program which comes with almost every Unix distribution. The sendmail in WebDNA is something like a synonyme and can lead to any mailserver (not the best name for a command...) But you are right, the command writes files to a folder from where they get transferred or collected from a mailserver, I don't know the details. > Do you have any experience with writing the emails to the email > server directly? I'm not sure I can do that now, but I'd like to > know where to begin. Yes, we do that with mass emails from PHP based webservers. PHP doesn't send as brutally as WebDNA but mass mailing from a webserver isn't a good idea. The machine goes up to 85% CPU load. That is not really bad on a Unix server but it isn't fine either. That's why we go directly to the mailserver. Our mailserver is Communigate Pro and it is inhouse. Currently we send our mails from PHP servers over direct connection (via a shell command) to a folder on the mailserver. A cron job runs on the mailserver which puts the files into the send folder via a Perl script. Actually there are different Perl scripts. Version A handles a sent address list and just one mail file for non-personalized mails where we use the mailing list function of the mailserver. Version B handles individual files for personalized mails, they are sent as single mails. I am not really happy with that and would prefer to transfer the files via FTP. We haven't checked all security issues yet but that would be more reliable than the current way. If it is to dangerous we plan to set up a separate SMTP server. It depends on your mailserver if you can do it or not. If it delivers mails out of a folder you can put your mailfiles in that folder. They must be complete mailfiles folowing the SMTP specifications (including the header) because they are sent without processing. I do not know right away how the files from WebDNA look like but probably they are ready to send? In most environments the access to the mailserver is an organizational or security-related problem. You need either a direct connection or FTP to that machine. You need the permissions to write to the send folder or you write it to another folder and run something like a Perl script which moves your files to the send folder. Perhaps it is a better idea to setup a mailserver just for that. I guess any old machine can handle that if it has no other duties. A dedicated SMTP server can be made pretty secure behind a firewall. ___ Peter Ostry ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: A sendmail warning ( Patrick McCormick 2005)
  2. Re: A sendmail warning ( William DeVaul 2005)
  3. Re: A sendmail warning ( William DeVaul 2005)
  4. Re: A sendmail warning ( Peter Ostry 2005)
  5. Re: A sendmail warning ( Peter Ostry 2005)
  6. Re: A sendmail warning ( William DeVaul 2005)
  7. Re: A sendmail warning ( William DeVaul 2005)
  8. Re: A sendmail warning ( Joe D'Andrea 2005)
  9. Re: A sendmail warning ( William DeVaul 2005)
  10. Re: A sendmail warning ( William DeVaul 2005)
  11. Re: A sendmail warning ( Terry Wilson 2005)
  12. Re: A sendmail warning ( Terry Wilson 2005)
  13. Re: A sendmail warning ( Peter Ostry 2005)
  14. Re: A sendmail warning ( Kenneth Grome 2005)
  15. A sendmail warning ( William DeVaul 2005)
On 27.12.2005, at 14:13, William DeVaul wrote: > I think sendmail only writes to a folder and then another program > trickles the emails out. I guess one trick is to make sure the > email server can handle the rate at which WebDNA sends the emails. I was referring to sendmail as the standard Unix mailserver. "sendmail" is the name of that program which comes with almost every Unix distribution. The sendmail in WebDNA is something like a synonyme and can lead to any mailserver (not the best name for a command...) But you are right, the command writes files to a folder from where they get transferred or collected from a mailserver, I don't know the details. > Do you have any experience with writing the emails to the email > server directly? I'm not sure I can do that now, but I'd like to > know where to begin. Yes, we do that with mass emails from PHP based webservers. PHP doesn't send as brutally as WebDNA but mass mailing from a webserver isn't a good idea. The machine goes up to 85% CPU load. That is not really bad on a Unix server but it isn't fine either. That's why we go directly to the mailserver. Our mailserver is Communigate Pro and it is inhouse. Currently we send our mails from PHP servers over direct connection (via a shell command) to a folder on the mailserver. A cron job runs on the mailserver which puts the files into the send folder via a Perl script. Actually there are different Perl scripts. Version A handles a sent address list and just one mail file for non-personalized mails where we use the mailing list function of the mailserver. Version B handles individual files for personalized mails, they are sent as single mails. I am not really happy with that and would prefer to transfer the files via FTP. We haven't checked all security issues yet but that would be more reliable than the current way. If it is to dangerous we plan to set up a separate SMTP server. It depends on your mailserver if you can do it or not. If it delivers mails out of a folder you can put your mailfiles in that folder. They must be complete mailfiles folowing the SMTP specifications (including the header) because they are sent without processing. I do not know right away how the files from WebDNA look like but probably they are ready to send? In most environments the access to the mailserver is an organizational or security-related problem. You need either a direct connection or FTP to that machine. You need the permissions to write to the send folder or you write it to another folder and run something like a Perl script which moves your files to the send folder. Perhaps it is a better idea to setup a mailserver just for that. I guess any old machine can handle that if it has no other duties. A dedicated SMTP server can be made pretty secure behind a firewall. ___ Peter Ostry ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Peter Ostry

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Email notification to one of multiple vendors ? (1997) Protect (1997) gateway application timeouts (1998) Adding Items to Cart (2003) [WebDNA] Domain upgrade questions (2009) WebCatalog Hosting (1996) Alternating colors (1997) WebCat2 several catalogs? (1997) populating a [table] (2004) WebCat2 Append problem (B14Macacgi) (1997) WebCatalog for Postcards ? (1997) Search repost: (2000) Card clearance, problems - solutions? (1997) searchable list archive (1997) Calculating multiple shipping... (1997) [WebDNA] linux linux linux (2009) WebCat2b13MacPlugIn - More limits on [include] (1997) Locking up with WebCatalog... (1997) I figured it out (1999) request for string functions (1998)