Tag Info

Hot answers tagged

25

You can absolutely see in the postfix logs where an email was sent, and whether it was accepted. Here's an example log entry from my mail server which indicates that the message was successfully sent to the Google SMTP servers. Dec 15 14:21:43 ebony postfix/smtp[2422]: D05BB1D872: to=, relay=gmail-smtp-in.l.google.com[74.125.201.27]:25, delay=1.4, ...


6

Depends. EDIT 1 (Because my first answer was snarky and bad) This is entirely dependent on all sending servers' preferences. If the sending server that connects to your server is set to... ...first connect with TLS over port 465 but die on an expired certificate, then yes you're toast. ...first connect with TLS over port 465 but be okay with an expired ...


5

No, you won't be able to check this. Email is a "best-effort" service. There are no guarantees that any given email will actually be delivered. Usually you will get a notification that delivery has been delayed, but that depends on the email software between you and the recipient. You can check your mail server's log to verify that it got sent, but ...


4

There is "Delivery Status Notification" aka DSN - MTA send a little message to the submitter when LDA occurs. But as far as that functionality has been used by spammers, postmasters turns it off. Some modern MTA like exim doesn't have it at all. From the logs you can know that message from your MTA has been passed to another MTA, but you can't estimate that ...


4

IIRC the PHP mail function on Linux typically defaults to using the sendmail command. Sendmail (or any local replacement SMTP server) needs not be explicitly configured nor be running as a daemon to work. For your messages to delivered reliably though, configuring and running sendmail (or replacement) in daemon mode is probably recommended. For instance ...


3

Please check the free script written by the firm where one of the highly qualified folks at Security SE works: https://labs.portcullis.co.uk/tools/ssl-cipher-suite-enum/ ssl-cipher-suite-enum identifies the following common security issues relating to SSL: ...Support of key exchange algorithms that don’t support forward secrecy – or equivalently, cipher ...


3

Postfix refused relay to mydomain.com because isn't listed as local or virtual domain. The first step is define the domain class (postfix.org/ADDRESS_CLASS_README.html). myhostname is the machine name. mydestination is a list with domains hosted and users listed on passwd.


2

Your postfix smtpd process is complaining with a: <us.er@mydomain.com>: Relay access denied because: mydomain.com is not configured/recognized as a local final destination; and postfix is not configured to relay messages to an external mydomain.com domain; So, being unable to deliver both localy (as for point 1) and remotely (as for point ...


2

Launch doveconf -a | grep _valid_ You have to set that variables to something like that: first_valid_uid = 26 last_valid_uid = 0 first_valid_gid = 6 last_valid_gid = 0


2

Delivery Reputation: Would using php mail() vs SMTP make any difference with the delivery rate? From what I understand, Postfix is going to be using SMTP protocol when communicating with other servers on the internet when delivering emails, so therefore is it safe to assume that it doesnt matter if the email was sent to postfix via php mail or smpt from ...


2

In many cases, the spamming scripts are uploaded by an automated process after an automated scanner finds a vulnerability in your webapp. Those spam scripts almost always use php mail() function and not SMTP. If someone was to hack into your server and grab smtp passwords from config file, then you have lost the castle anyway. But in a lot of automated ...


2

Solution - Postfix version 2.7 or above required: /etc/postfix/master.cf #smtp inet n - n - - smtpd 127.0.0.1:smtp inet n - n - - smtpd -o syslog_name=postfix-localhost -o smtp_helo_name=localhost -o smtp_bind_address=127.0.0.1 -o myhostname=localhost ...


2

Change your config-file with SQL-query like that: . . . . . password_query= SELECT username as user, \ password \ FROM mailbox \ WHERE username = '%n@%d' \ AND active=1 user_query = SELECT maildir AS userdb_home, \ 150 AS userdb_uid, \ ...


2

If you don't have access to the logs of the server you used, you can't prove it for that particular message. Normally, you do get an error message back in case of failure, unless the server thinks it's spam and just discards it. If the server is unreachable, the sending server will keep trying for a couple of days. You'll get a deferred notice after a few ...


1

You're probably not sharing the same mailbox location/folder and/or mailbox delivery style (MBOX vs. MDIR) in both Postfix and Dovecot. As a result, Postfix is (correctly) writing under "/home/mailuser/Maildir" (where you see your mail arriving, under the "new" subfolder), but as dovecot is searching somewhere else... it doesn't find such mails (so you get a ...


1

I got it working 100% I considered deleting this questions since it had no comments or answers but after spending nearly 8 hours on setting up this mail server...I just couldn't do it as this might very well help others searching for the answer to this problem. My searches revealed that many people have had this problem and there isn't many answers to it! ...


1

The benefit of this is to know that if I choose to disable some specific cipher, which clients is it likely to affect, just like the SSL labs tests show for web clients. You don't need to restrict yourself to a specific cipher, but instead simply enable all ciphers which are acceptable to you and in the order you prefer them. The resulting cipher then ...


1

Every email received by postfix always be passed to milter. So you shouldn't have worry about it. To do rewriting, you can use recipient_canonical_maps here. In main.cf add this parameter recipient_canonical_maps = hash:/etc/postfix/process2main And in /etc/postfix/process2main add this line me@process.example.com me@example.com This will rewrite ...


1

Disclaimer: I'm assuming that you only want to parsing email with mailin and the email won't to delivered to dovecot again. To do that, replace the virtual_transport parameter so it becomes virtual_transport = smtp:[127.0.0.1]:10025 That's it, instead delivering it to dovecot, postfix will pass the email to mailin via SMTP port 10025. [UPDATE] Based ...


1

Setup another server and have it receive mail for backup.domain.name. Create all accounts both on the regular server and the backup server. Add individual entries for accounts to the sender and recipient bcc maps. sender_bcc_maps = hash:/etc/postfix/bcc_maps recipient_bcc_maps = hash:/etc/postfix/bcc_maps /etc/postfix/bcc_maps account1@example.com ...


1

Binding problem Command netstat returns tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 14774/sendmail: MTA If you want to use postfix, please uninstall/stop sendmail. sudo apt-get remove sendmail Then restart postfix sudo service postfix restart Email bounce problem This line Dec 8 19:07:27 ns3268116 postfix/smtp[11051]: A84F8120023: to=, ...



Only top voted, non community-wiki answers of a minimum length are eligible