Hi again!

Forgot to mention that I've installed the sha fingerprint for the
smtp.gmail.server.

-Mats

2014-10-29 22:43 GMT+01:00, Mats Olsson <plan9....@gmail.com>:
> Hi guys!
>
> OK, now I can get my mail but not send mail. This is what I've done:
>      Changed the header file in /mail/box/$user/headers (since it
> didn't exist i filled in the below).
>      Added my login information to factotum according to the docs.
>      Sent email to the server like this:
>        ;upas/smtp -d -a -h localhost.localdomain net!smtp.gmail.com
> myemail recipiente-mail
>          a window shows up like when retrieving mail to fill in the
> password
>
> A lot of thing are going on but terminates in "Username and Password
> not accepted
> Temporary failure, Retry "(all the time)
>
> The command:
>   ;tail -1 /sys/log/smtp results in the following:
>   myipaddr. the time and TLS started to smtp.gmail.com
>
> So obviously I'm missing something that I can't find in the
> documentation or the wiki. I would be eternally grateful if someone
> could shed some light on this. The only thing I can come up with is
> that the machinename is wrong but I've tried several with the same
> result. So, please help me out.
>
> Kind greetings,
> Mats
>
> 2014-10-27 20:10 GMT+01:00, erik quanstrom <quans...@quanstro.net>:
>> On Mon Oct 27 12:34:58 EDT 2014, lu...@proxima.alt.za wrote:
>>> > one does not have to put eve in adm or especially sys.  in fact, i
>>> > think
>>> > this
>>> > makes one's system significantly less secure.
>>>
>>> It's complicated, in that access controls are enforced by distinct
>>> entities with potentially very distinct criteria.  Trying to conceive
>>> all possible combination of clients, servers and third-party
>>> authenticators can lead to massive migraines.
>>
>> it's not complicated.  permissions work like unix.  there is simply
>> a lack of the unix requirement that the owner of the file server be
>> the owner of the cpu server.
>>
>> certainly one could require different creds for the same user on
>> every host, but we don't do that.
>>
>> - erik
>>
>>
>

Reply via email to