Am 17.02.2012 18:41, schrieb Toni Mueller: > > On Fri, Feb 17, 2012 at 06:35:11PM +0100, Reindl Harald wrote: >> Am 17.02.2012 18:31, schrieb Simon Hintermann: >>> SENDER ([email protected]) sends an email to [email protected] >>> || >>> v >>> WEBSERVER ([email protected] forwards all mails to [email protected]) >>> || >>> v >>> MAIL GATEWAY (local domains: domain.com) sees a mail with a "From: >>> [email protected]" header and says that this is an >>> unwanted mail >>> || >>> v >>> warning and pass to yahoo.com or simply drop... >> >> why does WEBSERVER does forward anything? >> forwarders have to be configured on the MTA/MDA and >> then your problems does not exist at all > > I am in a similar situation, and would like to bar people from using the > sendmail binary.
people do not software does - as example dbmail if in the dbmail_aliases a external fowarder is defined and since this is NOT using smtp the restrictions are not active here as expected > Having said that, I guess that Simon thinks of the case that the user is > using some webmail package, which could very well inject an email with a > sender @toto.com into the mail system. and that is why smtpd_*_restricitions are enforced: webmail usually uses smtp > Eg. my mutt is configured to set the envelope sender from the 'From:' > line, too, and a web application is equivalent to shell access, in his > case. a webapplication si NOT equivalent to shell access mostly it will NOT run on the same machine as the mailserver even if it does - normally you shpuld DISABLE any shell-commands for php and so the app is forced to use "phpmailer" as example which can use smtp and so your restrictions are aneforced in all this cases forwrding is never done by a webserver mor is it a topic for smtp restrictions because this are different worlds
signature.asc
Description: OpenPGP digital signature
