Hi,
I have the following problem if I forward an email received from yahoo to
an other yahoo account the message is rejected.
If I send a message from yahoo -> my server and forwarded to a google
account the message is marked as spam, since is considered a spoofed.
Can I fixed this adding some hea
No.
SPF is designed to be secure, eg you cannot add some header to bypass the
authentication, then every phisher would add such a header.
What you need to do, is to rewrite the FROM adress or encapsulate the email.
Rewriting FROM adress can be as simple as rewriting yourn...@yahoo.com to
yourn..
Thank you very much for the fast reply.
I was looking on sieve or postfix and I do not find how I can do it.
Since I believe that will be the best way to do it.
Can you help me out?
Thank you
On Thu, Sep 17, 2015 at 1:51 PM, Sebastian Nielsen
wrote:
> No.
> SPF is designed to be secure, eg you
The best thing here is to set up a header filter that replaces first From:
header with your adress, and first To: header with the destination gmail adress.
To prevent that any spam blacklisted adresses appear, discard every to: and cc:
header after this.
Then you ensure the MAIL FROM in the SMTP
Thank you very much for the answer.
If I modified the headers the user it will not understand why it cannot
reply direct to the email.
I find strange that sieve do not have an option to encapsulate the email.
I will try to modify the headers in order to do some test.
Thank you very much to your f
Hi,
Last weekend one of our service provider for our application upgraded there
email server (Apache JAMES). And now, there telling us that the ORCPT variable
is not supported.
or mail bounces with this error:
Sep 15 00:35:40 devsys-prod-com-mta01 postfix/smtp[23429]: D01B34127C:
to=u...@prov
Jean-Francois Couture:
> Last weekend one of our service provider for our application
> upgraded there email server (Apache JAMES). And now, there telling
> us that the ORCPT variable is not supported.
SMTP servers that announce DSN support and reject ORCPT are BROKEN.
You can configure Postfix to
Sebastian Nielsen skrev den 2015-09-17 19:51:
Then you host a own SPF record.
no no no no and no
SPF is not From: body header
do you think about SenderID ?
sid-milter test both, SenderID is depricated with a replacement of DKIM
You have to setup SRS when forwarding.
On 2015/9/18 ζζδΊ 1:40, Il Neofita wrote:
Hi,
I have the following problem if I forward an email received from yahoo
to an other yahoo account the message is rejected.
If I send a message from yahoo -> my server and forwarded to a google
account the message
I have a brand new installation, from source, of Postfix 3.0.2 on
Debian 7, 64-bit. I successfully did the initial local tests for
postfix as described in "The Book of Postfix." (Note that I have
virtual servers but have not yet configured postfix for handling
them.) Then I made my first test fo
If the domain has strict identity alignment set up, then From: body must
match MAIL FROM, which must match the SPF record.
Thats why you need to replace or encapsulate the From: aswell, incase the
sender domain has strict identity aligment set up.
-Ursprungligt meddelande-
From: Benny
On 9/17/2015 9:17 PM, Tom Browder wrote:
> I have a brand new installation, from source, of Postfix 3.0.2 on
> Debian 7, 64-bit. I successfully did the initial local tests for
> postfix as described in "The Book of Postfix."
Please note the book is now rather dated. While the examples and
gen
On Thu, Sep 17, 2015 at 9:17 PM, Tom Browder wrote:
> I have a brand new installation, from source, of Postfix 3.0.2 on
> Debian 7, 64-bit. I successfully did the initial local tests for
> postfix as described in "The Book of Postfix." (Note that I have
> virtual servers but have not yet config
13 matches
Mail list logo
