1 to 2 of 2
We have been forced to add rules to our anti spam filters not to allow e-mails to come into our organization from and external source with the sender being from our domain. Example I am fred and my E-mail is firstname.lastname@example.org in intervals I setup a task for someone but the e-mail is blocked by out spam filter because it sees it coming from email@example.com from an external source.Any way to have Intervals send the e-mail with a from address of firstname.lastname@example.org or something like this?
You can't change that (although please request it using the 'feature request?' link in intervals), but intervals does set the correct headers so the emails shouldn't be being caught by your spam filter.With your example, the headers sent would include:From: "Fred" <email@example.com>X-Sender: "Intervals" <firstname.lastname@example.org>Sender: "Intervals" <email@example.com>Where a "Sender" header is specified, your spam filters should be looking at that to identify the source of the email, not the "From" header, which is just a human-readable label.Intervals also has domain keys which can be used to verify the email:DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=myintervals.com; h= mime-version:content-type:from:sender:to:subject:message-id :date; s=mx; bh=WUbyyhjWaKR0lB0W28y7WfRW7qU=; b=Y9BBwHT8w9XVzVoF yeLqSgGAcN+3ixMW6gep8pZe8QQUWCi55u8m0eXyMMlb9qAX/udVaKSdBX4lc/2W imRHfg==DomainKey-Signature: a=rsa-sha1; c=nofws; d=myintervals.com; h= mime-version:content-type:from:sender:to:subject:message-id :date; q=dns; s=mx; b=qlDVke71C0bv2zE1mSf3ZzS7XPzyqLc95YJlLnEYnD 7I8ICHXPLf/+wBVUxzz1ihBJBFIK/av/ESzJ324h3C3Q==
Comments are closed.For more Intervals help documentation, please visit help.myintervals.com