Topic: Sending Email Through your ISP's Email Server

[colwyn]

I am trying to change my outbound email from my SME V6.01-01 from using DNS to send to sending the emails through my ISp's email server. (My DSL connection has dynamic addresses and alot RBL services are rejecting them from dynamic).

My issue is that in server manger you can put in the IP address of your ISP's SMTP server but no username and password.

Is there a contrib that adds a username and password capability ?

Thanks,

Colwyn

[kozel]

I have found that you do not need a username and password for sending thru you isp's email server only receiving.  You isp allows you because you are on their network.  Of course, you case may be different.

[meanlocha]

I dont know how to do this in SME 6.0.1.  I have not
found a contrib to do it.

but in SME 7a17, there is a smtp-auth-proxy service
which combined with SMTPSmartHost will do the trick.

so the following or its equivalent might work (I have not tried it)
/sbin/e-smith/db configuration set SMTPSmartHost mailserver.ISP.net
/sbin/e-smith/db configuration setprop smtp-auth-proxy enabled Passwd yourpassword Userid youruserid
/sbin/e-smith/signal-event email-update

Anthony

[colwyn]

Unfortunately SBC DSL services requires username and password even if you are on their own network. Most of my previous ISP's did not do this but SBC has to make life difficult !!!

[meanlocha]

What I wrote above should have read like this:

/sbin/e-smith/db configuration set SMTPSmartHost mailserver.ISP.net
/sbin/e-smith/db configuration setprop smtp-auth-proxy status enabled Passwd yourpassword Userid youruserid
/sbin/e-smith/signal-event email-update

I also have SBC DSL and will be switching to SME7axx
very soon.  

My problem is that the old mail servers
mail.pacbell.net are equivalent to prodigy.net
mail servers which get frequently blacklisted
on bl.spamcop.net

Anthony

[woyzeck]

I don't use sme to send mail.  I have the workstations e-mail program set up to send mail through the isp as they require autentication with a username and password.  I do however use fetchmail to download e-mails from the isp so I can use clamav and spam assassin to scan for viruses and spam.

I don't know if this matters at all, but I run sme in server only mode.

Derek

[colwyn]

Setting the email client to send mail should resolve my problem until V7 gets released. Thanks for the help.

I know this question will get some hate mail, but why do we have to developement tracks (6.5 and 7.0) ?

Which is going to be the supported track ?

Colwyn

[gordonr]

I know this question will get some hate mail, but why do we have to developement tracks (6.5 and 7.0) ?

We don't, really. There is no new development planned on 6.5

6.5 is at Release Candidate 1 - the maintenance team are planning to update it with the latest updates and then release it. But they need to deal with updates for 6.0/6.0.1 first.

7.0 is still undergoing major changes and may be some time before it is released.

Which is going to be the supported track ?

Once 7.0 comes out, there should be no reason not to use 7.0, and every reason to do so. Until then, you should consider 6.5

Gordon

[jok11n]

Once 7.0 comes out, there should be no reason not to use 7.0, and every reason to do so. Until then, you should consider 6.5
Gordon

I guess the confusion is that neither are yet considered final and not knowing which will make it first. It does sound as though 6.5 is now very close but I would maybe still hesitate to change from 6.01 to 6.5 in the hopes that 7.0 is not too far away.

[gordonr]

I guess the confusion is that neither are yet considered final and not knowing which will make it first. It does sound as though 6.5 is now very close but I would maybe still hesitate to change from 6.01 to 6.5 in the hopes that 7.0 is not too far away.

7.0 is at Alpha, 6.5 is at Release Candidate (Alpha/Beta/RC/final) - the release candidate would have been updated if there were showstopper bugs.

[meanlocha]

I just installed SME 6.5RC1 and tried smtp-auth-proxy without
success.  I sent in a bug report:
http://no.longer.valid/mantis/bug_view_advanced_page.php?bug_id=0000260

I tried to do the same on SME7a26 but this version needs some
bug fixes to do a test of smtp-auth-proxy, for example:
http://sourceforge.net/tracker/?group_id=96750&atid=615772

Anthony

[meanlocha]

Despite the difficulty of the server-manager not saving
new settings, it is possible to work with SME7a26.
I am particularly interested in smtp-auth-proxy.
I tested SME7a26 smtp-auth-proxy and it
worked successfully.
Some output from /var/qmail/log/current:

2005-08-04 15:10:44.475579500 new msg 100133
2005-08-04 15:10:44.489056500 info msg 100133: bytes 275 from <user1@xxxx.xxx> qp 24780 uid 0
2005-08-04 15:10:44.510982500 starting delivery 11: msg 100133 to remote user2@yyyy.yyy
2005-08-04 15:10:44.511358500 status: local 0/10 remote 1/20
2005-08-04 15:10:46.810905500 delivery 11: success: 127.0.0.1_accepted_message./
Remote_host_said:_250_ok_1123193446_qp_59652/
2005-08-04 15:10:46.810931500 status: local 0/10 remote 0/20
2005-08-04 15:10:46.835691500 end msg 100133

and from /var/log/smtp-auth-proxy/current:

2005-08-04 15:10:17.941150500 2005/08/04-15:10:17 esmith::SMTPAuthProxy (type Net::Server::Fork) starting! pid(24582)
2005-08-04 15:10:18.222058500 Binding to TCP port 26 on host localhost
2005-08-04 15:10:18.405016500 Setting gid to "99 99"
2005-08-04 15:10:18.406985500 Setting uid to "99"
2005-08-04 15:10:45.428296500 220 smtp102.sbc.mail.mud.yahoo.com ESMTP

QED

Anthony

[daley]

This is interesting, i am still using smeserver 6.01, does smeserver v6.01 has this feature? if so, how shd i enable it?

Alternatively, does smeserver v6.5 work the same requirement?

Pls advise,
Daley

[meanlocha]

Read the whole thread and you will see:
6.0.1 does not have this feature;
6.5 has the feature and it does not *seem* to work - which means I did not get it to work;
7a26 has the feature and I confirmed that it works.

Anthony

[delineate]

I've been having fun w/ smtp-auth-proxy on 6.5RC2. I need to get this going for sbc as well - a major PITA. Anyways, I started out with smtp.sbcglobal.yahoo.com entered in "Address of Internet provider's mail server" in the server-manager.

Then I followed meanlocha's instructions above to add SMTPSmartHost, Userid, & Passwd.

Still am not able to auth. I get the following error in response to outgoing test mail and in /var/log/qmail/current:
"Remote host said: 530 authentication required - for help go to http://help.yahoo.com/help/us/sbc/dsl/mail/pop/pop-11.html"

I do a "netstat -nlt inet" and see, as expected:
tcp        0      0 127.0.0.1:26            0.0.0.0:*               LISTEN
which means smtp-auth-proxy is at least running.

I check /var/qmail/control/smtproutes, which has the following entry
:smtp.sbcglobal.yahoo.com

This doesn't make sense -as I understand it- the entry should be
:127.0.0.1:26
to forward all remote bound mail to the smtp-auth-proxy, which then forwards to smpt.sbcglobal.yahoo.com. sbcglobal in smtproutes would cause qmail to directly try to comunicate with that server, which bypasses smtp-auth-proxy!

If I manualy change the smtproutes to ":127.0.0.1:26", my outgoing mail properly gets passed to smtp-auth-proxy -> smtp.sbcglobal.yahoo.com -> destination smtp server.

So is this a bug, a feature, am I missing something, or have I cheated?
Irregardless, hope this helps someone else out...
David Lemstra