Andrew, all depends on how the business is organised; here I am a "infrastructure" guy (I take care of servers etc.); developpers are in another unit... We push for developpers guidelines/internal procedures, but as we don't have the same bosses, guess what? ;(
On Fri, Sep 12, 2008 at 10:12, Andrew Scott <[EMAIL PROTECTED]>wrote: > Ideally... > > I would be looking at improving the practice on these developers, for > example one should be well aware that settings in development and > production > need to be different. So putting such things as services and other handlers > in place, that would do the job and regardless of what server you are on > those settings are pulled up. > > Hence you could totally say that if in development the to field will always > be a test account. > > However I know that was not your question, and the adivce you have been > given will solve your problem. But as I stated, you really should try to > begin to nip this in the butt now and begin to get these guys to adhere to > some guidelines / internal development procedures. > > Just a thought. > > > On Fri, Sep 12, 2008 at 8:12 AM, Beru <[EMAIL PROTECTED]> wrote: > > > Denstar, I might be interested in this "subethasmtp", how do you use it? > So > > if this is not a real smtp daemon, I guess you can define it as your mail > > server in CF admin, but what happens to your mail once submitted to > > subethasmtp? > > > > On Wed, Sep 10, 2008 at 22:41, denstar <[EMAIL PROTECTED]> wrote: > > > > > On Wed, Sep 10, 2008 at 8:10 AM, Beru wrote: > > > .... > > > > - One way is to define rules on the smtp server to rewrite the > > > destination > > > > address to a unique junk email box, but this means we have to fiddle > > with > > > > smtp rules... pffff... > > > > > > Ouch. > > > > > > > - The other way around would have been to use cfmailparam to do this, > > but > > > I > > > > find no practical way to include this in the existing codebase > without > > > > adding code to each page > > > > > > Well, you could pretty easily use a regular expression to find all > > > your cfmail tags, and add/replace the "mailhost" bit with a variable, > > > and then set the variable somewhere. > > > > > > But you'll find, eventually, that you want do do other stuff, like > > > maybe just test the basics, without sending anything anywhere, etc.. > > > > > > So the real advice is to abstract all those <cfmail tags into a > > > component, and use that component instead. Then you can do whatever > > > the hell you want to do, without changing everything everywhere. > > > > > > Side note: I've got a subethaSMTP thing that listens on whatever port > > > you specify, and acts like a mail server. Great for "live" testing > > > without a real email server (sorta like a test harness). I'm willing > > > to trade it for beer. > > > Or a postcard. > > > Or just someone asking for it. > > > (it's not really worth beer, but it's sorta nifty, maybe) > > > > > > Anyways tho, abstract those mails when you get a chance, but a > > > variable would probably get you what you need, quick. > > > Regex is your friend! > > > > > > -- > > > But he who dies in despair has lived his whole life in vain. > > > Theodor Adorno > > > > > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;203748912;27390454;j Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:312418 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
