Archived from groups: alt.comp.periphs.webcam (
More info?)
On Sat, 1 Jan 2005 10:10:58 -0500, "johnQdoe"
<JohnQdoe@outthere.com> wrote:
>
>"Si Ballenger" <shb*NO*SPAM*@comporium.net> wrote in message
>news:41d64dcf.32948807@news.comporium.net...
>> On Sat, 1 Jan 2005 00:55:02 -0500, "johnQdoe"
>> <JohnQdoe@outthere.com> wrote:
>>
>> >Well didn't use Inetserv. I'm running XP Pro and it has IIS 5.1 with
>SMTP
>> >support. Took a few minutes to set it up and then directed the camera to
>> >the system. Worked first shot!
>> >
>> >Now I'm wondering why the heck it works if I use the PC as a pass through
>to
>> >the cable SMTP server? It appears to be using the very same information
>I
>> >entered in the camera config. Why can't it connect directly. I'd rather
>> >not leave the PC on but at least I got it to work in some fashion!
>>
>> I posted this once before for you. For sending mail via your ISP
>> smtp server, including a user name and password may be giving you
>> an authinication error (at least it does on my system). I suggest
>> you try *not* using a name and password and see what happens.
>> User names and passwords seem to be used for accessing your
>> email account and reading what is there.
>
>I did try not using a username or password but that didn't work either. But
>if no account or password is used, doesn't that mean anybody from any place
>could send email through the server? Not sure anybody would allow or want
>that type of open access.
If you are interested in experimenting, below is my origional
post with a link to the free sendemail windows application and
the info on using the application. The sendemail application
captures errors in a file for viewing, and thats where I noticed
authinication errors when I included the user name and password.
I think most smtp servers look at the originating IP address
(with in the ISPs domain or not) to determine if the email is
comming with in its system and should be sent. I've been testing
this setup to automatically send a webcam frame capture via email
when an event is triggered. In the batch file you would need to
put in the appropriate email addresses and smpt server info for
your test.
======================================
As strange as it may seem, you may not need your user name and
password. I've been tinkering with a free command line email
application called sendemail which was getting authorization
errors. I removed the user name and password from the command
line and it works. If you are sending to a mail server at your
current ISP, then may accept email from with in its system with
out the user and password. Below is what is required to send mail
with in the system of my ISP. From, to, subject, message, and
mail server. If you are using a mail server outside the system or
from another ISP, then the user name and password would
definately be needed. Try skipping the user name and password.
http://caspian.dotconf.net/menu/Software/SendEmail/
::========sendemail.bat==========
@echo off
sendemail.exe -f me@home.net -t me@work.net -u test -m send email
test -s smtp.myisp.net:25 -l error.txt
::==================================
sendemail.exe-1.50 by Brandon Zehm <caspian@dotconf.net>
Synopsis: sendemail.exe -f ADDRESS [options]
Required:
-f ADDRESS from (sender) email address
* At least one recipient required via -t, -cc, or -bcc
* Message body required via -m, STDIN, or -o
message-file=FILE
Common:
-t ADDRESS [ADDR ...] to email address(es)
-u SUBJECT message subject
-m MESSAGE message body
-s SERVER[
ORT] smtp mail relay, default is
localhost:25
Optional:
-a FILE [FILE ...] file attachment(s)
-cc ADDRESS [ADDR ...] cc email address(es)
-bcc ADDRESS [ADDR ...] bcc email address(es)
Paranormal:
-xu USERNAME authentication user (for SMTP
authentication)
-xp PASSWORD authentication password (for SMTP
authentication)
-l LOGFILE log to the specified file
-v verbosity, use multiple times for
greater effect
-q be quiet (no stdout output)
-o NAME=VALUE see extended help topic "misc" for
details
Help:
--help TOPIC The following extended help topics
are available:
addressing explain addressing and related
options
message explain message body input and
related options
misc explain -xu, -xp, and others
networking explain -s, etc
output explain logging and other output
options