I've inherited a small problem to solve...
client is "blackadder", solaris 5.10 (sparc), running Sendmail
8.13.8+Sun/8.13.8
relay/mailhost is "jack", solaris 5.10 9sparc) running Sendmail
8.13.8+Sun/8.13.8
mc file is
divert(0)dnl
VERSIONID(`@(#)sendmail.mc 1.11 (Sun) 06/21/04')
OSTYPE(`solaris8')dnl
DOMAIN(`solaris-generic')dnl
define(`confFALLBACK_SMARTHOST', `mailhost$?m.$m$.')dnl
FEATURE(`access_db', `hash -T<TMPF> /etc/mail/access_map')
FEATURE(`domaintable')dnl
FEATURE(`virtusertable', `dbm /etc/mail/virtusers')
FEATURE(`blacklist_recipients')
FEATURE(`mailertable')
FEATURE(`delay_checks')
MAILER(`local')dnl
MAILER(`smtp')dnl
define(`confMAX_HEADERS_LENGTH',16384)dnl
define(`confPRIVACY_FLAGS',`goaway')dnl
define(`confMAX_RCPTS_PER_MESSAGE',50)dnl
define(`confSMTP_LOGIN_MSG', `$j server ready at $b')dnl
define(`confPRIVACY_FLAGS',`novrfy, noexpn, needmailhelo,
restrictmailq, restrictqrun, needexpnhelo, needvrfyhelo')dnl
define(`confBAD_RCPT_THROTTLE', 3)dnl
LOCAL_NET_CONFIG
R$* < @ $* .$m. > $* $#esmtp $@ $2.$m $: $1 < @ $2.$m. > $3
LOCAL_RULE_3
R$* <@ $* .issolutions.co.uk > $: $1 <@ jack.issolutions.co.uk >
access database includes
to:didds3@yahoo.co.uk RELAY
Connect:192.168.52.48 REJECT
however, when we battempt to send an email to didds3@yahoo.co.uk from
the client (blackadder -192.168.52.48) it never arrives. If sent from
the relay/mailhub itself it does FTR.
when this occurs the log on the relay host includes the line(s) (which
i think are the pertinent ones)
[xxx's to replace real world domain name, hidden for obvious reasons]
Feb 24 12:32:03 jack sendmail[9778]: [ID 801593 mail.info]
p1OCVhDu009778: from=
<iss@blackadder.xxxxx.xx.xx>, size=354, class=0, nrcpts=1,
msgid=<20110224
1230.p1OCUsEQ007484@blackadder.xxxxx.xx.xx>, proto=ESMTP, daemon=MTA-
v4, r
elay=blackadder.xxxx.xx.xx [192.168.52.48]
Feb 24 12:32:03 jack sendmail[9778]: [ID 801593 mail.info]
p1OCVhDu009778: from=<iss@blackadder.xxxxx.xx.xx>, size=354, class=0,
nrcpts=1, msgid=<201102241230.p1OCUsEQ007484@blackadder.xxxxx.xx.xx>,
proto=ESMTP, daemon=MTA-v4, relay=blackadder.xxxx.xx.xx
[192.168.52.48]
Feb 24 12:39:37 jack sendmail[9828]: [ID 702911 mail.info]
STARTTLS=client, relay=mailhost.xxxxx.xx.xx, version=TLSv1/SSLv3,
verify=FAIL, cipher=AES128-SHA, bits=128/128
Feb 24 12:39:42 jack sendmail[9828]: [ID 801593 mail.info]
p1OCVhDu009778: to=<didds3@yahoo.co.uk>, delay=00:07:39,
xdelay=00:07:39, mailer=esmtp, pri=120354,
relay=mailhost.issolutions.co.uk [192.168.52.4], dsn=5.7.1, stat=User
unknown
Feb 24 12:40:17 jack sendmail[9828]: [ID 801593 mail.info]
p1OCVhDu009778: p1OCeHDu009828: DSN: User unknown
Feb 24 12:40:28 jack sendmail[9828]: [ID 801593 mail.info]
p1OCeHDu009828: to=<iss@blackadder.xxxxx.xx.xx>, delay=00:00:11,
xdelay=00:00:00, mailer=esmtp, pri=31612,
relay=blackadder.xxxxx.xx.xx. [192.168.52.48], dsn=2.0.0, stat=Sent
(p1OCeS3P008480 Message accepted for delivery)
I understabnd that sendmail usess the access DB in the order of "ips",
"from" then "to" which would explain it rejecfting email from
blackadder before accepting the email address to be sent to... but I
thought the m4 macro
FEATURE(`delay_checks') was supposed to reverse that order, which
would aloow the email to be sent?
what are we doing wrong?
finally as welll... if I use /etc/init.d/sendmail restart (which is
just a svcadm restart) it doesn;t start the
/usr/lib/sendmail -bd -q15m daemon... but it starts manually fine.
any ideas what is happening there?
cheers
ian
|
|
0
|
|
|
|
Reply
|
didds
|
2/24/2011 2:17:36 PM |
|
In article <7e052b50-206d-42f3-95de-b381641aaf38@d12g2000vbz.googlegroups.com>,
didds <didds3@yahoo.co.uk> wrote:
>I've inherited a small problem to solve...
>
>however, when we battempt to send an email to didds3@yahoo.co.uk from
>the client (blackadder -192.168.52.48) it never arrives. If sent from
>the relay/mailhub itself it does FTR.
>
>when this occurs the log on the relay host includes the line(s) (which
>i think are the pertinent ones)
>
>Feb 24 12:32:03 jack sendmail[9778]: [ID 801593 mail.info]
>p1OCVhDu009778: from=<iss@blackadder.xxxxx.xx.xx>, size=354, class=0, nrcpts=1,
>msgid=<20110224 1230.p1OCUsEQ007484@blackadder.xxxxx.xx.xx>, proto=ESMTP,
>daemon=MTA-v4, relay=blackadder.xxxx.xx.xx [192.168.52.48]
>
>Feb 24 12:32:03 jack sendmail[9778]: [ID 801593 mail.info]
>p1OCVhDu009778: from=<iss@blackadder.xxxxx.xx.xx>, size=354, class=0,
>nrcpts=1, msgid=<201102241230.p1OCUsEQ007484@blackadder.xxxxx.xx.xx>,
>proto=ESMTP, daemon=MTA-v4, relay=blackadder.xxxx.xx.xx [192.168.52.48]
>
>Feb 24 12:39:37 jack sendmail[9828]: [ID 702911 mail.info]
>STARTTLS=client, relay=mailhost.xxxxx.xx.xx, version=TLSv1/SSLv3,
>verify=FAIL, cipher=AES128-SHA, bits=128/128
Fix the TLS problem shown above.
>Feb 24 12:39:42 jack sendmail[9828]: [ID 801593 mail.info]
>p1OCVhDu009778: to=<didds3@yahoo.co.uk>, delay=00:07:39,
>xdelay=00:07:39, mailer=esmtp, pri=120354,
>relay=mailhost.issolutions.co.uk [192.168.52.4], dsn=5.7.1, stat=User
>unknown
Second issue: the backup smarthost doesn't like the message.
>
>Feb 24 12:40:17 jack sendmail[9828]: [ID 801593 mail.info]
>p1OCVhDu009778: p1OCeHDu009828: DSN: User unknown
>
>Feb 24 12:40:28 jack sendmail[9828]: [ID 801593 mail.info]
>p1OCeHDu009828: to=<iss@blackadder.xxxxx.xx.xx>, delay=00:00:11,
>xdelay=00:00:00, mailer=esmtp, pri=31612,
>relay=blackadder.xxxxx.xx.xx. [192.168.52.48], dsn=2.0.0, stat=Sent
>(p1OCeS3P008480 Message accepted for delivery)
bounce message relayed back to sender.
>
>I understabnd that sendmail usess the access DB in the order of "ips",
>"from" then "to" which would explain it rejecfting email from
>blackadder before accepting the email address to be sent to... but I
>thought the m4 macro
>FEATURE(`delay_checks') was supposed to reverse that order, which
>would aloow the email to be sent?
>
>
>what are we doing wrong?
>
>finally as welll... if I use /etc/init.d/sendmail restart (which is
>just a svcadm restart) it doesn;t start the
>
>/usr/lib/sendmail -bd -q15m daemon... but it starts manually fine.
>any ideas what is happening there?
>
>cheers
>
>ian
>
|
|
0
|
|
|
|
Reply
|
bonomi
|
2/24/2011 4:26:24 PM
|
|
|
1 Replies
396 Views
(page loaded in 0.043 seconds)
Similiar Articles: relaying ONLY to an email address - comp.mail.sendmailI've inherited a small problem to solve... client is "blackadder", solaris 5.10 (sparc), running Sendmail 8.13.8+Sun/8.13.8 relay/mailhost is "ja... Configuring sendmail relay behind the firewall - comp.unix.solaris ...Right now, my email addresses (all [user]@gangwarily.ca ... The only differance I can see is the actual MX spec in ... mx > stantive.com Server: 10.171.93.101 Address ... ALOM 1.5 domain name problem - comp.unix.solarisrelaying ONLY to an email address - comp.mail.sendmail ALOM 1.5 domain name problem - comp.unix.solaris relaying ONLY to an email address - comp.mail.sendmail I've ... Email addresses want to delete from the Address Line - comp.mail ...relaying ONLY to an email address - comp.mail.sendmail... this occurs the log on the relay host includes the line(s ... Send mail script step - Sending mail to multiple ... why connecting to 127.0.0.1 via relay? - comp.mail.miscrelaying ONLY to an email address - comp.mail.sendmail why connecting to 127.0.0.1 via relay? - comp.mail.misc Only allow connections from localhost - comp ... denied ... sending current record by email - comp.databases.filemaker ...relaying ONLY to an email address - comp.mail.sendmail sending current record by email - comp.databases.filemaker ... relaying ONLY to an email address - comp.mail ... login fail block IP - comp.sys.sun.adminrelaying ONLY to an email address - comp.mail.sendmail... confMAX_RCPTS_PER_MESSAGE',50)dnl define(`confSMTP_LOGIN ... mailhost.xxxxx.xx.xx, version=TLSv1/SSLv3, verify ... Only allow connections from localhost - comp.databases.ibm-db2 ...relaying ONLY to an email address - comp.mail.sendmail why connecting to 127.0.0.1 via relay? - comp.mail.misc Only allow connections from localhost ... problem sending mail: Sending the email to the following server ...... import org.apache.commons.mail.*;SimpleEmail email = new ... If the "To" field is> a domain external address (name ... has configured it toprevent it being used as a relay. Kentrox/Cisco/Subrate DS3 problems.... - comp.dcom.sys.cisco ...... yea, remove the usual spam stuff to email me ... command on the hssi interface, it shows only ... interface Hssi1/0.12 point-to-point ip address x.x.x.x x.x.x.x frame-relay ... Global Relay » Support » Email, Continuity and Security SupportIMAP creates a continual connection to the server and only ... Webmail is accessed from the Global Relay login page (your full email address and password are required). Relaying Denied - the email error explained. - Gammadyne CorporationAn explanation of the 'Relaying Denied' email error. ... to specify the mail server's local IP address, not ... The only other solution is to not use the mail ... 7/23/2012 4:10:27 PM
|