Forward from non gmail account

It can come from a non-gmail account, as long as it's a Google Account (in fact my Google Account isn't a gmail.com email). You can't play Ingress without a Google Account, so allowing forwarding from accounts that can't be used for Ingress seems a little silly.

There *are* some restrictions on forwarding emails though. I'm not familiar with sieve, so I'm not sure what it's doing internally to the emails. Forwarded emails must remain 100% intact as they were sent from Niantic (the system uses DKIM to verify that the origin of the email was from Niantic and that the email itself was not changed in any way). This is to prevent malicious attempts to feed in incorrect/fake data.

So long story short is that if your system is forwarding emails in a 100% unaltered form, it should work. If it alters the email in any way, it will not work.

 

I don't know anything about Lampje, so no idea if it performs validation of email integrity. I suppose you could try forwarding them from sieve to your Gmail account and then set up a normal email forward filter rule from there. I've seen a few people do that and then the emails seem to forward along into Outgress just fine. Might at least be worth trying.

 

The only email address that Outgress cares about is the email address in the "To:" header within emails Ingress sends you. If that's a gmail.com address, they would need to be forwarded from Gmail.

If it's a non-Gmail address, you would forward from that server, but it working is going to be dependent on how that server works. If emails are altered in anyway from the original, they are ignored.

 

I'd say the first thing to do would be to decide if this site brings anything of value to you. If not, the rest is all moot and definitely not worth setting up a forwarding rule regardless.


A-C isn't going to work because then the email is in an altered state and will be ignored if it comes in to the Outgress servers:

In order for emails to be processed, they must adhere to both of these criteria:

• In must have been generated by Niantic servers
• It must not have been edited in any way

Allowing emails that originated from non-Niantic servers or email damage reports that have been altered from how they were originally from Niantic really would just open the system up to people feeding in fake/false/incorrect data.

Those are the most important criteria... there are some secondary requirements as well such as the incoming email must come over a SMTP TLS (secure) connection.

If your email damage reports are being sent to a gmail.com address and then forwarded along to an external email, the simplest solution I would think would be to create a normal forwarding email filter on that Gmail account for just the email damage reports. I believe you can have multiple forwarding filters defined (forwarded to multiple places).

 

You don't need a gmail.com email address, just a Google Account (which you also need for Ingress). If you don't have a Google Account, the site definitely will have no value to you because it's related to Ingress.

Personally, my email isn't a gmail.com address either, but I know how to set up forwarding on the email platform I use, so it works fine.

There aren't instructions for setting up forwarding for non-Gmail addresses because there are an infinite number of possible email platforms one could be using, all with different forwarding instructions (and some might not allow forwarding at all). The Gmail forwarding instructions cover 99% of users who have Google Accounts with a gmail.com address tied to it. For the other 1% of us, the forwarding setup is going to be dependent on your email platform and it's ability to forward emails in an unaltered fashion.

The criteria for forwarded emails to work (regardless if it's a gmail.com address or not) is as follows:

• Email must have been generated by a Niantic server
• Email must not have been edited in any way (for example if your forwarding mechanism even adds "Fwd:" to the subject, it's now altered and invalid). The ability to check if an email has been altered is just a yes/no flag, it's not granular enough to tell *what* has been altered... only that it was (or was not) altered.
• The email server must transmit emails over a secure (TLS) connection.

Gmail is able to forward emails in a secure fashion without altering the original emails, which is why it works for gmail.com addresses. It's not that they are a gmail.com address, rather that the Gmail servers don't attempt to alter the email when forwarding.

Also, for the system to know which emails are yours, the address Ninatic sends your email damage reports to (the "To" header in the email), must match the email you use for your account on this site.

 

I've never tried to set up forward on an email client. Truth be told, I haven't used email in about 8 years (at least not where if you send me something, I would see it... I don't check the email account I have actively). I use email for things like Outgress or when you have to click a link to verify a new account somewhere, I'll go and grep the mail I have for the link.

There are a whole lot of possibilities, in my case, I have a Google Account that *actually* has no gmail.com email address tied to it.

If I open my Ingress game and look on the Device tab, it's not a gmail.com address shown (really only important in the context of Outgress because the "To:" header in email damage reports is not a gmail.com address).



Myself, I do it with server-side forwarding when it comes in. There is no client "checking" an email box and performing an action or anything like that.

You can call it whatever you want... Sendmail, Postfix, Qmail, etc. call it a forward. If an email client calls the same thing something different, that's fine too. Regardless of what the forwarding mechanism calls it, the requirements for Outgress is that the original (unaltered) email be sent to the Outgress mail servers. I suspect that most client-side forwarding is *probably* going to fail. I haven't tested it, but I know if the email is altered in any way it will fail (so if they do something like quote the email or alter the subject it has been altered, it's not going to work).

Additionally doing client-side forwarding is going to make your Outgress alerts borderline useless because of lag since a client is typically going to poll for new mail on a regular basis. Server-side forwarding is going to forward it the instant the mail server receives it. And the mail servers on Outgress' side don't deliver incoming email to a mailbox that needs to be checked (incoming mail is delivered to the application directly).

The bottom line is that regardless of what you call it or how you do it, the technical requirements for Outgress to receive and process incoming email damage reports is here: https://outgress.com/threads/forward-from-non-gmail-account.61/#post-380

 

It's Postfix 2.11, nothing was changed to how it works as far as doing forwards... it's a pretty vanilla setup in that regard.

Besides needing to be able to forward emails unaltered, it needs to be able to communicate over an SMTP TLS (secure) connection.

Postfix forwarding is basically editing the /etc/postfix/virtual file (or wherever you have it), rebuilding the lookup table with postmap command, and then reloading the daemon process so it reads your new settings.

 

If they come in completely unaltered, it will work fine. I can't check without knowing something about who it is (like their agent name).