Re: team alias and SPF
On 2017-04-18 00:04:07 (+0200), Benny Pedersen wrote: Philip Paeps skrev den 2017-04-17 19:49: On 2017-04-17 19:33:36 (+0200), Geert Stappers wrote: teamfoo: localcopy j...@example.com b...@domain.tld john@some.where Bob checks SPF on incoming messages. Bob should not be checking SPF from your mailserver if he knows there's a forward / expander there. the forwarding host ip can be added to spf whitelist in mta stage where spf is being breaked, doing so will in case of spamassaasin check spf for the real sender ips that is the originating ip Sure. That's a possibility. Checking SPF breaks email forwarding. incorrect since enveloper domain changes on the forward host Only if you take steps to change the envelope. In a normal/default setup, the envelope will not be changed. The easiest way to do this, is for Bob to check a list of forwarders in his ``smtpd_sender_restrictions`` if he's using Postfix. its not postfix job of make envelope sender fixses Correct. since spf is not dkim, or even sid-milter that breaks spf by checking from: header with breaks spf, i think most users see sender-id as a spf fail there in, but its not spf spf is maillists safe, so why say forwarding breaks spf ? SPF is only "safe" for mailing lists if the mailing list takes ownership of the message and remails it with a new envelope. SPF is not "safe" when you're simply forwarding the message (i.e.: without changing the envelope). If you check SPF, you need to whitelist every machine that forwards mail for you. Your backup MX for one. But also every other host that you know legitimately forwards mail for you. DKIM is completely unrelated. Philip -- Philip Paeps Senior Reality Engineer Ministry of Information
Re: Do you know an FOSS email system for kids?
On 4/15/2017 10:31 AM, Dedeco Balaco Baco wrote: in the last months, I have been searching for an email system with some features to make it better for kids, even for younger ages, and also their parents. We need a few features to guarantee some security to free messaging among known friends, but some supervision for unknown addresses. I have a system I wrote for my kids and nephews/nieces. It builds on top of mimedefang with mysql backend. I cannot share the UI for the database manipulations but can give you the database layout and example queries. It used a CMS on Apache that did the ability to whitelist/blacklist, etc. I can package up the snippets under GPLv2 and some documentation if that's a solution you are interested in pursuing. If you are interested in publishing it further, even if 3 people ever use it, I'll be more helpful as I like to surface code I've written for public benefit. Regards, KAM
mydomain and myhostname
Hello, I have here two different postfix installations, one is postfix 2.11.3-1 from Debian 8, the other is postfix 3.1.0-3 from Ubuntu 16.04. /etc/postfix/main.cf is the same on both machines, mydomain and myhostname are not set in main.cf . When I call postconf, I get mydomain = cs.uni-dortmund.de myhostname = cloudhost177.cs.uni-dortmund.de on the Debian machine, but mydomain = localdomain myhostname = cloudhost176.localdomain on the Ubuntu machine. What are the possible reasons for that? I cannot find out why the Debian postfix finds the domain information, but the Ubuntu postfix does not. Regards Christoph
Re: mydomain and myhostname
On 18 April 2017 at 16:35, Christoph Pleger wrote: > Hello, > > I have here two different postfix installations, one is postfix 2.11.3-1 > from Debian 8, the other is postfix 3.1.0-3 from Ubuntu 16.04. /etc/postfix/ > main.cf is the same on both machines, mydomain and myhostname are not set > in main.cf . When I call postconf, I get > > mydomain = cs.uni-dortmund.de > myhostname = cloudhost177.cs.uni-dortmund.de > > on the Debian machine, but > > mydomain = localdomain > myhostname = cloudhost176.localdomain > > on the Ubuntu machine. >From http://www.postfix.org/postconf.5.html#myhostname: the default [for myhostname] is to use the fully-qualified domain name (FQDN) from gethostname(), or to use the non-FQDN result from gethostname() and append ".$mydomain" - i.e. what you see when you type 'hostname' at the command line, which in turn is usually taken from the contents of /etc/hostname. And mydomain is by default derived from myhostname. If you update /etc/hostname you may also need to update /etc/hosts.
Re: mydomain and myhostname
Christoph Pleger: > Hello, > > I have here two different postfix installations, one is postfix 2.11.3-1 > from Debian 8, the other is postfix 3.1.0-3 from Ubuntu 16.04. > /etc/postfix/main.cf is the same on both machines, mydomain and > myhostname are not set in main.cf . When I call postconf, I get > > mydomain = cs.uni-dortmund.de > myhostname = cloudhost177.cs.uni-dortmund.de > > on the Debian machine, but > > mydomain = localdomain > myhostname = cloudhost176.localdomain > > on the Ubuntu machine. > > What are the possible reasons for that? I cannot find out why the Debian > postfix finds the domain information, but the Ubuntu postfix does not. 'localdomain' is the Postfix built-in default domain name when the machine name is not in 'host.domain' form. Wietse
Re: mydomain and myhostname
Hello, I have here two different postfix installations, one is postfix 2.11.3-1 from Debian 8, the other is postfix 3.1.0-3 from Ubuntu 16.04. /etc/postfix/ main.cf is the same on both machines, mydomain and myhostname are not set in main.cf . When I call postconf, I get mydomain = cs.uni-dortmund.de myhostname = cloudhost177.cs.uni-dortmund.de on the Debian machine, but mydomain = localdomain myhostname = cloudhost176.localdomain on the Ubuntu machine. From http://www.postfix.org/postconf.5.html#myhostname: the default [for myhostname] is to use the fully-qualified domain name (FQDN) from gethostname(), or to use the non-FQDN result from gethostname() and append ".$mydomain" - i.e. what you see when you type 'hostname' at the command line, which in turn is usually taken from the contents of /etc/hostname. And mydomain is by default derived from myhostname. If you update /etc/hostname you may also need to update /etc/hosts. The format of /etc/hostname and /etc/hosts is exactly the same on the two machines, only the actual values differ. /etc/hostname contains the non-FQDN name, /etc/hosts contains first the FQDN and then the non-FQDN. Regards Christoph
