[pskmail] Re: Gmail as server SMTP
- From: "Dan Ozment" <dan@xxxxxxxxxx>
- To: <pskmail@xxxxxxxxxxxxx>
- Date: Thu, 29 Mar 2012 15:25:01 -0400
Bernie,
I don?t think the end user ? the sailor in your example ? should worry about
which SMTP server is being used to send his outbound mail. The SMTP server
that is specified on the pskmail server is the one that pskmail will use to
send outbound email. It doesn?t have anything to do with where the client
is or what his email address is. This is simply the next hop for the
pskmail server to send mail to. As long as the pskmail server I?m
currently using can connect to and authenticate with an SMTP server
somewhere it should be able to send my outbound mail.
From the perspective of an end user, I am going to send my outbound mail
from my pskmail client to the pskmail server. My job is to get my message
to the server. The server is responsible for sending it on its way over
the internet. As a client I don?t care how the server does that as long as
the mail is delivered. He can use any SMTP server that is available to him.
I do care about the POP settings. Those settings tell the pskmail server
where my actual mailbox lives and gives it the credentials to download mail
that has been delivered to me at that mailbox.
So, the POP settings are specific for each user, and I believe the SMTP
settings are specific for the server.
Dan
KJ4ZZE
From: pskmail-bounce@xxxxxxxxxxxxx [mailto:pskmail-bounce@xxxxxxxxxxxxx] On
Behalf Of Pär Crusefalk
Sent: Thursday, March 29, 2012 3:11 PM
To: pskmail@xxxxxxxxxxxxx
Subject: [pskmail] Re: Gmail as server SMTP
Hi Bernard,
Well, as the pskmail server will always use the same smtp server for all
clients there is no need for the client to care about the server smtp
settings. No need for the sailor to set up anything in advance, it will just
work. The client only has to send what pop account to fetch email from (the
usual settings upload) and the server will use the client email address as
the from and reply-to addresses on outgoing messages.
The password in user_db.pl used to be the plain text password but is now
encrypted using the session password as key.
73 de Per, sm0rwo
2012-03-29 19:29, Bernard Dekok skrev:
Hi Par,
Thanks.
You wrote a little something about Gmail in the old server manual and also
in some notes on the Wiki.
I think that was long ago, because Gmail has since added features such as
"allow access" to Gmail accounts from other accounts, locking out multiple
sign ins from a single IP address (different computers behind a single
router), and Captcha.
All can be handled in the Gmail "Settings" (Gear wheel) tab.
The problem with Gmail as a SMTP server then, is that a sailboat for
instance, will have to setup it's client Gmail address well in and advance
of the cruise.
It will have to anticipate the Gmail SMTP servers' radio footprints that it
will sail through, and set up the Gmail servers in advance with help of the
server sysops.
Or it can email the server sysops via APRS message, Iridium, or Winmor to
set the parameters....
Not really ideal.
I hope somebody can prove my thinking wrong.
Further question for you:
When manually setting up the client's user_db.pl file in the server, how is
the password handled ?
I see it is some code when coming in via radio.
Will a regular alphabet password work as well, or is the code needed ?
If so, what is the code ?
KC9SGV
On Thu, Mar 29, 2012 at 8:49 AM, Pär Crusefalk <per@xxxxxxxxxxxx> wrote:
Hi Bernard,
Yes, you can update that database manually. That's mostly how I do it
for myself, that way it's good to go right away :-).
Yes, gmail is both a blessing and a curse. It does not behave exactly
like other email servers and that has caused a lot of trouble. For
instance the settings regarding if it should present only new messages
or all messages has created the impression that pskmail does not see all
the messages in the account (you see all the messages in the web
interface but as the pop interface is set to show only new emails
pskmail only sees the new ones). I should write some more about it some
day, or perhaps I already did in the manual (can't remember now)..:-).
73 de Per, sm0rwo
Bernard Dekok skrev 2012-03-29 01:56:
> Thanks, Par,
>
> Yes, I realize it is all in the pskmailrc.pl <http://pskmailrc.pl>
> I looked at your code a bit, to the extent that I understand it.
> The user_db.pl <http://user_db.pl> has nothing to do with it.
> But sometimes a client can't update the server with a bad HF connection,
> as I found.
> The update does not "take".
> Then it would be possible for the server sysop to manually update the
> user-db.pl <http://user-db.pl> file, not so ?
> Would that even work ?
>
> Gmail is very spam-conscious.
> So Gmail it makes it hard for good intented users, like PSKmailers too,
> unfortunately.
> Once you get it working, it works just fine, though.
> I hope other server sysops can duplicate my findings as discussed.
>
> KC9SGV
>
>
>
> On Wed, Mar 28, 2012 at 6:57 AM, Pär Crusefalk <per@xxxxxxxxxxxx
> <mailto:per@xxxxxxxxxxxx>> wrote:
>
> Hi Bernard,
>
> I'm sorry but the server will only use one common smtp server for all
> users so this may look like its working but in reality it's your
> pskmailrc.pl <http://pskmailrc.pl> that is doing all the heavy
> lifting here.
> Users should of course fetch emails from their own accounts but the
> server will always send outgoing emails through the one server
> configured within pskmailrc.pl <http://pskmailrc.pl>. Here is the
> code that does it:
>
> sub send_mail {
> my($to, $from, $subject, @body)= @_;
> my $smtp;
>
> if ($smtpauthlevel != 2) # Will not use TLS Auth
> {
> $smtp = Net::SMTP->new($relay,
> Hello => $smtphelo,
> Debug => 1,);
> die "Could not open connection: $!" unless $smtp;
> if ($smtpauthlevel == 1 && $smtptlsuser ne '') # Plain AUTH here
> {
> if ( !$smtp->auth($smtptlsuser, $smtptlspass) ) {
> logprint ("SMTP authentication failed or is not needed.\n");
> }
> }
> }
> else # Will use TLS Auth
> {
> logprint ("SMTP TLS requested, no debug info available..\n");
> $smtp = new Net::SMTP::TLS($relay,
> Hello => $smtphelo,
> Port => $smtptlsport,
> User => $smtptlsuser,
> Password => $smtptlspass,
> Timeout => 10,
> Debug => 1);
> die "Could not open TLS connection: $!" if (! defined $smtp);
> }
> etc........
>
> So, it's the parameters from pskmailrc.pl <http://pskmailrc.pl> that
> are used.
>
> The problem with use of different smtp servers is also that other
> servers than gmail may have restricted access to users from within
their
> own network. That is, comcast may have an smtp server that only
> customers currently connected through comcast may access. Trying to
> access that smtp server when not connected through comcast will by
> default be regarded as a spam attempt. So, trying to use other smtp
> servers will fail.
>
> That user database is somewhat confusing here, it was designed many
> moons ago and the smtp server field is no longer used.
>
> 73 de Per, sm0rwo
>
>
>
> Bernard Dekok skrev 2012-03-28 13:15:
> > Hi All,
> >
> > Some new tips on handling Gmail as server SMTP which worked for me.
> >
> > Below is an example of a working server
> > *"user_db.pl <http://user_db.pl> <http://user_db.pl>"* file *using
> Gmail as SMTP host*.
> > Note that the *Pop user is also with Gmail,* in this case, but with
a
> > *different* Gmail address account.
> > The Pop user will have to go into his Gmail account and *allow
access*
> > to the
> > server SMTP Gmail account, to access his Pop user account.
> > It will work OK initially without this step above, but then later it
> > suddenly won't....
> >
> > K1RJV K3UK AI7RR K2MO K8ZAG KC9SGV KZ5ED
> >
> > Station callsign: KC9SGV
> >
> > Commands for KC9SGV:
> > 1: Pop host = pop.gmail.com <http://pop.gmail.com>
> <http://pop.gmail.com>
> > 2: Pop user = kc9sgv1000@xxxxxxxxx <mailto:kc9sgv1000@xxxxxxxxx>
> <mailto:kc9sgv1000@xxxxxxxxx <mailto:kc9sgv1000@xxxxxxxxx>>
> > 3: Pop password = mysecret
> > 4: SMTP server = smtp_host
> > 5: From address = kc9sgv1000@xxxxxxxxx
> <mailto:kc9sgv1000@xxxxxxxxx> <mailto:kc9sgv1000@xxxxxxxxx
> <mailto:kc9sgv1000@xxxxxxxxx>>
> > 6: Mail file = /home/administrator/.pskmail/.mailuser (or similar)
> > 7: APRS password = none
> > 9: Delete callsign
> > 0: Exit
> >
> > Command nr:
> >
> > The *server station* also needs to *signed out of all Google and
Gmail
> > accounts* from the same IP address.
> > Otherwise Gmail handles multiple simultaneous transactions as
> > undesirable, and locks the server out.
> > The client must enable POP, and disable IMAP in his Gmail account.
> >
> > Hope it works for you too.
> > KC9SGV
> >
>
>
> --
> Mobile: +46703784299 <tel:%2B46703784299> <tel:%2B46703784299>
>
>
--
Mobile: +46703784299 <tel:%2B46703784299>
Other related posts:
