Best way to set up a noreply address?

S

Strator

Verified User
Joined
Jan 19, 2011
Messages
274
I'm fed up with corporations sending me mail from noreply-addresses and would like to turn the tables, but it's not so easy. I thought setting up a forwarder and forwarding it to :fail: would be good enough, but then exim will not allow you to send. Any workarounds for that? Thanks!
 
Last edited:
So that's an SPF issue if I see correctly. I presume you do have MX records and SPF and a working other email address in place for the mydomain.com domain?
 
For workaround, just create as email account and config the sieve filter to automatics delete all incoming message.
 
Richard G said:
So that's an SPF issue if I see correctly. I presume you do have MX records and SPF and a working other email address in place for the mydomain.com domain?
Click to expand...
It works when I set up [email protected] to be forwarded to my normal email address ([email protected]). When I set it up to :fail: I am unable to send. Kinda feels like I'm a school boy who doesn't have the same privileges as adults - any stinky corporation can send me noreply messages all they want, and when I try to answer them, it turns out there's no account on the other end, but when I set up the same, it's against the "rules" (at least that's what I make of it).

Ohm J said:
For workaround, just create as email account and config the sieve filter to automatics delete all incoming message.
Click to expand...
I'm afraid that's not a workaround. I also have [email protected] where all replies disappear silently in my spam folder, but [email protected] needs to bounce so the sender knows, otherwise it's not a proper noreply-address.
 
Strator said:
When I set it up to :fail: I am unable to send.
Click to expand...
Yeaht that's odd indeed. That should normally work without issues if the forward to a normal address works. It's stated in the docs.
Just as a test, does it have the same issue if you use :blackhole: instead of the :fail: option?
If not, then I think this is indeed a bug.
 
Additionally, I would like to test for you but how does one send from a non existing mail address (as there is no smtp password)?
 
Richard G said:
Additionally, I would like to test for you but how does one send from a non existing mail address (as there is no smtp password)?
Click to expand...
Just set it up as an alias in your favorite mail program, set up the forwarder in DA and off you go.

:blackhole: works, only :fail: doesn't.

In the docs you quoted it says it has the same functionality as the catch-all E-mail options. These are:

Fail: The sender is notified that the address doesn't exist
Ignore: The email is droppend and completely ignored.

So judging from that, setting :fail: as a forwarder doesn't actually forward anything, but rather it emulates a non-existing account.
 
Strator said:
:blackhole: works, only :fail: doesn't.
Click to expand...
Ok then this is the same situation which is already present for years, at least 2020.
I've read at the Vimexx provider a question from a user which complaint it didn't work anymore in 2020 because he also got that verify error. So I was intrigued.
But the reply from another customer was it still worked, but he was using the blackhole option. So that's why I wondered if that would work.
Now we know this works, I don't have to test anymore.

Both the old and new docs state that also fail should work. But I can imagine in modern times an spf issue can occur for some reason. Still, since it's an option which should work imho it's still a bug, however a bug for some years already then. :)

@zEitEr any idea about this?
 
This issued might cause by jailshell. it's 4 year ago and I forgot it 😅
O

Post in thread 'BubbleWrap jail for PHP - mail issue'

@smtalk

everything is lastest version
exim_config => 4.5.30
jailshell_sh => 0.4

but when I have in Mail Forwarder like

[email protected] => :fail:
that I don't want to catch email from reply client or anything to inbound this mailbox.

It can't send email and got
Code: 
sendmail: recipient address [email protected] not accepted by the server
sendmail: server message: 550-Verification failed for <[email protected]>
sendmail: server message: 550 Sender verify failed
sendmail: could not send mail (account default from /home/admin/.msmtprc)

normally without jailshell call...
 
LawsHosting said:
If :fail: fails to generate a bounce, surely it's a bug.......... But the "old help site" does state it should work.
Click to expand...
I appreciate you trying to help, but you are confusing this thread by making false statements. :fail: does bounce, and it was never said otherwise - the problem is that, once you've configured a forwarder to :fail: exim will not allow you to use that mail as a sender.

Richard G said:
Both the old and new docs state that also fail should work.
Click to expand...
This might be a misunderstanding, unless I've overlooked something. It only says that the bounce will work but there's no word about sending, so it depends on the purpose. For example, if I retire a mail address and want others to know it doesn't work anymore by receiving a bounce, then :fail: behaves according to the docs. Unfortunately, that's not what I'm looking for, though.

Ohm J said:
This issued might cause by jailshell. it's 4 year ago and I forgot it 😅
O

Post in thread 'BubbleWrap jail for PHP - mail issue'

@smtalk

everything is lastest version
exim_config => 4.5.30
jailshell_sh => 0.4

but when I have in Mail Forwarder like

[email protected] => :fail:
that I don't want to catch email from reply client or anything to inbound this mailbox.

It can't send email and got
Code: 
sendmail: recipient address [email protected] not accepted by the server
sendmail: server message: 550-Verification failed for <[email protected]>
sendmail: server message: 550 Sender verify failed
sendmail: could not send mail (account default from /home/admin/.msmtprc)

normally without jailshell call...
Click to expand...
Looks exactly like my problem, except that I'm not aware I'm using jailshell, so probably I'm not (I only have a single instance of jailshell.sh that lives in /directadmin/configure).

But at the end of your thread, you are vowing to find a workaround because you couldn't use :fail: - so did you?
 
Ehhh, sorry... English is not my primary language, that's meant :fail: doesn't work, So I need to find workaround better than using :blackhole: .

so I just disable jailshell. Or using SMTP protocol instead of PHP mail() .
 
So, you want to send as a legit account but not receive to that account?.....

I just sent an email from a main email account but set the From field to no-reply@ (eg. anything), and it got sent and received—spf, dkim, etc passed too.

Not sure if this is what you want to do - if not, ignore this...... I'm misunderstanding & talking out of my backside...... as usual.
 
LawsHosting said:
So, you want to send as a legit account but not receive to that account?.....

I just sent an email from a main email account but set the From field to no-reply@ (eg. anything), and it got sent and received—spf, dkim, etc passed too.

Not sure if this is what you want to do - if not, ignore this...... I'm misunderstanding & talking out of my backside...... as usual.
Click to expand...
Things I've tried:

- Send from a non-existing mail address: It's the same as setting up the address to :fail: (which confirms that :fail: simply emulates a non-existing address). Sender verify failed.

- Sent from a different mail client to make sure Thunderbird isn't just being a PITA. Same result: Sender verify failed.

- Set noreply@ as the return address. Works but really looks stupid, because the recipient will see your regular address in the email field, and only when he hits reply will it switch to noreply@.

So I wonder what you're doing differently. Are you using regular exim installation as provided by DA/Custombuild?
 
Strator said:
So I wonder what you're doing differently. Are you using regular exim installation as provided by DA/Custombuild?
Click to expand...
Since I closed my business, using a VPS for personal stuff - with a mixture of Google Suite and the VPS for a mixture of accounts (important & non-inportant)...

Tested this on a server account........ Bog standard Exim SpamBlocker.conf except disabled IPv6 in /etc/exim.variables.conf.custom - I don't care for IPv6.... Besides, spf, dkim, etc are better on IPv4......

Are you using rDNS (PTR) properly on the IP?

If changing the From email isn't allowed (if I remember, this could be true), not sure my config allows it - the domain I tested from (to a Gmail address) has legit spf, dkim and dmarc records 🤷🏻‍♂️

I have add_domain_to_domainips=1 in DA's config, but doubt that makes a difference.
 
Last edited:
You must log in or register to reply here.
Back
Top