Re: How to handle MacPorts' handles in the future (including the email address connected to it)??

2016-11-05 Thread Marko Käning 
Hi Ryan,

On 02 Nov 2016, at 23:49 , Ryan Schmidt  wrote:
> I'm confused about why you're confused or what you're talking about.

:)


> We've always provided @macports.org email forwarding for committers. You tell 
> us what handle you want, we set it up to forward to whatever email address 
> you want. We had that for 10 years on macOS forge and we now moved that same 
> system to our new server. Is it not working for you for some reason?

What I mean is that I do receive the emails being sent to you via my macports
handle mk, but I can’t send emails through smtp.macports.org or something like
that. I’d like to be able to send emails as well, not just receive them. What
am I missing here - in case the requested is also possible since 10 years?

Greets,
Marko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: How to handle MacPorts' handles in the future (including the email address connected to it)??

2016-11-02 Thread Ryan Schmidt 

> On Nov 1, 2016, at 3:17 PM, Marko Käning  wrote:
> 
> Hi Rainer,
> 
> On 01 Nov 2016, at 21:05 , Rainer Müller  wrote:
>> What do you mean by address rewriting? If you are referring to problems
>> with SPF,
> 
> I guess I do.
> 
> 
>> the new mail server is now doing SRS [1].
> 
> OK...
> 
> 
>> Right now we do not host any mailboxes with IMAP, we only forward mails
>> to existing addresses. I would like to keep the administrative overhead
>> low, certainly all developers have an existing mailbox.
> 
> Yeah, I understand that. I’d be happy enough with the rewriting approach.
> 
> 
>> Although I thought about implementing authenticated mail submission on
>> our mail server in order to be able to enable SPF for macports.org and
>> reduce spam. But that will not happen in the near future while there are
>> other issues.
> 
> So, what does it mean? Does the new server support it - as written above - or 
> doesn’t MacPorts support it?
> 
> You see me confused. ;)

I'm confused about why you're confused or what you're talking about.

We've always provided @macports.org email forwarding for committers. You tell 
us what handle you want, we set it up to forward to whatever email address you 
want. We had that for 10 years on macOS forge and we now moved that same system 
to our new server. Is it not working for you for some reason?


___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: How to handle MacPorts' handles in the future (including the email address connected to it)??

2016-11-01 Thread Marko Käning 
Hi Rainer,

On 01 Nov 2016, at 21:05 , Rainer Müller  wrote:
> What do you mean by address rewriting? If you are referring to problems
> with SPF,

I guess I do.


> the new mail server is now doing SRS [1].

OK...


> Right now we do not host any mailboxes with IMAP, we only forward mails
> to existing addresses. I would like to keep the administrative overhead
> low, certainly all developers have an existing mailbox.

Yeah, I understand that. I’d be happy enough with the rewriting approach.


> Although I thought about implementing authenticated mail submission on
> our mail server in order to be able to enable SPF for macports.org and
> reduce spam. But that will not happen in the near future while there are
> other issues.

So, what does it mean? Does the new server support it - as written above - or 
doesn’t MacPorts support it?

You see me confused. ;)

Marko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: How to handle MacPorts' handles in the future (including the email address connected to it)??

2016-11-01 Thread Rainer Müller 
On 2016-11-01 20:27, Marko Käning wrote:
> I’d actually be happier if I had my - up to now - MacPorts handle
> (mk) also for the future… :)
> 
> But ok, I guess I’ll have to apply at ad...@macports.org for a new
> handle then, being m...@macports.org, right?
> 
> The only problem with all this is, that I then have to ask my good
> old friend Brad (pixilla) to create that user mkae on his mail server
> (which can handle address rewriting).

What do you mean by address rewriting? If you are referring to problems
with SPF, the new mail server is now doing SRS [1].

> Well, as an alternative I could go through my own email provider, but
> they have special requirements for such address rewriting and I
> wonder whether at least those could be fulfilled by macports.org - in
> case it is absolutely impossible to get an email address at MacPorts’
> IMAP server directly.

Right now we do not host any mailboxes with IMAP, we only forward mails
to existing addresses. I would like to keep the administrative overhead
low, certainly all developers have an existing mailbox.

Although I thought about implementing authenticated mail submission on
our mail server in order to be able to enable SPF for macports.org and
reduce spam. But that will not happen in the near future while there are
other issues.

Rainer

[1] http://www.openspf.org/SRS
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev