How Do I Configure Spamfilter Whitelist with Wildcard Sub-domains?

Discussion in 'Technical' started by rwheindl, Jan 26, 2018.

  1. rwheindl

    rwheindl Member

    I've recently purchased an updated copy of the ISPConfig 3 manual, however it does not include examples of white-listing random sub-domains. We have a situation where the content filter is blocking the LinkedIn signup automated verification emails. Here's an excerpt:
    Code:
    Jan 24 22:46:43 g1s2 postfix/smtpd[26615]: NOQUEUE: filter: RCPT from maila-de.linkedin.com[108.174.6.141]: <[email protected]e.linkedin.com>: Sender address triggers FILTER amavis:[127.0.0.1]:10026; from=<[email protected]e.linkedin.com> to=<[email protected]> proto=ESMTP helo=<maila-de.linkedin.com>
    Jan 24 22:46:44 g1s2 postfix/cleanup[26708]: 048F520B3E7A: reject: header Message-ID: <[email protected]linkedin.com> from maila-de.linkedin.com[108.174.6.141]; from=<[email protected]e.linkedin.com> to=<[email protected]> proto=ESMTP helo=<maila-de.linkedin.com>: 5.7.1 message content rejected
    Jan 24 22:50:01 g1s2 postfix/smtpd[26821]: NOQUEUE: filter: RCPT from maila-af.linkedin.com[108.174.3.134]: <[email protected]e.linkedin.com>: Sender address triggers FILTER amavis:[127.0.0.1]:10026; from=<[email protected]e.linkedin.com> to=<[email protected]> proto=ESMTP helo=<maila-af.linkedin.com>
    Jan 24 22:50:02 g1s2 postfix/cleanup[27061]: 144782022D28: reject: header Message-ID: <1216961161.778[email protected]> from maila-af.linkedin.com[108.174.3.134]; from=<[email protected]e.linkedin.com> to=<[email protected]> proto=ESMTP helo=<maila-af.linkedin.com>: 5.7.1 message content rejected
    Jan 24 22:50:28 g1s2 postfix/smtpd[26645]: NOQUEUE: filter: RCPT from maila-ac.linkedin.com[108.174.3.131]: <[email protected]e.linkedin.com>: Sender address triggers FILTER amavis:[127.0.0.1]:10026; from=<[email protected]e.linkedin.com> to=<[email protected]> proto=ESMTP helo=<maila-ac.linkedin.com>
    Jan 24 22:50:29 g1s2 postfix/cleanup[27061]: 0ECFA2022D28: reject: header Message-ID: <[email protected]linkedin.com> from maila-ac.linkedin.com[108.174.3.131]; from=<[email protected]e.linkedin.com> to=<[email protected]> proto=ESMTP helo=<maila-ac.linkedin.com>: 5.7.1 message content rejected
    Jan 25 07:04:56 g1s2 postfix/smtpd[22443]: NOQUEUE: filter: RCPT from maile-ab.linkedin.com[108.174.3.194]: <[email protected]e.linkedin.com>: Sender address triggers FILTER amavis:[127.0.0.1]:10026; from=<[email protected]e.linkedin.com> to=<[email protected]> proto=ESMTP helo=<maile-ab.linkedin.com>
    Jan 25 07:04:56 g1s2 postfix/cleanup[23251]: C4CB4201D43E: reject: header Message-ID: <[email protected]inkedin.com> from maile-ab.linkedin.com[108.174.3.194]; from=<[email protected]e.linkedin.com> to=<[email protected]> proto=ESMTP helo=<maile-ab.linkedin.com>: 5.7.1 message content rejected
    Notice, the sending server changes each time. I've tried adding @linkedin.com as suggested in the manual but these errors continue. Will that field accept @*.linkedin.com for the wild-card sending server names? It's not mentioned in the manual how to correct this in the filter... Thanks for the help!
     
  2. rwheindl

    rwheindl Member

    I found the problem. There was a file called: /etc/postfix/header_checks with a bunch of stuff in it. (I think I had been experimenting previously and forgot to clear it.) Clearing the list from that file allowed the confirmation emails to come through the filter.
     

Share This Page