Re: Problems receiving SMTP mail
From: Peter Weaver (newsgroup_at_weaverconsulting.ca)
Date: 05/18/05
- Next message: AEF: "Re: Backup /owner=original /overlay question"
- Previous message: Bill Gunshannon: "Re: Mac advertising vs. ideas for VMS advertising"
- In reply to: JF Mezei: "Re: Problems receiving SMTP mail"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 18 May 2005 16:15:14 -0400
JF Mezei wrote:
> Peter Weaver wrote:
>> Actually, what I posted was part of the log created by doing the
>> TCPIP$SMTP_RECV_TRACE.
>
> Perhaps you need to have the log level increased as well for the trace
> to really work.
>
> $DEFINE/SYSTEM TCPIP$SMTP_RECV_DEBUG 1
>
> The log you included in your original message did not have a data
> trace. The data trace is very obvious, what is being sent and what is
> being received.
Yup, had that one too;
"TCPIP$SMTP_LOG_LEVEL" = "3"
"TCPIP$SMTP_NOSEY" = "1"
"TCPIP$SMTP_RECV_DEBUG" = "1"
"TCPIP$SMTP_RECV_TRACE" = "1"
"TCPIP$SMTP_SYMB_TRACE" = "1"
>
>
>> This part happens just after the sender is
>> accepted.
>
> You mean VMS responds to the MAIL FROM: with a 200 series status
> message ? Or does VMS take forever to respond to it ?
Yup, 250 email-address... Sender OK
The response was fairly quick.
>
> Do you have any RBL services in your SMTP config ? RBLs normally
> generate an opcom message as well as go into accounting if accounting
> is enabled. (You need to enable MESSAGE (user message) class
> accounting.)
No RBL's yet.
>
>
>> Source 192.168.2.21 53749
>> Destination 192.168.2.21 53
>> UDP
>
>
> This is key here.
>
> 192.168 are local non routable addresses, so this probably means
inside
> your own lan. Both source and destination are the same, and the
> destination is port 53, which means DNS. Also, the fact that this
> uses UDP is not consistent with SMTP, but consistent with DNS.
>
> So the packets you are seeing are DNS requests being made to your own
> DNS server. And if your default domain for resolution is
> weaverconsulting.ca , and it can't resolve a domain, it tries to
> resolve it with the default comain appended.
>
> This is meant to work as:
> with default domain of chocolate.com:
>
> resolving "pastry" would initially fail,
> it then adds chocolate.com and will succeed in resolving
> pastry.chocolate.com
>
> So, it seems that your DNS server is unable to resolve the domain of
> the sender, and then tries to see if it might not be resolvable
> inside your domain.
That is consistent with the answer I hacked together, setting
"Accept-Unresolvable-Domains:" and "Accept-Unqualified-Senders:" to
true.
>
> Have you tried to NSLOOKUP the "xxxxx.com" to see what happens ?
>
> If this happens after the MAIL FROM: command, then you might want to
> TELNET/PORT=25 to your machine and enter:
>
> HELO xxxxx.com
> MAIL FROM: user@xxxxx.com
> RCPT TO: you@weaverconsulting.ca
> QUIT
>
> If you get 200 codes for the first 3 commands, it means that the
> problem might be in the receiver having problems doing reverse lookup
> of the IP address of the sending SMTP server.
>
Rats, I should have thought of that myself! I have given that answer out
to other people many times myself, but when I have a problem I forget to
check the basics!
>
> YOu can also play with the SMTP.CONFIG file to loosen restrictions on
> IP reverse transaltability.
Right, thanks for your help once again JF.
-- Peter Weaver Weaver Consulting Services Inc. Canadian VAR for CHARON-VAX www.weaverconsulting.ca
- Next message: AEF: "Re: Backup /owner=original /overlay question"
- Previous message: Bill Gunshannon: "Re: Mac advertising vs. ideas for VMS advertising"
- In reply to: JF Mezei: "Re: Problems receiving SMTP mail"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
