I find that most of the complaints I get come from
places where deferred mail happens. So I want to never
have any mail deferred. If it isn't bad enough to reject,
then I will take it.
I tried turning deferall off by putting a "0" entry in
the "Defer Acceptance" on the "Handling Tab"
On teh Connections Tab, I also entered 0 in the New
Contact Delay.
But It still defers the mail. The entry in the log says
Defer until 00:00 for nnn.nnn.nnn.nnn mail.yadayada.com
followed by Deferred mail to david@watchit.com form
<mail. someothing.com> nnn.nnn.nnn.nnn
I have been loving Fluffy so far, but lately I am getting
so many complaints about it mail not getting through,
only to find that most is deferred and never resent
because some bozo's have their mail server set with too
short a rety period. and now this is starting to take way
too much time to explain it.
How do I shut off dererral all together. Am I failing to do
it right, or is this a bug?
BTW, the good news, is that the Fluffy does properly tell
Exchange to retry. I installed the registry hack that
Wayne suggested a while back and at least I get the
proper retry indication into Exchange. But I find many
Exchange installs have about only a couple of minute
retry period, and all I have tried then immediately call it
undeliverable.
Thanks
David
Logged In: YES
user_id=660239
Ok, what you describe is a bug. And what you describe was, I
thought, fixed in all recent 1.4.x releaases of Fluffy. What
version are you running?
There is still a bug when Fluffy reports getting stuck in
ipvalidate loop when the defer time is set to zero. Fluffy will
then accept the mail without doing a DNSBL check. This is
fixed in 1.4.83.
The onyl other comment is that if a connection is cached as
having been dedeferred, and then you sent the defer new
contact time to 0 minutes, the cached values will still be used
until their timer expires. So if the defer time was 15 minutes,
and you set it to 0, some sites might still get deferred if the
previously connected in the last 15 minute window. But this
doesn't seem to be the problem you describe.
Anyway, please try 1.4.83 (available under bug report
titled 'best 1.4 version here') and let me know if you still have
this issue/