At 00.07 01/06/2006, you wrote:
tonix (Antonio Nati) wrote:
At 23.25 31/05/2006, you wrote:

tonix (Antonio Nati) wrote:

At 21.44 31/05/2006, you wrote:

Rick Macdougall wrote:

Ken Jones wrote:


Tonino was able to do a fast analysis of the problem.

Server: Qmail with Tonino's check user patch.

When an email sender identifying itself as SMTPSVC(6.0.3790.1830)
sends an email to multiple rcpt's, where some of the rcpt are
valid and some are invalid, not all the emails to valid rcpts
are delivered and the sender reports an incorrect list of
valid/invalid rcpts.

Problem due to Outlook not fully supporting SMTP protocol.

So there was no real resolution ? Did you have them stop using the ISA firewall ?

I disabled check user for their static IP.

Are they using your server as a relay, or are they just sending to everyone from Outlook? I feel chkuser should be disabled when used as relay from Outlook or Eudora.

They are just sending using Outlook. Not as a relay.
They are an external company sending to local users.

We do not have any reported problems from any relay users.

I have reported complaints from customers which use Outlook; when they send to multiple recipients (and one is wrong) cannot understand which is the error. So I have a dedicated qmail-smtpd for relaying users where I accept all messages without chkuser.

It looks like firefox does not like the error message too.

To be more exact, this is not a problem of chkuser, but of every smtp server rejecting not existing rcpt (including qmail + chkuser).

I sent a test mail to a valid and an invalid account on our mail
server and firefox pops up a message:

An error occurred while sending mail. The mail server responded:
sorry, no mailbox here by that name (#5.1.1 - chkusr). Please verify
that your email address is correct in your Mail preferences and try again.

Probably in a future version I'll give the option to have an extended error, specifying which rcpt has not been found.

Something like "sorry, <[EMAIL PROTECTED]> is not known/recognized on this server (#chkuser)".

Looks like I need to disable chkuser when RELAYCLIENT is set.

Is there an easy way, with the current version, to disable chk user
when the RELAYCLIENT is set?

Version 2.0.9 will have such feature. Probably I'll publish a 2.0.9-beta that could help to solve these problems (actual code is stable, but I have to add other features, or more likely I'll freeze 2.0.9 and work on 2.0.10).



Reply via email to