Recent content by larsen

I have now configured our systems (JIRA, etc.) to use PMG as the mail server. It was only necessary to add those servers' IPs at "PMG > Configuration > Mail Proxy > Networks". Other servers where there was no specific service, I configured Postfix to use "relayhost". Mails from our domain...

The bug report now has a patch that makes it possible to use "/var/log/mail.log*".

I have setup DKIM so that mails from our internal network that are sent over PMG get a signature. Now I wonder what to do with our external servers, e.g. JIRA or Gitlab. Those currently send mails via a smarthost but could be switched to using the local Postfix on each server. One option...

Thanks for the info! I don't need it that often. We just recently started using PMG, so there will probably be less and less need for such things.

When I run postmap -q jondoe@example.com btree:/var/lib/postfix/verify_cache this often takes up to 15 minutes or more until I get a result. The next second, it returns instantly. I checked this with strace and noticed that it's waiting for a read lock for the "verify_cache.db"...

Thanks!

Ah ok. The sending domain doesn't have any SPF record, so this would be the culprit?

I can see that a mail got greylisted, then delivered from the same host/ip some minutes later: Oct 13 12:00:54 gateway postfix/smtpd[146215]: connect from mail1.bemta26.messagelabs.com[85.158.142.4] Oct 13 12:00:55 gateway postfix/smtpd[146215]: NOQUEUE: reject: RCPT from...

@aaron: Any idea?

Ah ok, that's good. We already use SPF checks. However, I just checked the corresponding SPF record, so now I wonder "shouldn't this have not been greylisted"? dig +short txt nets1.spf.messagelabs.com nets2.spf.messagelabs.com | grep 195.245.230 "v=spf1 ip4:85.158.136.0/21 ip4:193.109.254.0/23...

As far as I understand the documentation, the whitelist (Configuration > Mail Proxy) only applies to MAIL FROM. As we use greylisting, I would like to whitelist known servers like this with a regex "mail[0-9].bemta[0-9][0-9].messagelabs.com" NOQUEUE: reject: RCPT from...

I would suspect it's "Greylisted and never returned".

I was wrong. I just found out that I indeed edited the file (via puppet) to change the name PMG sends mail under. Have changed "myhostname" to "pmg.example.com" now. The spam report gets delivered. Interestingly, the spam report comes from "postmaster@example.com" although "myorigin =...

I noticed that some spam reports bounce, while others do not: Oct 7 00:05:15 pmg postfix/local[247078]: 8D03AC11D3: to=<j.doe@example.com>, relay=local, delay=0.1, delays=0.07/0/0/0.02, dsn=5.1.1, status=bounced (unknown user: "j.doe") Oct 7 00:05:15 pmg postfix/smtp[247081]: C5DA2C1361...

I suspect it's stored in PMGs postgresql database (just guessing).