| 1 |
>> > That kind of delivery limits the access to this mails to the local |
| 2 |
>> > maschine. If I want to read local I don't need mails, I could just read |
| 3 |
>> > the logfiles from portage in /var/log/ |
| 4 |
>> > |
| 5 |
>> > But I am aware that solving this problem is nothing that portage has to |
| 6 |
>> > do, as it is no problem with portage at all. |
| 7 |
>> > |
| 8 |
>> > My mail was just to show that not everyone has a local mailserver |
| 9 |
>> > running on his maschine. |
| 10 |
>> > |
| 11 |
>> > Greetings |
| 12 |
>> > |
| 13 |
>> > Sebastian |
| 14 |
>> > |
| 15 |
>> |
| 16 |
>> then let it store everything as elog and read that with elogv. |
| 17 |
>> |
| 18 |
>> mail is just an additional bonus feature. |
| 19 |
>> |
| 20 |
> |
| 21 |
> His initial mail said that he would like a copy of elogs to go to his inbox at |
| 22 |
> his ISP. Later mails imply he might want to read them over IMAP so they are |
| 23 |
> accessible at multiple locations. |
| 24 |
> |
| 25 |
> Sebastian, |
| 26 |
> |
| 27 |
> Have you looked at ssmtp? Very light, very small and you can protect your |
| 28 |
> login password with Unix file permissions instead of leaving them open in |
| 29 |
> make.conf |
| 30 |
|
| 31 |
Could I use ssmtp to send elog mail to my email address? I wouldn't |
| 32 |
even need a login password if this is all I use it for, right? |
| 33 |
|
| 34 |
- Gra t |
Archives