Oops

Am 2013-06-10 08:43, schrieb Timo Röhling: Am 2013-06-10 07:13, schrieb j...@soe.se: I have written a small policy service. But I whish to not use it for those emails which are rejected. Only permited emails (permit_mynetworks and permit_sasl_authenticated) Any ideas

Re: check_policy_service not for rejected?

Am 2013-06-10 07:13, schrieb j...@soe.se: I have written a small policy service. But I whish to not use it for those emails which are rejected. Only permited emails (permit_mynetworks and permit_sasl_authenticated) Any ideas? smtpd_recipient_restrictions = check_policy_service unix:private/po

Re: 'reject_non_fqdn_helo_hostname' not working?!

Am 2013-06-07 15:16, schrieb Nikolas Kallis: I thought for a domain to be fully qualified, it must have a PTR record setup for it? No, fully qualified means that all domain name components up to the top level domain are specified. While you can generally expect that fully qualified domain name

Re: Postfix, Autoreply

Am 20.05.2013 23:34, schrieb motty cruz: > less /usr/local/auto/autoreply > > #!/bin/sh > From:mo...@mydomain.com > To:$1 > Subject:Vacation > Content-Type:text/plain; charset=utf-8 > > This is an autoreponder email. >

Re: postscreen and Google

Am 2013-05-13 13:12, schrieb LuKreme: Other than disabling postscreen which I’m not going to do, is there anything I can do to whitelist all the google.com domains? Google recommends their SPF entries: http://support.google.com/a/bin/answer.py?hl=en&hlrm=de&answer=60764 You could create an auto

Re: Routing Control of locally generated bounces in Postfix

Am 2013-04-19 12:28, schrieb nullnullachtfuenfz...@arcor.de: The problem arises with mail originating from senders in @B2.example.com to recipients in @A1.example.com. Because the destination server in A also does a smtpd_sender_restrictions=reject_unknown_sender_domain and @B2.example.com is unk

Re: sender_canonical_maps does not work since I've installed amavisd-new + clamav + spamassassin

Am 2013-04-17 10:00, schrieb Frank Bonnet: -o local_header_rewrite_clients= http://www.postfix.org/ADDRESS_REWRITING_README.html: NOTE: Postfix versions 2.2 and later rewrite message headers from remote SMTP clients only if the client matches the local_header_rewrite_clients parameter,

Re: Scheduling policies for outgoing smtp server

Am 2013-04-05 12:36, schrieb Giorgio Luchi: - User A [...] sends 1 different email to 1 million of different domain destinations [...] - User B [...] sends an email to a different more domain destinatio Doesn't this scream for two different postfix instances? - One high priority instance with

Re: SMTPS 465

Am 2013-04-15 07:27 schrieb Stan Hoeppner: We've been told that this kernel upgrade created the problem. Simply reverting to the previous kernel should fix it. I wager the OP upgraded more than just the kernel, or upgraded the kernel in-place, Russian Roulette style. ;) The lesson learned is th

Re: Deferred mail

Am 17.01.2013 06:20, schrieb Muzaffer: > Jan 17 06:14:20 ommuse postfix/smtp[25504]: BC05AF629A: > to=mailto:sertacona...@gmail.com>>, relay=none, > delay=116212, delays=116107/0.02/105/0, dsn=4.4.1, status=deferred > (connect to alt4.gmail-smtp-in.l.google.com >

postsrsd: new sender rewriting scheme daemon

Hello list, I am developing a daemon to handle the sender rewriting scheme (SRS) with Postfix. SRS can be added to Postfix via {sender,recipient}_canonical_maps. The concept is very similar to Fruneau's postfix tools. I wrote the daemon for my own mail server (and I've been running it for a