Auteur: Darren Mackay - Lists Date: À: exim-users Sujet: RE: [Exim] Access denied error and retries
Hi,
| > So are you are saying that upgrading to exim v3.22 will actually bounce the | > messages rther than attempting delivery on an alternate smarthost? | | I am. | | > If this
| > is the case this would in fact create quite a problem with users compalining | > mail is bouncing just because the ISP uses an MTA that does not fully
| > conform to the RFCs (it is also very unlikely that the ISP will change their | > MTA either - they are using a custom version of sendmail I believe). | | I'm sorry, but if an MTA doesn't conform to the RFCs in too gross a way,
| what can I do? Exim was changed from its previous incorrect behaviour
| because people pointed out that it was buggy, and that it should bounce
| messages when it received an initial response such as "554 No SMTP
| service here".
Rather than risk heaps of users getting really really unhappy and the
possibility of management getting rather upset I would rather put up with my
logs filled with errors during peak times for the time being (considering we
used to have every problem under the sun before using exim as a gatway for
our internal mail servers).
I received a response from the ISP and essentially they said they will not
be changing their MTAs just because they received a few complaints every
week (I assume from this that I am not the only person who has complained).
In a perfect world, all MTAs will completely conform to the relevant RFCs.
But in reality, they don't. It would be nice if exim would attempt delivery
using alternate routers / smarthosts rather than bouncing the messages on
the first error though (any chance of this making it ito v4??)