Hello,
We have a MDaemon running. The only problem we have is that confirmation messages of a subscription to a mailinglist are not accepted by Rollernet. There is also no entry in the incoming mail log for the domain on the Rollernet side. We have no problem with confirmation messages to other mail servers. Thanks
These are the messages. Could you tell where the problem is.
Thu 2008-10-09 07:44:08: <-- 220 mail2.rollernet.us ESMTP Postfix
Thu 2008-10-09 07:44:08: --> EHLO womenlobby:info
Thu 2008-10-09 07:44:09: <-- 250-mail2.rollernet.us
Thu 2008-10-09 07:44:09: <-- 250-PIPELINING
Thu 2008-10-09 07:44:09: <-- 250-SIZE 104857600
Thu 2008-10-09 07:44:09: <-- 250-VRFY
Thu 2008-10-09 07:44:09: <-- 250-ETRN
Thu 2008-10-09 07:44:09: <-- 250-STARTTLS
Thu 2008-10-09 07:44:09: <-- 250-ENHANCEDSTATUSCODES
Thu 2008-10-09 07:44:09: <-- 250-8BITMIME
Thu 2008-10-09 07:44:09: <-- 250 DSN
Thu 2008-10-09 07:44:09: --> MAIL From:<MDaemon@womenlobby.info> SIZE=967
Thu 2008-10-09 07:44:09: <-- 250 2.1.0 Ok
Thu 2008-10-09 07:44:09: --> RCPT To:<wkuypers@pragmacom.eu>
Thu 2008-10-09 07:44:09: <-- 501 5.5.2 <womenlobby:info>: Helo command rejected: Invalid name
Thu 2008-10-09 07:44:09: --> QUIT
confirmation message mailinglist Mdaemon
Moderator: Moderators
-
- Site Admin
- Posts: 598
- Joined: Wed Nov 17, 2004 10:05 pm
- Location: Nevada
- Contact:
It's the HELO:
There can't be a : in the HELO; it causes it to fail a valid FQDN format test. We don't check to see if the HELO is real (i.e. "test.local" would pass because Exchange does this a lot even though it would never resolve for us), but it needs to be formatted properly.Thu 2008-10-09 07:44:08: --> EHLO womenlobby:info
Technical Support support@rollernet.us
Roller Network LLC
Roller Network LLC
-
- Site Admin
- Posts: 598
- Joined: Wed Nov 17, 2004 10:05 pm
- Location: Nevada
- Contact:
Here's the line from our logs:
The ":" character really was sent. The gmail servers do not check for proper HELO formatting as you can see here:
(Google also lets me forge the sender domain, in addition to accepting the invalid HELO, and the message was not marked as spam.)
However, we do check for proper HELO/EHLO formatting. For more information, see Postfix smtpd_helo_restrictions for reject_invalid_helo_hostname.
Code: Select all
Oct 8 22:44:15 mail2 postfix/smtpd[24057]: NOQUEUE: reject: RCPT from sv0.pragmacom.be[213.186.35.47]: 501 5.5.2 <womenlobby:info>: Helo command rejected: Invalid name; from=<MDaemon@womenlobby.info> to=<wkuypers@pragmacom.eu> proto=ESMTP helo=<womenlobby:info>
Code: Select all
smtpauth:~$ telnet gmail-smtp-in.l.google.com 25
Trying 209.85.199.27...
Connected to gmail-smtp-in.l.google.com.
Escape character is '^]'.
220 mx.google.com ESMTP l31si5449026rvb.2
HELO womenlobby:info
250 mx.google.com at your service
MAIL FROM:<MDaemon@womenlobby.info>
250 2.1.0 OK l31si5449026rvb.2
RCPT TO:<glendale2x@gmail.com>
250 2.1.5 OK l31si5449026rvb.2
DATA
354 Go ahead l31si5449026rvb.2
subject: test
test
.
250 2.0.0 OK 1223652255 l31si5449026rvb.2
quit
221 2.0.0 closing connection l31si5449026rvb.2
However, we do check for proper HELO/EHLO formatting. For more information, see Postfix smtpd_helo_restrictions for reject_invalid_helo_hostname.
Technical Support support@rollernet.us
Roller Network LLC
Roller Network LLC