Re: [exim] Forged FROM

2016-07-28 Thread Heiko Schlittermann
Yan Seiner (Do 28 Jul 2016 19:48:18 CEST): > Hi everyone: > > I'm not sure what, if anything can be done about my situation. One spambot > is forging my email address and IP in their FROM headers, so my email server > is getting hammered with bounces. … > I don't think there's

Re: [exim] Forged FROM

2016-07-28 Thread Always Learning
On Thu, 2016-07-28 at 13:48 -0400, Yan Seiner wrote: > One spambot is forging my email address and IP in their FROM headers, > so my email server is getting hammered with bounces. Are you using SPF ? -- Regards, Paul. England, EU. England's place is in the European Union. -- ##

Re: [exim] Forged FROM

2016-07-28 Thread Alan Hicks
Hi Yan, They take a while to implement, but you can let others know how you send mail with DMARC, SPF and DKIM. When the spammers get reduced hits they'll move onto someone else. https://en.wikipedia.org/wiki/DMARC https://en.wikipedia.org/wiki/Sender_Policy_Framework

Re: [exim] Forged FROM

2016-07-28 Thread Jeremy Harris
On 28/07/16 18:48, Yan Seiner wrote: > Hi everyone: > > I'm not sure what, if anything can be done about my situation. One > spambot is forging my email address and IP in their FROM headers, Actually the envelope from, not the headers from: > so my > email server is getting hammered with

[exim] Forged FROM

2016-07-28 Thread Yan Seiner
Hi everyone: I'm not sure what, if anything can be done about my situation. One spambot is forging my email address and IP in their FROM headers, so my email server is getting hammered with bounces. I've checked and I'm not running an open relay, and the emails are not originating with me

Re: [exim] 454 Error

2016-07-28 Thread Viktor Dukhovni
> On Jul 27, 2016, at 3:35 PM, John C Klensin wrote: > > Keep in > mind that a CNAME can point anywhere in the tree and that, in > the general case (the SMTP requirement that the > originally-specified domain appear in RCPT and that only final > names (no aliases) can appear

Re: [exim] 454 Error

2016-07-28 Thread Hardy
Hah! Is it some simple typo? You said > Uber users can initiate support tickets by replying to certain emails; the > replies go to some_unique_addr...@help.uber.com. But then > Result: 25: SMTP error from remote mail server after RCPT TO:< > test...@frontends.uber.com>: 454 4.7.1

Re: [exim] 454 Error

2016-07-28 Thread Hardy
On 27.07.2016 02:34, Mike Kadin wrote: [snip] Result: 25: SMTP error from remote mail server after RCPT TO:< test...@frontends.uber.com>: 454 4.7.1 : Relay access denied The sender (exim) does not have a problem, it seems working correctly, tries to forward the