|
code
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Sending emailI am writing an app which needs to create and send email messages.
The machines on which this app will be running do not have any installed email client (these machines are on the plant floor). A further wrinkle is that the virus software is setup to block any out going traffic on port 25 (thereby ruling out using winsock on port 25). Can anyone suggest any options for accomplishing this? Thanks, Steve i can only share what one company did :-)
winsock on port 25 was used. The firewall was configured to allow port 25 traffic for that specific EXE file. Meaning of course, that port 25 was available only for that application and closed for any other application. The wrinkle here, is that only the compiled app will send email, so you won't be able send email running the app within the VB IDE, only from the compiled program unless, of course, you also unblock the IDE's EXE file. Perhaps some else can chime in with a real solution to your problem. Regards, Saga -- Show quoteHide quote"Steve" <sredmyeNONr@SPAMMErfcorp.com> wrote in message news:1172587851.866879.292250@k78g2000cwa.googlegroups.com... >I am writing an app which needs to create and send email messages. > The machines on which this app will be running do not have any > installed email client (these machines are on the plant floor). > > A further wrinkle is that the virus software is setup to block any out > going > traffic on port 25 (thereby ruling out using winsock on port 25). > > Can anyone suggest any options for accomplishing this? > > Thanks, > Steve > vbSendMail (www.freevbcode.com) might do the trick. You can specify the SMTP
port to use if 25 isn't your default. Show quoteHide quote "Steve" <sredm***@rfcorp.com> wrote in message news:1172587851.866879.292250@k78g2000cwa.googlegroups.com... >I am writing an app which needs to create and send email messages. > The machines on which this app will be running do not have any > installed email client (these machines are on the plant floor). > > A further wrinkle is that the virus software is setup to block any out > going > traffic on port 25 (thereby ruling out using winsock on port 25). > > Can anyone suggest any options for accomplishing this? > > Thanks, > Steve >
Show quote
Hide quote
On Feb 27, 11:53 am, "Nobody" <trin***@nobody.com> wrote: Ability to specify the port is not the problem (i can do this quite> vbSendMail (www.freevbcode.com) might do the trick. You can specify the SMTP > port to use > if 25 isn't your default. > > "Steve" <sredm***@rfcorp.com> wrote in message > > news:1172587851.866879.292250@k78g2000cwa.googlegroups.com... > > > > >I am writing an app which needs to create and send email messages. > > The machines on which this app will be running do not have any > > installed email client (these machines are on the plant floor). > > > A further wrinkle is that the virus software is setup to block any out > > going > > traffic on port 25 (thereby ruling out using winsock on port 25). > > > Can anyone suggest any options for accomplishing this? > > > Thanks, > > Steve- Hide quoted text - > > - Show quoted text - simply with the winsock control or API) but since the server is listening on port 25 that aint going to do me much good. "Steve" <sredm***@rfcorp.com> wrote in message Create a relay/proxy server running where it can connect to the real SMTPnews:1172595916.571973.180640@t69g2000cwt.googlegroups.com > Ability to specify the port is not the problem (i can do this quite > simply with the winsock control or API) but since the server is > listening on port 25 that aint going to do me much good. server and connect to that instead? Configure an SMTP server listening on another port? Record the email info in a database somewhere and have another job that reads it and sends the emails? Unblock port 25 on machines that need to use it? -- Reply to the group so all can participate VB.Net: "Fool me once..." Let me get this straight -
Your anti-virus software is blocking port 25, but your server is on port 25? Nothing VB does can over-ride a blocked port. You need to allow your anti-virus program to get out on Port 25. Show quoteHide quote "Steve" <sredm***@rfcorp.com> wrote in message news:1172595916.571973.180640@t69g2000cwt.googlegroups.com... > On Feb 27, 11:53 am, "Nobody" <trin***@nobody.com> wrote: > > vbSendMail (www.freevbcode.com) might do the trick. You can specify the SMTP > > port to use > > if 25 isn't your default. > > > > "Steve" <sredm***@rfcorp.com> wrote in message > > > > news:1172587851.866879.292250@k78g2000cwa.googlegroups.com... > > > > > > > > >I am writing an app which needs to create and send email messages. > > > The machines on which this app will be running do not have any > > > installed email client (these machines are on the plant floor). > > > > > A further wrinkle is that the virus software is setup to block any out > > > going > > > traffic on port 25 (thereby ruling out using winsock on port 25). > > > > > Can anyone suggest any options for accomplishing this? > > > > > Thanks, > > > Steve- Hide quoted text - > > > > - Show quoted text - > > Ability to specify the port is not the problem (i can do this quite > simply with the winsock control or API) but since the server is > listening on port 25 that aint going to do me much good. > "Steve" wrote...
Show quoteHide quote : I am writing an app which needs to create and send email You can connect to an SMTP server locally which relays the: messages. The machines on which this app will be running : do not have any installed email client (these machines are on : the plant floor). : : A further wrinkle is that the virus software is setup to block : any out going traffic on port 25 (thereby ruling out using : winsock on port 25). : : Can anyone suggest any options for accomplishing this? : : Ability to specify the port is not the problem (i can do this : quite simply with the winsock control or API) but since the : server is listening on port 25 that aint going to do me much : good. message out. You request the IIS firewall managers to open port 25 for your application only. That way you can connect to remote servers which immediately switch you over to another port anyways so that they can continue to listen for more connections on port 25. So you'll need to get the IIS firewall managers to allow your app to connect out not only through port 25 but ALL other ports as well. Or you can build your own server which uses another port and accepts initial connections through a another specific port. You probably need to get approval anyways, right? It's not too difficult to build your own server. MS provided some samples inside MSDN under the Winsock titles. Server simply means an app that listens for connections and then handles the incoming connections and provides a way to transfer data. Hope this helps some. -- Jim Carlock Post replies to the group. Just be aware that many anti-spam scanners will pick up on SMTP relays and
flag the message as spam (or at least give it a very high likelihood of being spam). Rob Show quoteHide quote "Jim Carlock" <anonymous@localhost> wrote in message news:e9t%23FRpWHHA.600@TK2MSFTNGP05.phx.gbl... > "Steve" wrote... > : I am writing an app which needs to create and send email > : messages. The machines on which this app will be running > : do not have any installed email client (these machines are on > : the plant floor). > : > : A further wrinkle is that the virus software is setup to block > : any out going traffic on port 25 (thereby ruling out using > : winsock on port 25). > : > : Can anyone suggest any options for accomplishing this? > : > : Ability to specify the port is not the problem (i can do this > : quite simply with the winsock control or API) but since the > : server is listening on port 25 that aint going to do me much > : good. > > You can connect to an SMTP server locally which relays the > message out. > > You request the IIS firewall managers to open port 25 for your > application only. That way you can connect to remote servers > which immediately switch you over to another port anyways so > that they can continue to listen for more connections on port 25. > So you'll need to get the IIS firewall managers to allow your app > to connect out not only through port 25 but ALL other ports as > well. > > Or you can build your own server which uses another port and > accepts initial connections through a another specific port. You > probably need to get approval anyways, right? > > It's not too difficult to build your own server. MS provided some > samples inside MSDN under the Winsock titles. Server simply > means an app that listens for connections and then handles the > incoming connections and provides a way to transfer data. > > Hope this helps some. > > -- > Jim Carlock > Post replies to the group. > > In article <1172587851.866879.292***@k78g2000cwa.googlegroups.com>,
sredm***@rfcorp.com (Steve) wrote: > *From:* "Steve" <sredm***@rfcorp.com> Remote-controlled carrier pigeons?> > I am writing an app which needs to create and send email messages. > The machines on which this app will be running do not have any > installed email client (these machines are on the plant floor). > > A further wrinkle is that the virus software is setup to block any out > going traffic on port 25 (thereby ruling out using winsock on port 25). > > Can anyone suggest any options for accomplishing this? http://www.theregister.co.uk/2007/02/27/remote_controlled_pigeons/ :^) Regards John (john@jeasonNoSpam.cix.co.uk) Remove the obvious to reply...
Show quote
Hide quote
"John K.Eason" <john@jeasonNoSpam.cix.co.uk> wrote in message No need to re-invent the wheel...news:memo.20070227173500.3832A@jeason.compulink.co.uk > In article <1172587851.866879.292***@k78g2000cwa.googlegroups.com>, > sredm***@rfcorp.com (Steve) wrote: > >> *From:* "Steve" <sredm***@rfcorp.com> >> >> I am writing an app which needs to create and send email messages. >> The machines on which this app will be running do not have any >> installed email client (these machines are on the plant floor). >> >> A further wrinkle is that the virus software is setup to block any >> out going traffic on port 25 (thereby ruling out using winsock on >> port 25). >> >> Can anyone suggest any options for accomplishing this? > > Remote-controlled carrier pigeons? > > http://www.theregister.co.uk/2007/02/27/remote_controlled_pigeons/ :^) http://www.faqs.org/rfcs/rfc1149.html -- Reply to the group so all can participate VB.Net: "Fool me once..." In article <OV7QiZpWHHA.3***@TK2MSFTNGP02.phx.gbl>, tiredofit@nospam.ever
(Bob Butler) wrote: Yes. but that doesn't suggest a method of routing them correctly! :^) Regards John (john@jeasonNoSpam.cix.co.uk) Remove the obvious to reply... On Feb 27, 12:35 pm, j...@jeasonNoSpam.cix.co.uk (John K.Eason) wrote:
Show quoteHide quote > In article <1172587851.866879.292***@k78g2000cwa.googlegroups.com>, Now thats funny!!!> > sredm***@rfcorp.com (Steve) wrote: > > *From:* "Steve" <sredm***@rfcorp.com> > > > I am writing an app which needs to create and send email messages. > > The machines on which this app will be running do not have any > > installed email client (these machines are on the plant floor). > > > A further wrinkle is that the virus software is setup to block any out > > going traffic on port 25 (thereby ruling out using winsock on port 25). > > > Can anyone suggest any options for accomplishing this? > > Remote-controlled carrier pigeons? > > http://www.theregister.co.uk/2007/02/27/remote_controlled_pigeons/:^) > > Regards > John (j...@jeasonNoSpam.cix.co.uk) Remove the obvious to reply... "John K.Eason" posted...
: Remote-controlled carrier pigeons? LOL: : http://www.theregister.co.uk/2007/02/27/remote_controlled_pigeons/ http://en.wikipedia.org/wiki/Stop_the_pigeon -- Jim Carlock Post replies to the group. These posts have been helpful but what I am looking for is some other
way (other than SMTP over port 25). I know it is possible because my machine (which has port 25 blocked) has no problem sending email via my email client (Outlook). If Outlook can send email around the blocked port there must be a way. If the machines on the plant floor had Outlook installed I would just automate Outlook to send the mail. But as I said in the original post those machines have no email client installed. Any ideas "Steve" <sredm***@rfcorp.com> wrote in message Your outlook clients are conencting to the exchange server using othernews:1172597996.674745.62250@z35g2000cwz.googlegroups.com > These posts have been helpful but what I am looking for is some other > way (other than SMTP over port 25). I know it is possible because my > machine (which has port 25 blocked) has no problem sending email via > my email client (Outlook). If Outlook can send email around the > blocked port there must be a way. If the machines on the plant floor > had Outlook installed I would just automate Outlook to send the mail. > But as I said in the original post those machines have no email client > installed. ports; that server is sending the mail for you. You can do essentially the same thing if you can run a server application on a system that doesn't have port 25 blocked. -- Reply to the group so all can participate VB.Net: "Fool me once..." "Steve" posted...
: These posts have been helpful but what I am looking for is some Okay, you need to set up a client app on those systems that are: other way (other than SMTP over port 25). I know it is possible : because my machine (which has port 25 blocked) has no problem : sending email via my email client (Outlook). If Outlook can send : email around the blocked port there must be a way. If the : machines on the plant floor had Outlook installed I would just : automate Outlook to send the mail. But as I said in the original : post those machines have no email client installed. to receive the messages. You don't even have to use SMTP to send the messages. You decide which ports the client listens on and then have your server send out to each machine that is to receive the message, or you broadcast the message and all will receive the same message at the same time, but this complicates things a little, especially if you want to guarantee delivery, meaning the each client sends back a response to the server app (which listens on its own port, meaning you need multiple winsock controls, one which constantly listens, one which then accepts connections and repliesl). Broadcasting works great when all clients are on the same network (ie, a 10.x.x.x or other like network). How you implement it depends upon your network configuration, and the number of systems you need to reply to. The client can reply with an MD5 checksum on the messages it receives. And then the server verifies the checksum and simply closes the connection. -- Jim Carlock Post replies to the group.
Show quote
Hide quote
On Feb 27, 3:58 pm, "Jim Carlock" <anonymous@localhost> wrote: Ok none of the suggestions thus far are viable for my situation. A> "Steve" posted... > : These posts have been helpful but what I am looking for is some > : other way (other than SMTP over port 25). I know it is possible > : because my machine (which has port 25 blocked) has no problem > : sending email via my email client (Outlook). If Outlook can send > : email around the blocked port there must be a way. If the > : machines on the plant floor had Outlook installed I would just > : automate Outlook to send the mail. But as I said in the original > : post those machines have no email client installed. > > Okay, you need to set up a client app on those systems that are > to receive the messages. You don't even have to use SMTP to > send the messages. You decide which ports the client listens on > and then have your server send out to each machine that is to > receive the message, or you broadcast the message and all will > receive the same message at the same time, but this complicates > things a little, especially if you want to guarantee delivery, > meaning the each client sends back a response to the server app > (which listens on its own port, meaning you need multiple > winsock controls, one which constantly listens, one which then > accepts connections and repliesl). Broadcasting works great > when all clients are on the same network (ie, a 10.x.x.x or other > like network). > > How you implement it depends upon your network configuration, > and the number of systems you need to reply to. The client can > reply with an MD5 checksum on the messages it receives. And > then the server verifies the checksum and simply closes the > connection. > > -- > Jim Carlock > Post replies to the group. solution that requires that something other than my app handle the mail is unacceptable for a number of reasons. The primary one is to many points of failure. I realize the question I am about to pose may cause some to cringe but here goes. Is there a way to build and send the TCP packet under the radar (so to speek) of the virus software so that it can get through? Alternatively is there a way to disable the virus software while sending then re-enable when finished >Is there a way to build and send the TCP packet under the radar... The problem with that is that if you manage to do it this way, theanti virus software isn't very effective. Disabling the antivirus is always an option, but if you are going to go to that extreme, it is better to simply unblock port 25 for your application. It would seem that if this is not a feasible solution, disabling the anti virus would be even more unfeasible by orders of magnitude. This is, of course, if you can even do it, since some companies have group policies for this kind of thing, so even if you do manage to disable the antivirus the policy will just reenable it again within seconds or minutes. I understand your problem, mostly because I had to go through it. The problem I had was going through Outlook in that it always pops up at least one dialog to get the user's confirmation to allow an app to send email. For an automated process, this was totally unacceptable. The "solution" was to install and use Outlook 97 on the PCs that needed to send automated email. Not a good thing. So I put together a small component (a form) that sent email through SMTP, totally bypassing Outlook. This worked like a charm, except that the antivirus blocked port 25 and opening the port was, as you say, not feasible. As I mentioned in another earlier post, the tradeoff was to disable port 25 for the specific EXEs that use the SMTP component. Not a perfect 10, but the solution at least minimized risk by not disabling the antivirus and by not unblocking port 25 for general use. Best regards Saga -- Show quoteHide quote"Steve" <sredmyerNON@SPAMMErfcorp.com> wrote in message news:1172682051.545573.269080@j27g2000cwj.googlegroups.com... > On Feb 27, 3:58 pm, "Jim Carlock" <anonymous@localhost> wrote: >> "Steve" posted... >> : These posts have been helpful but what I am looking for is some >> : other way (other than SMTP over port 25). I know it is possible >> : because my machine (which has port 25 blocked) has no problem >> : sending email via my email client (Outlook). If Outlook can send >> : email around the blocked port there must be a way. If the >> : machines on the plant floor had Outlook installed I would just >> : automate Outlook to send the mail. But as I said in the original >> : post those machines have no email client installed. >> >> Okay, you need to set up a client app on those systems that are >> to receive the messages. You don't even have to use SMTP to >> send the messages. You decide which ports the client listens on >> and then have your server send out to each machine that is to >> receive the message, or you broadcast the message and all will >> receive the same message at the same time, but this complicates >> things a little, especially if you want to guarantee delivery, >> meaning the each client sends back a response to the server app >> (which listens on its own port, meaning you need multiple >> winsock controls, one which constantly listens, one which then >> accepts connections and repliesl). Broadcasting works great >> when all clients are on the same network (ie, a 10.x.x.x or other >> like network). >> >> How you implement it depends upon your network configuration, >> and the number of systems you need to reply to. The client can >> reply with an MD5 checksum on the messages it receives. And >> then the server verifies the checksum and simply closes the >> connection. >> >> -- >> Jim Carlock >> Post replies to the group. > > Ok none of the suggestions thus far are viable for my situation. A > solution that requires that something other than my app handle the > mail is unacceptable for a number of reasons. The primary one is to > many points of failure. > > I realize the question I am about to pose may cause some to cringe but > here goes. Is there a way to build and send the TCP packet under the > radar (so to speek) of the virus software so that it can get through? > Alternatively is there a way to disable the virus software while > sending then re-enable when finished > 
Other interesting topics
|
|||||||||||||||||||||||
