Subscribing to this forum didn't work with default ispcp configuration

[Tseng]

simple Wrote:I'm a big fan of "stick with the standards"-behaviour in most cases. In the discussion here, where the standard install template of postfix is included, I would prefer a more fault tolerant solution. Most big providers in Germany (e.g. Freenet and T-Online) don't use a standards-conform HELO. So would you rather have every single admin change the two lines after installation, or wouldn't it be better to do something like that in the install template:

Code:

/etc/postfix/main.cf
[..]
smtpd_helo_restrictions      = permit_mynetworks,
                               permit_sasl_authenticated,
# would be more standards-compliant, but some big ISPs don't deliver FQDN HELOs
#                              reject_invalid_helo_hostname,
#                              reject_non_fqdn_helo_hostname
[..]

I agree to that. Like some of us noticed, it's a problem if very big isps dont stick to the standards. It wouldn't help anyone if big isps like t-online, freenet or others can't send emails to a ipscp server just because ispcp (postfix) requires a valid HELO as default setting. And like rbtux wrote... most of the people actually don't know what a HELO is. A lot of them have problems installing ispCP, so why should we rely on people knowing how to change the settings? Imho a valid HELO shouldn't be required by defaullt.

Tseng