The messages that are not coming through (that I can confirm were
sent) appear to be bouncing back and forth between the sender's mail
server(s) and ours:
cat /var/log/qmail/smtp/current | tai64nlocal | grep senders-
[EMAIL PROTECTED] | more
2008-03-28 14:52:12.420736500 CHKUSER accepted sender: from <senders-
[EMAIL PROTECTED]::> remote <wx-out-0506.google.com:unknown:
66.249.82.228> rcpt <> : sender accepted
2008-03-28 14:52:12.481703500 CHKUSER accepted rcpt: from <senders-
[EMAIL PROTECTED]::> remote <wx-out-0506.google.com:unknown:
66.249.82.228> rcpt <[EMAIL PROTECTED]> : found existing recipient
2008-03-28 14:52:12.557343500 qmail-smtpd: qq soft reject (mail
server temporarily rejected message (#4.3.0)): MAILFROM:<senders-
[EMAIL PROTECTED]> RCPTTO:[EMAIL PROTECTED]
2008-03-28 14:58:29.973702500 CHKUSER accepted sender: from <senders-
[EMAIL PROTECTED]::> remote <wx-out-0506.google.com:unknown:
66.249.82.233> rcpt <> : sender accepted
2008-03-28 14:58:30.018130500 CHKUSER accepted rcpt: from <senders-
[EMAIL PROTECTED]::> remote <wx-out-0506.google.com:unknown:
66.249.82.233> rcpt <[EMAIL PROTECTED]> : found existing recipient
2008-03-28 14:58:30.093115500 qmail-smtpd: qq soft reject (mail
server temporarily rejected message (#4.3.0)): MAILFROM:<senders-
[EMAIL PROTECTED]> RCPTTO:[EMAIL PROTECTED]
2008-03-28 15:19:19.568116500 CHKUSER accepted sender: from <senders-
[EMAIL PROTECTED]::> remote <wx-out-0506.google.com:unknown:
66.249.82.234> rcpt <> : sender accepted
2008-03-28 15:19:19.622001500 CHKUSER accepted rcpt: from <senders-
[EMAIL PROTECTED]::> remote <wx-out-0506.google.com:unknown:
66.249.82.234> rcpt <[EMAIL PROTECTED]> : found existing recipient
2008-03-28 15:19:19.702765500 qmail-smtpd: qq soft reject (mail
server temporarily rejected message (#4.3.0)): MAILFROM:<senders-
[EMAIL PROTECTED]> RCPTTO:[EMAIL PROTECTED]
It's my mail server that is soft-rejecting these messages and
creating this havok. What's going on?
(And this is why there are times when I think it would be best to
never, ever, ever upgrade or touch a server that is working properly.)
On Mar 28, 2008, at 3:03 PM, Eric Shubert wrote:
Roxanne Sandesara wrote:
OK. I've added that. Thus far, it does appear to have worked, but I
can't be sure if that's just the usual 'come and go' of this
problem or
an actual honest-to-goodness solution.
The later. IIRC the reason it appeared to be intermittent would be
that it
only applies to mail that originated on windoze clients (which is
probably
the majority, but not all).
On my own, personal toaster server, which I only installed a month
ago,
fresh, this value was not added to the tcp.smtp line. If this is
something one needs to have, shouldn't the packages add that to the
files as they are created?
I'm surprised that a fresh install wouldn't have it. Did you start
with the
latest, or did you upgrade to the latest after installing a previous
version first?
On an upgrade, you should see a .rpmnew file that contains the
change. The
upgrade process (rpm) isn't sophisticated enough to make changes to
configuration files, so in the event that there's a change, the new
configuration file is tagged with the .rpmnew extension (sometimes
it's
replaced, and the previous file is tagged .rpmold). You should always
examine .rpmnew files for changes from the version you used before any
customization. This is SOP for rpm.
--
-Eric 'shubes'
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: qmailtoaster-list-
[EMAIL PROTECTED]
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
