Do you mean the log, to whom mail were sent? On local Postfix it would be /var/log/mail.log.
If you mean the full content of every mail sent to a specific mailbox, check for bcc maps in http://www.postfix.org/postconf.5.html - again Postfix specific.
Visvanath Ratnaweera
Posts made by Visvanath Ratnaweera
Moodle in English -> Hardware and performance -> Help! Database server CPU maxed out -> Re: Help! Database server CPU maxed out
by Visvanath Ratnaweera -
Noted that Ken is talking about NFS and you about a "shared NTFS mount". Is that a typo?
Moodle in English -> Installing and upgrading help -> upgrade issue from 3.5 to 3.7 - Table "message_conversations" does not exist -> Re: upgrade issue from 3.5 to 3.7 - Table "message_conversations" does not exist
by Visvanath Ratnaweera -
Increase the https://docs.moodle.org/37/en/Debugging level to maximum and get detailed error messages.
Moodle in English -> Installing and upgrading help -> SMTP connect error with Gmail after upgrade to 3.7 -> Re: SMTP connect error with Gmail after upgrade to 3.7
by Visvanath Ratnaweera -
Hi Emma
Good point about the parallel SMTP connections in Moodle 3.7. Haven't experienced that, I am still at 3.5. I thought I've seen suggestions on moodle.org exactly to this effect, to break up mail load in to sessions, since the MXs on the receiving end (hotmail.com, yahoo.com. etc) do not like a big load of mails in one go. Apparently Gmail behaves differently.
I run all three combinations of SMTP with Moodle. If you want to go Postfix on localhost, it is unbelievably simple. On Debian flavours of Linux, get do 'apt-get install postfix', tell the installtion script that yours is a site on the Internet. Then go through /etc/postfix/main.cf. Likely you need to focus on myorigin, myhostname and mydestination only. Restart the service. That is all on the Postfix side.
Getting the mail accepted by everybody is a longer story. The first step is to add the IP address of your serve to the TXT record of your domain in the DNS. See https://en.wikipedia.org/wiki/Sender_Policy_Framework#Implementation. Then carefully follow the SPAM warnings of the MXs. Improving the SPF record and/or progressing to DKIMhttps://en.wikipedia.org/wiki/DomainKeys_Identified_Mail, and further as necessary.
Good point about the parallel SMTP connections in Moodle 3.7. Haven't experienced that, I am still at 3.5. I thought I've seen suggestions on moodle.org exactly to this effect, to break up mail load in to sessions, since the MXs on the receiving end (hotmail.com, yahoo.com. etc) do not like a big load of mails in one go. Apparently Gmail behaves differently.
I run all three combinations of SMTP with Moodle. If you want to go Postfix on localhost, it is unbelievably simple. On Debian flavours of Linux, get do 'apt-get install postfix', tell the installtion script that yours is a site on the Internet. Then go through /etc/postfix/main.cf. Likely you need to focus on myorigin, myhostname and mydestination only. Restart the service. That is all on the Postfix side.
Getting the mail accepted by everybody is a longer story. The first step is to add the IP address of your serve to the TXT record of your domain in the DNS. See https://en.wikipedia.org/wiki/Sender_Policy_Framework#Implementation. Then carefully follow the SPAM warnings of the MXs. Improving the SPF record and/or progressing to DKIMhttps://en.wikipedia.org/wiki/DomainKeys_Identified_Mail, and further as necessary.
Moodle in English -> Installing and upgrading help -> SMTP connect error with Gmail after upgrade to 3.7 -> Re: SMTP connect error with Gmail after upgrade to 3.7
by Visvanath Ratnaweera -
Hi Emma
The answer is simple: Either you are dependent (on Google) or you are independent. You can't change Google, if it says no, then it is no!
You become independent by either a) running your own SMTP, the "phpmail" you mentioned, or b) sending mail via the SMTP server of your institution, or c) by taking the service of a commercial (authenticated) SMTP relay. As you have already experienced they don't have the bulk mail problem, if they complain you can always raise the limit. The (unavoidable) down side is, you have to get your mailer white listed, starting with a SPF record for your SMTP server.
The answer is simple: Either you are dependent (on Google) or you are independent. You can't change Google, if it says no, then it is no!
You become independent by either a) running your own SMTP, the "phpmail" you mentioned, or b) sending mail via the SMTP server of your institution, or c) by taking the service of a commercial (authenticated) SMTP relay. As you have already experienced they don't have the bulk mail problem, if they complain you can always raise the limit. The (unavoidable) down side is, you have to get your mailer white listed, starting with a SPF record for your SMTP server.