We use the hMailServer to forward incoming mails via distribution list.
The problem is that the recipient receives the mail with the address of the distribution list instead of the actual recipient address.
Is there a possibility that the recipient receives the mail with the real recipient address instead of the address of the distribution list. So that it appears to the recipient as if he had received the message directly and not via the distribution list.
Related
this is a pretty specific case, but it drives me crazy...
We recently migrated our email service to google workspace. We do have an invoice#mydomain.com address which earlier was configured to forward emails to someinbox#datev.com. someinbox is a mail upload feature for tax related invoices of our company. The problem started when i was trying to set up the mail filter in Gmail.
All emails with an attachment should be forwarded to someinbox#datev.com. To forward emails with Gmail, google needs to verify that I am allowed to forward to that specific address. It therefore now sends a confirmation email with a link to that address. that email is being sent by eg. noreply-forwarding#google.com, which is being rejected (550 5.7.1 Security policy violation: sender address not authorized). The problem is, datev only accepts emails from "verified sender addresses". It does that verification by also sending an email verification to that "verified sender address". Which in my case now becomes the noreply-forwarding#google.com, which I obviously not maintain and therefore i am unable to verify that address.
So I am unable to add the forwarding email address in Gmail, because of the sender google uses to verify the forwarding address.
We use google workspace, so I am able to use the pretty cool routing feature of Gmail. First I created an email-alias called datev#mydomain.com. I then setup a rule which simply changes the envelope-sender to someinbox#datev.com if the envelope-sender is datev#mydomain.com. that part works. If I send an email from the invoice#mydomain.com to datev#mydomain.com it changes datev#mydomain.com to someinbox#datev.com.
The next problem was, every forwarding (which the Gmail filter was doing) works by sending the same email to someinbox#datev.com while keeping the original sender. That also happened when I tried to do the same workaround by creating a new email forwarder (or even a mailbox) on a different domain without google workspace. I also tried it using posteo. The original sender is being used as the sender address and therefore datev rejects it. It wouldn't be possible to register all sender address as we get a lot of invoices from business partners.
Does anybody know or see a way of doing this? Aren't there any secure email forwarder which replace the sender address to the one of the forwarder instead of keeping the original one? I know, this is in most cases a pretty nice feature as you can see who the email originally sent, in my case it makes me nuts.
I was looking for the email address of a few profiles on GitHub and came across the no-reply email IDs. I know that these email IDs are created to make our personal email private, but I was wondering what happens if we mail to that no-reply address, I tried to mail me with my friend's email account and didn't receive any error neither did I receive the mail in my inbox. So what happened to that mail?
If you try to send mail to that domain, it will be returned as undeliverable.
In order to send mail to a domain, that domain must have either one or more MX records that provide the names of hosts to which mail can be delivered, or one or more A or AAAA records pointing to hosts which have a mail server running. In this case, users.noreply.github.com has no MX records, and it is a CNAME for github.github.io, which points to hosts which do not run a mail server.
When you attempt to send a mail to a server and it can't be delivered immediately, it is usually queued by your mail server, and if it remains undeliverable after some time (by default five days), it will bounce. Normally, you will receive a bounce message from your mail server indicating that the mail wasn't able to be delivered.
The point of those addresses is to allow users to attribute their commits to the correct account without having to receive emails. It wouldn't be very useful to prevent people from sending spam (or, in some cases, hostile or abusive emails) if the addresses weren't totally undeliverable.
I have multiple domains which I receive e-mail for and have set up my mailserver to deliver it all to a single mailbox for convenience, example below:
comment#myblog.com
contact#mybusiness.com
admin#mywebsite.com
They all come to me at my single mailbox:
ian#me.com
When I reply to these e-mails the reply-to address will be:
ian#me.com
I would like to automatically have postfix change that reply-to address, based on the address that the e-mail was originally sent to, so for example:
Email is sent to me at: comment#myblog.com
I reply from: ian#me.com
I want the reply-to to be: comment#myblog.com
Is there a way to automate this with postfix?
Thanks in advance.
It is doable in postfix anyway. But it requires some programming to parse the mail to determine the recipient email address and add Reply-To header from that value. You need to use an external content filter or a Milter application. But I dont think it is a cleaner way.
I would rather say that setting Reply-To header should be done by the MUA eg. (Thunderbird, Outlook etc ) instead of Postfix MTA. For eg. in Thunderbird, If you receive all your emails for
comment#myblog.com
contact#mybusiness.com
admin#mywebsite.com
at ian#me.com, then you can add identities for all the email addresses above( You can set your Name, Email address, Reply-To address etc). So when you reply to an email sent to comment#myblog.com, then the Reply-To address will be set to comment#myblog.com. For Thunderbird, you have to add identities by clicking Edit -> Account Settings -> Manage Identities. More info here. All MUAs should have this option of managing identities.
Hope that helps.
How can I delete the: old_mail_address#domain.com and move to new_mail_address#domain.com in cPanel?
So that when a user sends an email to the old_mail_address#domain.com it will be directly forwarded to new_mail_address#domain.com and there's no error while sending that mail.
To solved it, I just create new mail address with new domain name and then forward message to the new mail address.
Example:
Old mail address : manellen#old-address.com
Create New mail address : manellen#new-address.com
Forward messages from old mail address to new mail address
From this case, we can see that one user has two mail address that is old mail address and new mail address. My reason about that is to avoid failed send messages or people can't send message to old mail address then I'm not delete the old mail address.
We are having a system that sends mail on behalf of the user (the user provide his own mail address).
The mails are send via our server and are set up to with our company mail address as From (as many of our clients have disallowed third party to send mails withe their address as From) and with the users mail address in the Reply-to.
Is it true that bounce mails are going to the Reply-to address rather than to the "From" address.
No, bounces will go to the reverse-path address in the SMTP envelope, which is usually (if you did not specify otherwise) the same as the From address supplied in the mail headers. Because you (correctly) use your company address as a reverse-path, bounces will be sent to your company. See Sender Rewriting Scheme for an example how it is possible to send bounces to the original user.