New answers tagged

0

I think the encrypted function you wanted is not in the server side.it is during transfer to outside and for the email content. I suggest you to add a security e-mail gateway to realize this function.


0

For the recipient, identifiers stored in a domain name (your arbitrary choice) & identifiers stored in the mailbox name (also your arbitrary choice) are not that different, except in the former case you are causing some additional useless DNS traffic. So what if you send every mail from a unique subdomain? You gain nothing, but you lose some nuance, and ...


3

The destination domain has a malformed MX record. $ dig mx smart.com.ph ; <<>> DiG 9.11.4-P2-RedHat-9.11.4-26.P2.amzn2.4 <<>> mx smart.com.ph ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4883 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT ...


1

You can not reliably determine all software used by arbitrary recipients, but you can with some certainty attribute most - if you are able to connect‡ to the server and run some tests. The server name as published in the MX record alone usually includes no information whatsoever about the software used. Things that commonly help you guess: when connecting, ...


0

Port 25 is blocked in AWS. Try switching to another VPS. That is the only solution!


0

You may not have to do anything. Check your first_valid_uid and last_valid_uid settings - it limits which of the users you have configure in your user database are actually valid Dovecot users. For logging in and mail delivery, these settings work the way you want: You can keep your system users, and keep Dovecot configured for reading the system user ...


0

Is the Vultr instance one of the IPv6-only sandbox plans? If so, the lack of IPv4 might be the issue.


2

Find a ID of one of the mails in the queue with mailq Then check the headers to see how it was sent with postcat -q ID (where ID is the ID of the message). This way you can check wether the email is sent by a authenticated user or a rogue script. Delete all emails from that user in the queue with: mailq | tail -n +2 | awk 'BEGIN { RS = "" } # $7=...


3

To achieve DMARC compliance, either SPF or DKIM must be aligned. So I do not understand why you did get this forensic report - as far as I understand the DMARC system, this message is comliant, since DKIM passed the alignment test As far as I see, the message is DMARC compliant - normally you would not get a forensic report, but there is a setting that ...


0

I've managed to remove Received header by adding the following to /etc/exim4/exim4.conf.localmacros: REMOTE_SMTP_TRANSPORTS_HEADERS_REMOVE = Received With this setting, Exim4 no longer leaks my IP address to recipients.


2

Get the message ID and grep on it. For example, in the line below, the message ID is F05911DBCA. Apr 16 06:29:12 mail.xxx.com postfix/qmgr[25497]: F05911DBCA: removed So you can execute $ grep F05911DBCA /var/log/maillog It will list all postfix log lines about this message, so you can check all steps done by Postfix for this specific connection. Also, ...


0

Thanks for your reply. I am not sure if you got the idea of what I am trying to do here. This is the actual task: "Email servers are configured to block, log and report emails with inappropriate protective markings." "The intended recipients of any blocked inbound emails, and the sender of any blocked outbound emails, are notified." Build ...


3

It sounds you don't want to rely on a MTA at all, but want to handle everything within your own code. If that is the case, don't use postfix as the MTA... But I think that if you set bounce_queue_lifetime to 0 only a single delivery attempt will be made. It might be useful to create your own bounce_service_name to handle delivery failures instead of the ...


0

Like Bob said certain mail servers has a feature like "if user is not found on this server, route to another host". Might not be that hard to set up if it's not Exchange, some servers has it as a GUI option. But you'd need the option on both servers so internal email would route correctly.


Top 50 recent answers are included