The solution that comes in mind is to use username and password to prove to
my server who I am, but I didn't find how to implement this solution (if it's
possible at all).
Suggestions? Comments? Please tell!
Michael
I didn;t think sendmail could do this.
I get around the problem simply by sshing in remotely and using pine.
Jason
Seems to be off-topic, but anyway:
SMTP AUTH or STARTTLS. You need 8.10/8.11 (8.11.1 is current). See
http://www.sendmail.org/~ca/email/starttls.html
http://www.sendmail.org/~ca/email/auth.html
or: http://www.sendmail.org/~ca/email/roaming.html
There are a couple things you can do about this:
1. SSH in and rebuild your MTA's relay database with your current IP
address.
2. Modify your POP3 daemon to build a database that your MTA can read for
relaying purposes and then automatically add any IP's that authenticate via POP3.
3. Run a daemon that parses your POP3 logs and automatically creates a database
every few minutes that your MTA can access for relaying purposes.
__
John Kerbawy <jo...@maKintosh.com>
http://www.postfix.org
http://www.cise.ufl.edu/help/software/www/postfix-ssl/
Hope this helps!
Tom
----- Original Message -----
From: Michael Richard <rich...@gel.ulaval.ca>
To: <mi...@openbsd.org>
Sent: Thursday, October 05, 2000 11:24 AM
Subject: Using sendmail w/ username & password?
>
> I'd like to use my smtp server from an outside network. Obviously, I get
an
> error message saying something like "relaying denied" (I didn't try, but
we
> all know that it will happen if I do). As I can connect from many
different
> addresses, I don't want to allow relaying from a large range of IPs.
>
> The solution that comes in mind is to use username and password to prove
to
> my server who I am, but I didn't find how to implement this solution (if
it's
> possible at all).
>
ssh -L25:localhost:25 your.server
and then use localhost as your smtp server. Yeah, make sure that your
remote sendmail excepts mail for relaying from localhost.
>>>>> "Michael" == Michael Richard <rich...@gel.ulaval.ca> writes:
Michael> The solution that comes in mind is to use username and
Michael> password to prove to my server who I am, but I didn't find
Michael> how to implement this solution (if it's possible at all).
Michael> Suggestions? Comments? Please tell!
> > The solution that comes in mind is to use username and password to prove to
> > my server who I am, but I didn't find how to implement this solution
> > (if it's possible at all).
> Seems to be off-topic, but anyway:
> SMTP AUTH or STARTTLS.
Another idea is to use SMTP after POP.
-Dominik
--
/* Dominik Rothert | d...@astorit.com *
* A S T O R I T | http://www.astorit.com/ *
* Hohenzollernring 52 | fon +49-221-251440 *
* 50672 Cologne, Germany | fax +49-221-251443 */:wq!
I've solved this on a limited basis by using qpopper and XTND XMIT.
POP3 has the ability to be a mail transport agent inbound as well as
outbound, but nobody really uses it. I use Eudora as my mail client,
which is one of the few agents that does support the XTND XMIT
command set. Works like a charm. Combined with APOP, this has
essentially removed any requirement for SMTP relaying at all on my
mail server. All mail in and out of my laptop or remote mail viewing
systems is handled by popper.
See:
ftp://ftp.qualcomm.com/eudora/servers/unix/popper/
The drawback is that you have to use Eudora unless you can find other
MTAs that use XTND XMIT (and preferably APOP, if you want encrypted
passwords.) I'm sure that there are some open source packages that
do, but I haven't researched it lately.
JT
yet another idea is to scp the hole mailspool from the server.
ssh -l loginid mailserver -f mv /var/mail/loginid /tmp/loginid_fetchme
scp -C loginid@mailserver:/tmp/loginid_fetchme /tmp/my_new_mail
formail -s procmail < /tmp/my_new_mail
------------=_970818790-24790-0
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: binary
There is a race condition in your code. If the mail server crashes during
the scp and it cleans /tmp on re-boot then your mail is lost.
Here is what I do:
ssh -a -x -f -L:2110:localhost:110 -l loginid mailserver sleep 5
fetchmail -P2110 -p pop3 localhost
You should pick an available port number instead of 2110 if you need 100%
reliability. And this has no relevance to the current topic (smtp), sorry.
Amanda.
------------=_970818790-24790-0--