Discussion:
Sendmail Issue
Tommy Laino
2012-08-08 19:03:34 UTC
Permalink
I am trying to setup voicemail to email notification. I read
thru the wiki on it and sendmail is installed. But when I
try to telnet to the localhost on port 25 the connection is
refused. This is my first time working with sendmail so
please be gentle on me. Thanks guys
--
Tommy Laino
Dome Technologies
Tommy Laino
2012-08-08 19:04:42 UTC
Permalink
This is SipX 4.4
--
Tommy Laino
Dome Technologies
Tony Graziano
2012-08-08 21:25:03 UTC
Permalink
We don't know how you installed this. ISO or RPM?

What is the output of

/etc/init.d/sendmail status

On Wed, Aug 8, 2012 at 3:04 PM, Tommy Laino <***@gmail.com> wrote:

>
>
> This is SipX 4.4
> --
> Tommy Laino
> Dome Technologies
> _______________________________________________
> sipx-users mailing list
> sipx-***@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>



--
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: ***@voice.myitdepartment.net
Fax: 434.465.6833
~~~~~~~~~~~~~~~~~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~

Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
2013!
<http://sipxcolab2013.eventbrite.com/?discount=tony2013>

--
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: ***@voice.myitdepartment.net

Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net
Tommy Laino
2012-08-09 02:36:04 UTC
Permalink
I installed it through RPM. The output I got was sendmail
(2506 2505) is running...
--
Tommy Laino
Dome Technologies
Douglas Hubler
2012-08-09 02:31:50 UTC
Permalink
sipxecs 4.4 or 4.6? in 4.6 smtp port would be blocked from ip
addresses outside the box (or cluster)

On Wed, Aug 8, 2012 at 10:36 PM, Tommy Laino <***@gmail.com> wrote:
>
>
> I installed it through RPM. The output I got was sendmail
> (2506 2505) is running...
> --
> Tommy Laino
> Dome Technologies
> _______________________________________________
> sipx-users mailing list
> sipx-***@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
Todd Hodgen
2012-08-09 07:05:02 UTC
Permalink
A few things that I've found with Sendmail, it's usually the receiving SMTP
gateway that is not happy with the domain used, or the email account.
Sometimes, adding the Emailformats file into etc/sipxpbx/sipivr and editing
it with an acceptable email address and domain resolves some of these
issues.
http://wiki.sipfoundry.org/display/sipXecs/Voicemail-Email+Custom+Notificati
ons

I find it easy to look at var/log/sendmail file to see what address emails
are being sent from, and sometimes there are some nice troubleshooting
nuggets in there as well.

-----Original Message-----
From: sipx-users-***@list.sipfoundry.org
[mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of Tommy Laino
Sent: Wednesday, August 08, 2012 7:36 PM
To: sipx-***@list.sipfoundry.org
Subject: Re: [sipx-users] Sendmail Issue



I installed it through RPM. The output I got was sendmail
(2506 2505) is running...
--
Tommy Laino
Dome Technologies
Michael Picher
2012-08-09 10:12:10 UTC
Permalink
If you have setup your SIP domain the same as your email domain may need to
add specific mx records and an A record to your DNS zone file.

Mike

On Thu, Aug 9, 2012 at 3:05 AM, Todd Hodgen <***@frontier.com> wrote:

> A few things that I've found with Sendmail, it's usually the receiving SMTP
> gateway that is not happy with the domain used, or the email account.
> Sometimes, adding the Emailformats file into etc/sipxpbx/sipivr and editing
> it with an acceptable email address and domain resolves some of these
> issues.
>
> http://wiki.sipfoundry.org/display/sipXecs/Voicemail-Email+Custom+Notificati
> ons
>
> I find it easy to look at var/log/sendmail file to see what address emails
> are being sent from, and sometimes there are some nice troubleshooting
> nuggets in there as well.
>
> -----Original Message-----
> From: sipx-users-***@list.sipfoundry.org
> [mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of Tommy Laino
> Sent: Wednesday, August 08, 2012 7:36 PM
> To: sipx-***@list.sipfoundry.org
> Subject: Re: [sipx-users] Sendmail Issue
>
>
>
> I installed it through RPM. The output I got was sendmail
> (2506 2505) is running...
> --
> Tommy Laino
> Dome Technologies
> _______________________________________________
> sipx-users mailing list
> sipx-***@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>
> _______________________________________________
> sipx-users mailing list
> sipx-***@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>



--
Michael Picher, Director of Technical Services
eZuce, Inc.

300 Brickstone Square****

Suite 201****

Andover, MA. 01810
O.978-296-1005 X2015
M.207-956-0262
@mpicher <http://twitter.com/mpicher>
linkedin <http://www.linkedin.com/profile/view?id=35504760&trk=tab_pro>
www.ezuce.com

------------------------------------------------------------------------------------------------------------
There are 10 kinds of people in the world, those who understand binary and
those who don't.
Tommy Laino
2012-10-30 18:41:50 UTC
Permalink
So I am back working on this again. I have done some
research and troubleshooting. I found that I am getting a
connection refused by 127.0.0.1. I believe that is wrong but
I have no idea how to fix it. Anybody know how to fix that?
--
Tommy Laino
Dome Technologies
Tony Graziano
2012-10-30 18:44:45 UTC
Permalink
Please verify whether you have more than one SMTP server running (i.e. is
postfix also installed somehow?).

This should be easy, and it's perplexing that it has come up. It works for
me in 4.4 or 4.6 out of the box.

What does the sendmail configuration file look like and HOW did you
configure it?

This is the canned sendmail m4 configuration from sipx 4.4:

divert(-1)dnl
dnl #
dnl # This is the sendmail macro config file for m4. If you make changes to
dnl # /etc/mail/sendmail.mc, you will need to regenerate the
dnl # /etc/mail/sendmail.cf file by confirming that the sendmail-cf package
is
dnl # installed and then performing a
dnl #
dnl # make -C /etc/mail
dnl #
include(`/usr/share/sendmail-cf/m4/cf.m4')dnl
VERSIONID(`setup for linux')dnl
OSTYPE(`linux')dnl
dnl #
dnl # Do not advertize sendmail version.
dnl #
dnl define(`confSMTP_LOGIN_MSG', `$j Sendmail; $b')dnl
dnl #
dnl # default logging level is 9, you might want to set it higher to
dnl # debug the configuration
dnl #
dnl define(`confLOG_LEVEL', `9')dnl
dnl #
dnl # Uncomment and edit the following line if your outgoing mail needs to
dnl # be sent out through an external mail server:
dnl #
dnl define(`SMART_HOST', `smtp.your.provider')dnl
dnl #
define(`confDEF_USER_ID', ``8:12'')dnl
dnl define(`confAUTO_REBUILD')dnl
define(`confTRY_NULL_MX_LIST', `True')dnl
define(`confDONT_PROBE_INTERFACES', `True')dnl
define(`PROCMAIL_MAILER_PATH', `/usr/bin/procmail')dnl
define(`ALIAS_FILE', `/etc/aliases')dnl
define(`STATUS_FILE', `/var/log/mail/statistics')dnl
define(`UUCP_MAILER_MAX', `2000000')dnl
define(`confUSERDB_SPEC', `/etc/mail/userdb.db')dnl
define(`confPRIVACY_FLAGS', `authwarnings,novrfy,noexpn,restrictqrun')dnl
define(`confAUTH_OPTIONS', `A')dnl
dnl #
dnl # The following allows relaying if the user authenticates, and disallows
dnl # plaintext authentication (PLAIN/LOGIN) on non-TLS links
dnl #
dnl define(`confAUTH_OPTIONS', `A p')dnl
dnl #
dnl # PLAIN is the preferred plaintext authentication method and used by
dnl # Mozilla Mail and Evolution, though Outlook Express and other MUAs do
dnl # use LOGIN. Other mechanisms should be used if the connection is not
dnl # guaranteed secure.
dnl # Please remember that saslauthd needs to be running for AUTH.
dnl #
dnl TRUST_AUTH_MECH(`EXTERNAL DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl
dnl define(`confAUTH_MECHANISMS', `EXTERNAL GSSAPI DIGEST-MD5 CRAM-MD5
LOGIN PLAIN')dnl
dnl #
dnl # Rudimentary information on creating certificates for sendmail TLS:
dnl # cd /etc/pki/tls/certs; make sendmail.pem
dnl # Complete usage:
dnl # make -C /etc/pki/tls/certs usage
dnl #
dnl define(`confCACERT_PATH', `/etc/pki/tls/certs')dnl
dnl define(`confCACERT', `/etc/pki/tls/certs/ca-bundle.crt')dnl
dnl define(`confSERVER_CERT', `/etc/pki/tls/certs/sendmail.pem')dnl
dnl define(`confSERVER_KEY', `/etc/pki/tls/certs/sendmail.pem')dnl
dnl #
dnl # This allows sendmail to use a keyfile that is shared with OpenLDAP's
dnl # slapd, which requires the file to be readble by group ldap
dnl #
dnl define(`confDONT_BLAME_SENDMAIL', `groupreadablekeyfile')dnl
dnl #
dnl define(`confTO_QUEUEWARN', `4h')dnl
dnl define(`confTO_QUEUERETURN', `5d')dnl
dnl define(`confQUEUE_LA', `12')dnl
dnl define(`confREFUSE_LA', `18')dnl
dnl FEATURE(delay_checks)dnl
FEATURE(`no_default_msa', `dnl')dnl
FEATURE(`smrsh', `/usr/sbin/smrsh')dnl
FEATURE(`mailertable', `hash -o /etc/mail/mailertable.db')dnl
FEATURE(`virtusertable', `hash -o /etc/mail/virtusertable.db')dnl
FEATURE(redirect)dnl
FEATURE(always_add_domain)dnl
FEATURE(use_cw_file)dnl
FEATURE(use_ct_file)dnl
dnl #
dnl # The following limits the number of processes sendmail can fork to
accept
dnl # incoming messages or process its message queues to 20.) sendmail
refuses
dnl # to accept connections once it has reached its quota of child
processes.
dnl #
dnl define(`confMAX_DAEMON_CHILDREN', `20')dnl
dnl #
dnl # Limits the number of new connections per second. This caps the
overhead
dnl # incurred due to forking new sendmail processes. May be useful against
dnl # DoS attacks or barrages of spam. (As mentioned below, a per-IP
address
dnl # limit would be useful but is not available as an option at this
writing.)
dnl #
dnl define(`confCONNECTION_RATE_THROTTLE', `3')dnl
dnl #
dnl # The -t option will retry delivery if e.g. the user runs over his
quota.
dnl #
FEATURE(local_procmail, `', `procmail -t -Y -a $h -d $u')dnl
FEATURE(`access_db', `hash -T<TMPF> -o /etc/mail/access.db')dnl
FEATURE(`blacklist_recipients')dnl
EXPOSED_USER(`root')dnl
dnl #
dnl # For using Cyrus-IMAPd as POP3/IMAP server through LMTP delivery
uncomment
dnl # the following 2 definitions and activate below in the MAILER section
the
dnl # cyrusv2 mailer.
dnl #
dnl define(`confLOCAL_MAILER', `cyrusv2')dnl
dnl define(`CYRUSV2_MAILER_ARGS', `FILE /var/lib/imap/socket/lmtp')dnl
dnl #
dnl # The following causes sendmail to only listen on the IPv4 loopback
address
dnl # 127.0.0.1 and not on any other network devices. Remove the loopback
dnl # address restriction to accept email from the internet or intranet.
dnl #
DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl
dnl #
dnl # The following causes sendmail to additionally listen to port 587 for
dnl # mail from MUAs that authenticate. Roaming users who can't reach their
dnl # preferred sendmail daemon due to port 25 being blocked or redirected
find
dnl # this useful.
dnl #
dnl DAEMON_OPTIONS(`Port=submission, Name=MSA, M=Ea')dnl
dnl #
dnl # The following causes sendmail to additionally listen to port 465, but
dnl # starting immediately in TLS mode upon connecting. Port 25 or 587
followed
dnl # by STARTTLS is preferred, but roaming clients using Outlook Express
can't
dnl # do STARTTLS on ports other than 25. Mozilla Mail can ONLY use STARTTLS
dnl # and doesn't support the deprecated smtps; Evolution <1.1.1 uses smtps
dnl # when SSL is enabled-- STARTTLS support is available in version 1.1.1.
dnl #
dnl # For this to work your OpenSSL certificates must be configured.
dnl #
dnl DAEMON_OPTIONS(`Port=smtps, Name=TLSMTA, M=s')dnl
dnl #
dnl # The following causes sendmail to additionally listen on the IPv6
loopback
dnl # device. Remove the loopback address restriction listen to the network.
dnl #
dnl DAEMON_OPTIONS(`port=smtp,Addr=::1, Name=MTA-v6, Family=inet6')dnl
dnl #
dnl # enable both ipv6 and ipv4 in sendmail:
dnl #
dnl DAEMON_OPTIONS(`Name=MTA-v4, Family=inet, Name=MTA-v6, Family=inet6')
dnl #
dnl # We strongly recommend not accepting unresolvable domains if you want
to
dnl # protect yourself from spam. However, the laptop and users on computers
dnl # that do not have 24x7 DNS do need this.
dnl #
FEATURE(`accept_unresolvable_domains')dnl
dnl #
dnl FEATURE(`relay_based_on_MX')dnl
dnl #
dnl # Also accept email sent to "localhost.localdomain" as local email.
dnl #
LOCAL_DOMAIN(`localhost.localdomain')dnl
dnl #
dnl # The following example makes mail from this host and any additional
dnl # specified domains appear to be sent from mydomain.com
dnl #
dnl MASQUERADE_AS(`mydomain.com')dnl
dnl #
dnl # masquerade not just the headers, but the envelope as well
dnl #
dnl FEATURE(masquerade_envelope)dnl
dnl #
dnl # masquerade not just @mydomainalias.com, but @*.mydomainalias.com as
well
dnl #
dnl FEATURE(masquerade_entire_domain)dnl
dnl #
dnl MASQUERADE_DOMAIN(localhost)dnl
dnl MASQUERADE_DOMAIN(localhost.localdomain)dnl
dnl MASQUERADE_DOMAIN(mydomainalias.com)dnl
dnl MASQUERADE_DOMAIN(mydomain.lan)dnl
MAILER(smtp)dnl
MAILER(procmail)dnl
dnl MAILER(cyrusv2)dnl
#
# Configured by sipX PBX: sipxpbx 4.4.0
#
# Configured by sipX PBX: sipxpbx 4.4.0
#
# Configured by sipX PBX: sipxpbx 4.4.0
#
# Configured by sipX PBX: sipxpbx 4.4.0
#
# Configured by sipX PBX: sipxpbx 4.4.0
#
# Configured by sipX PBX: sipxpbx 4.4.0
#
# Configured by sipX PBX: sipxpbx 4.4.0
#
# Configured by sipX PBX: sipxpbx 4.4.0
define(`confMCI_CACHE_TIMEOUT', `1m')dnl
define(`confTO_INITIAL', `1m')dnl
define(`confTO_CONNECT', `1m')dnl
define(`confTO_ACONNECT', `1m')dnl
define(`confTO_HELO', `1m')dnl
define(`confTO_MAIL', `1m')dnl
define(`confTO_RCPT', `1m')dnl
define(`confTO_DATAINIT', `1m')dnl
define(`confTO_DATABLOCK', `1m')dnl
define(`confTO_DATAFINAL', `1m')dnl
define(`confTO_RSET', `1m')dnl
define(`confTO_QUIT', `1m')dnl
define(`confTO_MISC', `1m')dnl
define(`confTO_COMMAND', `1m')dnl
define(`confTO_IDENT', `1m')dnl
define(`confTO_FILEOPEN', `1m')dnl
define(`confTO_LHLO', `1m')dnl
define(`confTO_AUTH', `1m')dnl
define(`confTO_STARTTLS', `1m')dnl
define(`confTO_CONTROL', `1m')dnl
define(`confTO_QUEUERETURN', `1d')dnl
define(`confTO_QUEUERETURN_DSN', `1h')dnl
define(`confTO_QUEUEWARN', `2d')dnl

--



On Tue, Oct 30, 2012 at 2:41 PM, Tommy Laino <***@gmail.com> wrote:

>
>
> So I am back working on this again. I have done some
> research and troubleshooting. I found that I am getting a
> connection refused by 127.0.0.1. I believe that is wrong but
> I have no idea how to fix it. Anybody know how to fix that?
> --
> Tommy Laino
> Dome Technologies
> _______________________________________________
> sipx-users mailing list
> sipx-***@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>



--
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: ***@voice.myitdepartment.net
Fax: 434.465.6833
~~~~~~~~~~~~~~~~~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~

Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
2013!
<http://sipxcolab2013.eventbrite.com/?discount=tony2013>

--
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: ***@voice.myitdepartment.net

Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net
Tommy Laino
2012-10-30 19:20:53 UTC
Permalink
Tony I checked to see if postfix or someother MTA is running
or installed and so far it appears that only sendmail is
installed. It was installed out of the box when I installed
4.4 through ISO. I have made no changes to the config file
for sendmail. Here it is

dnl # The -t option will retry delivery if e.g. the user
runs over his quota.
dnl #
FEATURE(local_procmail, `', `procmail -t -Y -a $h -d
$u')dnl
Fs is the sendmail macro config file for m4. If you make
changes to
dnl # /etc/mail/sendmail.mc, you will need to regenerate
the
dnl # /etc/mail/sendmail.cf file by confirming that the
sendmail-cf package is
dnl # installed and then performing a
dnl #
dnl # make -C /etc/mail
dnl #
include(`/usr/share/sendmail-cf/m4/cf.m4')dnl
VERSIONID(`setup for linux')dnl
OSTYPE(`linux')dnl
dnl #
dnl # Do not advertize sendmail version.
dnl #
dnl define(`confSMTP_LOGIN_MSG', `$j Sendmail; $b')dnl
dnl #
dnl # default logging level is 9, you might want to set it
higher to
dnl # debug the configuration
dnl #
dnl define(`confLOG_LEVEL', `9')dnl
dnl #
dnl # Uncomment and edit the following line if your outgoing
mail needs to
dnl # be sent out through an external mail server:
dnl #
dnl define(`SMART_HOST', `smtp.your.provider')dnl
dnl #
define(`confDEF_USER_ID', ``8:12'')dnl
dnl define(`confAUTO_REBUILD')dnl
define(`confTRY_NULL_MX_LIST', `True')dnl
define(`confDONT_PROBE_INTERFACES', `True')dnl
define(`PROCMAIL_MAILER_PATH', `/usr/bin/procmail')dnl
define(`ALIAS_FILE', `/etc/aliases')dnl
define(`STATUS_FILE', `/var/log/mail/statistics')dnl
define(`UUCP_MAILER_MAX', `2000000')dnl
define(`confUSERDB_SPEC', `/etc/mail/userdb.db')dnl
define(`confPRIVACY_FLAGS',
`authwarnings,novrfy,noexpn,restrictqrun')dnl
define(`confAUTH_OPTIONS', `A')dnl
dnl #
dnl # The following allows relaying if the user
authenticates, and disallows
dnl # plaintext authentication (PLAIN/LOGIN) on non-TLS
links
dnl #
dnl define(`confAUTH_OPTIONS', `A p')dnl
dnl #
EATURE(`access_db', `hash -T<TMPF> -o /
FEATURE(`blacklist_recipients')dnl
EXPOSED_USER(`root')dnl
dnl #
dnl # For using Cyrus-IMAPd as POP3/IMAP server through LMTP
delivery uncomment
dnl # the following 2 definitions and activate below in the
MAILER section the
dnl # cyrusv2 mailer.
dnl #
dnl define(`confLOCAL_MAILER', `cyrusv2')dnl
dnl define(`CYRUSV2_MAILER_ARGS', `FILE
/var/lib/imap/socket/lmtp')dnl
dnl #
dnl # The following causes sendmail to only listen on the
IPv4 loopback address
dnl # 127.0.0.1 and not on any other network devices. Remove
the loopback
dnl # address restriction to accept email from the internet
or intranet.
dnl #
dnl DAEMON_OPTIONS(`Port=smtp,Addr=0.0.0.0, Name=MTA')dnl
dnl #
dnl # The following causes sendmail to additionally listen
to port 587 for
dnl # mail from MUAs that authenticate. Roaming users who
can't reach their
dnl # preferred sendmail daemon due to port 25 being blocked
or redirected find
dnl # this useful.
dnl #
dnl DAEMON_OPTIONS(`Port=submission, Name=MSA, M=Ea')dnl
dnl #
dnl # The following causes sendmail to additionally listen
to port 465, but
dnl # starting immediately in TLS mode upon connecting. Port
25 or 587 followed
dnl # by STARTTLS is preferred, but roaming clients using
Outlook Express can't
dnl # do STARTTLS on ports other than 25. Mozilla Mail can
ONLY use STARTTLS
dnl # and doesn't support the deprecated smtps; Evolution
<1.1.1 uses smtps
dnl # when SSL is enabled-- STARTTLS support is available in
version 1.1.1.
dnl #
dnl # For this to work your OpenSSL certificates must be
configured.
dnl #
dnl DAEMON_OPTIONS(`Port=smtps, Name=TLSMTA, M=s')dnl
dnl #
dnl # The following causes sendmail to additionally listen
on the IPv6 loopback
dnl # device. Remove the loopback address restriction listen
to the network.
dnl #
dnl DAEMON_OPTIONS(`port=smtp,Addr=::1, Name=MTA-v6,
Family=inet6')dnl
dnl #
dnl # enable both ipv6 and ipv4 in sendmail:
dnl #
dnl DAEMON_OPTIONS(`Name=MTA-v4, Family=inet, Name=MTA-v6,
Family=inet6')
dnl #
dnl # We strongly recommend not accepting unresolvable
domains if you want to
dnl # protect yourself from spam. However, the laptop and
users on computers
dnl # that do not have 24x7 DNS do need this.
FEATURE(`accept_unresolvable_domains')dnl
dnl #
dnl FEATURE(`relay_based_on_MX')dnl
dnl #
dnl # Also accept email sent to "localhost.localdomain" as
local email.
dnl #
LOCAL_DOMAIN(`localhost.localdomain')dnl
dnl #
dnl # The following example makes mail from this host and
any additional
dnl # specified domains appear to be sent from mydomain.com
dnl #
dnl MASQUERADE_AS(`mydomain.com')dnl
dnl #
dnl # masquerade not just the headers, but the envelope as
well
dnl #
dnl FEATURE(masquerade_envelope)dnl
dnl #
dnl # masquerade not just @mydomainalias.com, but
@*.mydomainalias.com as well
dnl #
dnl FEATURE(masquerade_entire_domain)dnl
dnl #
dnl MASQUERADE_DOMAIN(localhost)dnl
dnl MASQUERADE_DOMAIN(localhost.localdomain)dnl
dnl MASQUERADE_DOMAIN(mydomainalias.com)dnl
dnl MASQUERADE_DOMAIN(mydomain.lan)dnl
MAILER(smtp)dnl
MAILER(procmail)dnl
dnl MAILER(cyrusv2)dnl
#
# Configured by sipX PBX: sipxpbx 4.4.0
define(`confMCI_CACHE_TIMEOUT', `1m')dnl
define(`confTO_INITIAL', `1m')dnl
define(`confTO_CONNECT', `1m')dnl
define(`confTO_ACONNECT', `1m')dnl
define(`confTO_HELO', `1m')dnl
define(`confTO_MAIL', `1m')dnl
define(`confTO_RCPT', `1m')dnl
define(`confTO_DATAINIT', `1m')dnl
define(`confTO_DATABLOCK', `1m')dnl
define(`confTO_DATAFINAL', `1m')dnl
define(`confTO_RSET', `1m')dnl
define(`confTO_QUIT', `1m')dnl
define(`confTO_MISC', `1m')dnl
define(`confTO_COMMAND', `1m')dnl
define(`confTO_IDENT', `1m')dnl
define(`confTO_FILEOPEN', `1m')dnl
define(`confTO_LHLO', `1m')dnl
define(`confTO_AUTH', `1m')dnl
define(`confTO_STARTTLS', `1m')dnl
define(`confTO_CONTROL', `1m')dnl
define(`confTO_QUEUERETURN', `1d')dnl
define(`confTO_QUEUERETURN_DSN', `1h')dnl
define(`confTO_QUEUEWARN', `2d')dnl


--
Tommy Laino
Dome Technologies
Tony Graziano
2012-10-30 19:27:08 UTC
Permalink
The line wrapping looks weird, like it was touched in a cli editor that was
set too narrow, the line wraps should not be there. I don't see the config
lines automatically inserted by sipx in there either. I think if you were
to open it in text editor that would show you wrapped lines and fix that,
while making sure the sipx generated lines were in there (they are not),
you would be able to fix it using the typical sendmail commands to rebuild
m4 and then restart the sendmail server.



On Tue, Oct 30, 2012 at 3:20 PM, Tommy Laino <***@gmail.com> wrote:

>
>
> Tony I checked to see if postfix or someother MTA is running
> or installed and so far it appears that only sendmail is
> installed. It was installed out of the box when I installed
> 4.4 through ISO. I have made no changes to the config file
> for sendmail. Here it is
>
> dnl # The -t option will retry delivery if e.g. the user
> runs over his quota.
> dnl #
> FEATURE(local_procmail, `', `procmail -t -Y -a $h -d
> $u')dnl
> Fs is the sendmail macro config file for m4. If you make
> changes to
> dnl # /etc/mail/sendmail.mc, you will need to regenerate
> the
> dnl # /etc/mail/sendmail.cf file by confirming that the
> sendmail-cf package is
> dnl # installed and then performing a
> dnl #
> dnl # make -C /etc/mail
> dnl #
> include(`/usr/share/sendmail-cf/m4/cf.m4')dnl
> VERSIONID(`setup for linux')dnl
> OSTYPE(`linux')dnl
> dnl #
> dnl # Do not advertize sendmail version.
> dnl #
> dnl define(`confSMTP_LOGIN_MSG', `$j Sendmail; $b')dnl
> dnl #
> dnl # default logging level is 9, you might want to set it
> higher to
> dnl # debug the configuration
> dnl #
> dnl define(`confLOG_LEVEL', `9')dnl
> dnl #
> dnl # Uncomment and edit the following line if your outgoing
> mail needs to
> dnl # be sent out through an external mail server:
> dnl #
> dnl define(`SMART_HOST', `smtp.your.provider')dnl
> dnl #
> define(`confDEF_USER_ID', ``8:12'')dnl
> dnl define(`confAUTO_REBUILD')dnl
> define(`confTRY_NULL_MX_LIST', `True')dnl
> define(`confDONT_PROBE_INTERFACES', `True')dnl
> define(`PROCMAIL_MAILER_PATH', `/usr/bin/procmail')dnl
> define(`ALIAS_FILE', `/etc/aliases')dnl
> define(`STATUS_FILE', `/var/log/mail/statistics')dnl
> define(`UUCP_MAILER_MAX', `2000000')dnl
> define(`confUSERDB_SPEC', `/etc/mail/userdb.db')dnl
> define(`confPRIVACY_FLAGS',
> `authwarnings,novrfy,noexpn,restrictqrun')dnl
> define(`confAUTH_OPTIONS', `A')dnl
> dnl #
> dnl # The following allows relaying if the user
> authenticates, and disallows
> dnl # plaintext authentication (PLAIN/LOGIN) on non-TLS
> links
> dnl #
> dnl define(`confAUTH_OPTIONS', `A p')dnl
> dnl #
> EATURE(`access_db', `hash -T<TMPF> -o /
> FEATURE(`blacklist_recipients')dnl
> EXPOSED_USER(`root')dnl
> dnl #
> dnl # For using Cyrus-IMAPd as POP3/IMAP server through LMTP
> delivery uncomment
> dnl # the following 2 definitions and activate below in the
> MAILER section the
> dnl # cyrusv2 mailer.
> dnl #
> dnl define(`confLOCAL_MAILER', `cyrusv2')dnl
> dnl define(`CYRUSV2_MAILER_ARGS', `FILE
> /var/lib/imap/socket/lmtp')dnl
> dnl #
> dnl # The following causes sendmail to only listen on the
> IPv4 loopback address
> dnl # 127.0.0.1 and not on any other network devices. Remove
> the loopback
> dnl # address restriction to accept email from the internet
> or intranet.
> dnl #
> dnl DAEMON_OPTIONS(`Port=smtp,Addr=0.0.0.0, Name=MTA')dnl
> dnl #
> dnl # The following causes sendmail to additionally listen
> to port 587 for
> dnl # mail from MUAs that authenticate. Roaming users who
> can't reach their
> dnl # preferred sendmail daemon due to port 25 being blocked
> or redirected find
> dnl # this useful.
> dnl #
> dnl DAEMON_OPTIONS(`Port=submission, Name=MSA, M=Ea')dnl
> dnl #
> dnl # The following causes sendmail to additionally listen
> to port 465, but
> dnl # starting immediately in TLS mode upon connecting. Port
> 25 or 587 followed
> dnl # by STARTTLS is preferred, but roaming clients using
> Outlook Express can't
> dnl # do STARTTLS on ports other than 25. Mozilla Mail can
> ONLY use STARTTLS
> dnl # and doesn't support the deprecated smtps; Evolution
> <1.1.1 uses smtps
> dnl # when SSL is enabled-- STARTTLS support is available in
> version 1.1.1.
> dnl #
> dnl # For this to work your OpenSSL certificates must be
> configured.
> dnl #
> dnl DAEMON_OPTIONS(`Port=smtps, Name=TLSMTA, M=s')dnl
> dnl #
> dnl # The following causes sendmail to additionally listen
> on the IPv6 loopback
> dnl # device. Remove the loopback address restriction listen
> to the network.
> dnl #
> dnl DAEMON_OPTIONS(`port=smtp,Addr=::1, Name=MTA-v6,
> Family=inet6')dnl
> dnl #
> dnl # enable both ipv6 and ipv4 in sendmail:
> dnl #
> dnl DAEMON_OPTIONS(`Name=MTA-v4, Family=inet, Name=MTA-v6,
> Family=inet6')
> dnl #
> dnl # We strongly recommend not accepting unresolvable
> domains if you want to
> dnl # protect yourself from spam. However, the laptop and
> users on computers
> dnl # that do not have 24x7 DNS do need this.
> FEATURE(`accept_unresolvable_domains')dnl
> dnl #
> dnl FEATURE(`relay_based_on_MX')dnl
> dnl #
> dnl # Also accept email sent to "localhost.localdomain" as
> local email.
> dnl #
> LOCAL_DOMAIN(`localhost.localdomain')dnl
> dnl #
> dnl # The following example makes mail from this host and
> any additional
> dnl # specified domains appear to be sent from mydomain.com
> dnl #
> dnl MASQUERADE_AS(`mydomain.com')dnl
> dnl #
> dnl # masquerade not just the headers, but the envelope as
> well
> dnl #
> dnl FEATURE(masquerade_envelope)dnl
> dnl #
> dnl # masquerade not just @mydomainalias.com, but
> @*.mydomainalias.com as well
> dnl #
> dnl FEATURE(masquerade_entire_domain)dnl
> dnl #
> dnl MASQUERADE_DOMAIN(localhost)dnl
> dnl MASQUERADE_DOMAIN(localhost.localdomain)dnl
> dnl MASQUERADE_DOMAIN(mydomainalias.com)dnl
> dnl MASQUERADE_DOMAIN(mydomain.lan)dnl
> MAILER(smtp)dnl
> MAILER(procmail)dnl
> dnl MAILER(cyrusv2)dnl
> #
> # Configured by sipX PBX: sipxpbx 4.4.0
> define(`confMCI_CACHE_TIMEOUT', `1m')dnl
> define(`confTO_INITIAL', `1m')dnl
> define(`confTO_CONNECT', `1m')dnl
> define(`confTO_ACONNECT', `1m')dnl
> define(`confTO_HELO', `1m')dnl
> define(`confTO_MAIL', `1m')dnl
> define(`confTO_RCPT', `1m')dnl
> define(`confTO_DATAINIT', `1m')dnl
> define(`confTO_DATABLOCK', `1m')dnl
> define(`confTO_DATAFINAL', `1m')dnl
> define(`confTO_RSET', `1m')dnl
> define(`confTO_QUIT', `1m')dnl
> define(`confTO_MISC', `1m')dnl
> define(`confTO_COMMAND', `1m')dnl
> define(`confTO_IDENT', `1m')dnl
> define(`confTO_FILEOPEN', `1m')dnl
> define(`confTO_LHLO', `1m')dnl
> define(`confTO_AUTH', `1m')dnl
> define(`confTO_STARTTLS', `1m')dnl
> define(`confTO_CONTROL', `1m')dnl
> define(`confTO_QUEUERETURN', `1d')dnl
> define(`confTO_QUEUERETURN_DSN', `1h')dnl
> define(`confTO_QUEUEWARN', `2d')dnl
>
>
> --
> Tommy Laino
> Dome Technologies
> _______________________________________________
> sipx-users mailing list
> sipx-***@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>



--
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: ***@voice.myitdepartment.net
Fax: 434.465.6833
~~~~~~~~~~~~~~~~~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~

Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
2013!
<http://sipxcolab2013.eventbrite.com/?discount=tony2013>

--
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: ***@voice.myitdepartment.net

Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net
Tommy Laino
2012-10-30 19:59:26 UTC
Permalink
I will give that a shot. If I create a new file and add the
missing lines and fix the line breaks how to do I go about
uploading it to the server? Sorry if thats a rookie question
but Im still learning the whole sendmail and linux command
line programming stuff.
--
Tommy Laino
Dome Technologies
Tommy Laino
2012-10-30 20:40:49 UTC
Permalink
Yes the email that I am using to send is the same as my SIP
domain. I am using Network Solutions for the domain hosting.
--
Tommy Laino
Dome Technologies
Michael Picher
2012-10-30 20:40:34 UTC
Permalink
Ok so Tommy... lets say your sipXecs server is in domain xyz.com and has
an authoritative dns server for that domain but has no MX records in it...

Now lets say that this same server wants to send mail to xyz.com. So it
does an mx record lookup for xyz.com and do you think it will find a mail
server?

So, look at the mx records you have at network solutions. Replicate the mx
records and the corresponding A records into your zone file (located in
/var/named/ ). When you're done, restart named (service named restart) and
if you haven't muffed the file format named will start.

Voila... DNS magic.

Mike

On Tue, Oct 30, 2012 at 4:40 PM, Tommy Laino <***@gmail.com> wrote:

>
>
> Yes the email that I am using to send is the same as my SIP
> domain. I am using Network Solutions for the domain hosting.
> --
> Tommy Laino
> Dome Technologies
> _______________________________________________
> sipx-users mailing list
> sipx-***@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>



--
Michael Picher, Director of Technical Services
eZuce, Inc.

300 Brickstone Square****

Suite 201****

Andover, MA. 01810
O.978-296-1005 X2015
M.207-956-0262
@mpicher <http://twitter.com/mpicher>
linkedin <http://www.linkedin.com/profile/view?id=35504760&trk=tab_pro>
www.ezuce.com

------------------------------------------------------------------------------------------------------------
There are 10 kinds of people in the world, those who understand binary and
those who don't.
Tommy Laino
2012-10-30 21:07:48 UTC
Permalink
Sounds simple. I will give it a shot. Thanks guys
--
Tommy Laino
Dome Technologies
Tommy Laino
2012-11-06 21:31:58 UTC
Permalink
Mike,
When I enter the command to edit the file /var/named/ I get
an error that says "Illegal File Name". I am not totally
sure I understand what is not working here.

Also, I did a fresh install on a new machine and tested it
and it does not work there either. Sorry If I am asking
silly questions or if I am missing something here that I
should know but I am learning this all on my own with a
limited background in mostly propietary IP phone systems.
--
Tommy Laino
Dome Technologies
Tony Graziano
2012-11-06 21:31:31 UTC
Permalink
That's the directory. There is a file there "sip domain.zone". You need to
edit the appropriate zone file in that directory.

Good luck.
On Nov 6, 2012 4:24 PM, "Tommy Laino" <***@gmail.com> wrote:

>
>
> Mike,
> When I enter the command to edit the file /var/named/ I get
> an error that says "Illegal File Name". I am not totally
> sure I understand what is not working here.
>
> Also, I did a fresh install on a new machine and tested it
> and it does not work there either. Sorry If I am asking
> silly questions or if I am missing something here that I
> should know but I am learning this all on my own with a
> limited background in mostly propietary IP phone systems.
> --
> Tommy Laino
> Dome Technologies
> _______________________________________________
> sipx-users mailing list
> sipx-***@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>

--
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: ***@voice.myitdepartment.net

Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net
Tommy Laino
2012-11-06 22:06:33 UTC
Permalink
OK I found the file. I see an area that shows "IP Addresses"
and below it it shows "www.mydomain.com IN A
192.yyy.zzz.222". What should the line for my MX record look
like?
--
Tommy Laino
Dome Technologies
Michael Picher
2012-11-06 22:11:22 UTC
Permalink
google is your friend.


On Tue, Nov 6, 2012 at 5:06 PM, Tommy Laino <***@gmail.com> wrote:

>
>
> OK I found the file. I see an area that shows "IP Addresses"
> and below it it shows "www.mydomain.com IN A
> 192.yyy.zzz.222". What should the line for my MX record look
> like?
> --
> Tommy Laino
> Dome Technologies
> _______________________________________________
> sipx-users mailing list
> sipx-***@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>



--
Michael Picher, Director of Technical Services
eZuce, Inc.

300 Brickstone Square****

Suite 201****

Andover, MA. 01810
O.978-296-1005 X2015
M.207-956-0262
@mpicher <http://twitter.com/mpicher>
linkedin <http://www.linkedin.com/profile/view?id=35504760&trk=tab_pro>
www.ezuce.com

------------------------------------------------------------------------------------------------------------
There are 10 kinds of people in the world, those who understand binary and
those who don't.
Tommy Laino
2012-11-07 04:34:29 UTC
Permalink
So I added my MX records and A records in my zone file. But
when I try to telnet mydomain.com 25 I get that the
connection is refused by 127.0.0.1 still. Tried the same
thing on my new server and its not working either. Did some
other research on Google and cant seem to find why this is
happening.
--
Tommy Laino
Dome Technologies
m***@mattkeys.net
2012-11-07 06:20:26 UTC
Permalink
You said your SIP domain is the same as your email domain, and that your DNS is hosted at Network Solutions. This is likely the issue and not a problem with sendmail unless you've borked the default configs. Sendmail in that use case would be used to deliver the email and not to receive it.

There are lots of reasons why sendmail wouldn't be able to deliver email but that discussion is outside the scope for a sipxecs mailing list. Verify easily that sendmail is working in the first place by using an alternate email address for the below test with a known good address like gmail, yahoo, etc.

$ echo "testing 123" | mail -s "sipx email test" ***@gmail.com && tail -f /var/log/maillog

You should see successful delivery in the mail log (press ctrl-c to stop tailing it), and within a few seconds or minutes the email should arrive in your inbox. Be sure to check your junk mail folders for the email if you don't spot it quickly. If you have successful delivery of the test email then sendmail is working just fine and it's a local DNS issue. To verify this is the case (replace example.com with your real domain) :

$ dig @localhost mx example.com

then compare against what the rest of the world has for your MX by using an outside DNS such as Google :

$ dig @8.8.8.8 mx example.com

If they don't match you'll need to edit your zone file, correct the MX record, then restart BIND.

$ service named restart

Repeat the dig test to verify they're the same now. You may want to consider the use of the smart_host config option of sendmail. To do so your "real" email server will need to allow mail relay from your sipx box. Optionally you could reconfigure sipx to use a different SIP domain all together or a subdomain of your real domain (voice.example.com instead of example.com).

HTH,
Matt
________________________________________
From: sipx-users-***@list.sipfoundry.org [sipx-users-***@list.sipfoundry.org] On Behalf Of Tommy Laino [***@gmail.com]
Sent: Tuesday, November 06, 2012 11:34 PM
To: sipx-***@list.sipfoundry.org
Subject: Re: [sipx-users] Sendmail Issue

So I added my MX records and A records in my zone file. But
when I try to telnet mydomain.com 25 I get that the
connection is refused by 127.0.0.1 still. Tried the same
thing on my new server and its not working either. Did some
other research on Google and cant seem to find why this is
happening.
--
Tommy Laino
Dome Technologies
Todd Hodgen
2012-11-07 06:41:32 UTC
Permalink
I've not been following this thread, but will add some comments as they
relate to email not being deliverable outbound via sipxecs. If this is DNS
related - this response doesn't touch that.

I find it useful in v4.4 to add the Emailformats.properties files to
sipxecs.
http://wiki.sipfoundry.org/display/sipXecs/Voicemail-Email+Custom+Notificati
ons It will allow you to set the Sent from email address to one that is
acceptable to the your SMTP gateway.

After installing the sample, and changing your from address, do a "service
sendmail restart", and do a restart of sipxconfig.

Looking at var/log/maillog can give you some clues as to why it is not being
delivered. Pay attention to the to and from address, the DNS codes give
some great google clues as well.

-----Original Message-----
From: sipx-users-***@list.sipfoundry.org
[mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of
***@mattkeys.net
Sent: Tuesday, November 06, 2012 10:20 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Sendmail Issue

You said your SIP domain is the same as your email domain, and that your DNS
is hosted at Network Solutions. This is likely the issue and not a problem
with sendmail unless you've borked the default configs. Sendmail in that use
case would be used to deliver the email and not to receive it.

There are lots of reasons why sendmail wouldn't be able to deliver email but
that discussion is outside the scope for a sipxecs mailing list. Verify
easily that sendmail is working in the first place by using an alternate
email address for the below test with a known good address like gmail,
yahoo, etc.

$ echo "testing 123" | mail -s "sipx email test" ***@gmail.com
&& tail -f /var/log/maillog

You should see successful delivery in the mail log (press ctrl-c to stop
tailing it), and within a few seconds or minutes the email should arrive in
your inbox. Be sure to check your junk mail folders for the email if you
don't spot it quickly. If you have successful delivery of the test email
then sendmail is working just fine and it's a local DNS issue. To verify
this is the case (replace example.com with your real domain) :

$ dig @localhost mx example.com

then compare against what the rest of the world has for your MX by using an
outside DNS such as Google :

$ dig @8.8.8.8 mx example.com

If they don't match you'll need to edit your zone file, correct the MX
record, then restart BIND.

$ service named restart

Repeat the dig test to verify they're the same now. You may want to consider
the use of the smart_host config option of sendmail. To do so your "real"
email server will need to allow mail relay from your sipx box. Optionally
you could reconfigure sipx to use a different SIP domain all together or a
subdomain of your real domain (voice.example.com instead of example.com).

HTH,
Matt
________________________________________
From: sipx-users-***@list.sipfoundry.org
[sipx-users-***@list.sipfoundry.org] On Behalf Of Tommy Laino
[***@gmail.com]
Sent: Tuesday, November 06, 2012 11:34 PM
To: sipx-***@list.sipfoundry.org
Subject: Re: [sipx-users] Sendmail Issue

So I added my MX records and A records in my zone file. But when I try to
telnet mydomain.com 25 I get that the connection is refused by 127.0.0.1
still. Tried the same thing on my new server and its not working either. Did
some other research on Google and cant seem to find why this is happening.
--
Tommy Laino
Dome Technologies
_______________________________________________
sipx-users mailing list
sipx-***@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
Tommy Laino
2012-11-08 01:25:18 UTC
Permalink
Matt thanks for the in depth testing. I changed the zone
file to match what I am getting from the Google DNS servers.
When I look at the logs I am getting the connection was
refused on 127.0.0.1.

Todd that file is not on the system so I will have to build
it and give that a shot.
--
Tommy Laino
Dome Technologies
Tommy Laino
2012-11-08 01:28:01 UTC
Permalink
I just had a thought that had not occured to me until just
now. Verizon FiOS in this area blocks port 25. All my
outbound mail servers use port 587. How do I change the port
that SipX sends mail out on? That may fix my issue
--
Tommy Laino
Dome Technologies
Tony Graziano
2012-11-08 01:22:54 UTC
Permalink
Ugh.

http://www.sendmail.org/~gshapiro/8.10.Training/DaemonPortOptions.html
On Nov 7, 2012 8:20 PM, "Tommy Laino" <***@gmail.com> wrote:

>
>
> I just had a thought that had not occured to me until just
> now. Verizon FiOS in this area blocks port 25. All my
> outbound mail servers use port 587. How do I change the port
> that SipX sends mail out on? That may fix my issue
> --
> Tommy Laino
> Dome Technologies
> _______________________________________________
> sipx-users mailing list
> sipx-***@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>

--
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: ***@voice.myitdepartment.net

Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net
Tommy Laino
2012-11-08 02:11:31 UTC
Permalink
OK I found an extra line in my sendmail.cf file. I went back
and tested again and the test email went through and I got a
message that it was accepted for delivery. But Im getting a
message that the connection timed out to the gmail server.
If I am understanding what is going correctly I am having an
issue with the hosting provider.
--
Tommy Laino
Dome Technologies
m***@mattkeys.net
2012-11-08 04:09:43 UTC
Permalink
Don't change the daemon port options as that changes what sendmail *listens* to. You should only be concerned with delivery for this particular issue and not receiving. If you want your sipxecs box to be your domain's email server that's a different story. Verizon FiOS is probably only restricting *inbound* tcp 25 so you can't run a mail server on their service. This is a normal practice and shouldn't be an issue. If they were blocking outbound 25 that would prevent email clients from sending mail and would be a much bigger deal. You can verify that you're making it to the remote smtp service by using telnet ... :

$ telnet smtp.example.com 25
Trying 192.0.2.2...
Connected to smtp.example.com.
Escape character is '^]'.
220 smtp.example.com ESMTP server ready Tue, 20 Jan 2004 22:33:36 +0200
HELO client.example.com
250 smtp.example.com
MAIL from: <***@example.com>
250 Sender <***@example.com> Ok
RCPT to: <***@example.com>
250 Recipient <***@example.com> Ok
DATA
354 Ok Send data ending with <CRLF>.<CRLF>
From: ***@example.com
To: ***@example.com
Subject: Test message
This is a test message.
.
250 Message received: ***@client.example.com
QUIT
221 mx1.example.com ESMTP server closing connection

Again there are a number of reasons why delivery can fail. For example, your network administrator may restrict outbound smtp to only specific IP addresses... or your SPF records may be incomplete (missing a entry for your sipxecs box) and Gmail is rejecting the host due to a lookup failure... etc. There's just too many variables for me to guess at without knowing your environment. Do you have a network administrator that can help you out?

HTH,
Matt
________________________________________
From: sipx-users-***@list.sipfoundry.org [sipx-users-***@list.sipfoundry.org] On Behalf Of Tommy Laino [***@gmail.com]
Sent: Wednesday, November 07, 2012 9:11 PM
To: sipx-***@list.sipfoundry.org
Subject: Re: [sipx-users] Sendmail Issue

OK I found an extra line in my sendmail.cf file. I went back
and tested again and the test email went through and I got a
message that it was accepted for delivery. But Im getting a
message that the connection timed out to the gmail server.
If I am understanding what is going correctly I am having an
issue with the hosting provider.
--
Tommy Laino
Dome Technologies
Todd Hodgen
2012-11-08 08:10:06 UTC
Permalink
There is a sample provided in the like I had sent. Copy and paste it,
that's all you really need to do, and then change the from field to your
own.

-----Original Message-----
From: sipx-users-***@list.sipfoundry.org
[mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of Tommy Laino
Sent: Wednesday, November 07, 2012 5:25 PM
To: sipx-***@list.sipfoundry.org
Subject: Re: [sipx-users] Sendmail Issue



Matt thanks for the in depth testing. I changed the zone file to match what
I am getting from the Google DNS servers.
When I look at the logs I am getting the connection was refused on
127.0.0.1.

Todd that file is not on the system so I will have to build it and give that
a shot.
--
Tommy Laino
Dome Technologies
Michael Picher
2012-10-30 19:53:27 UTC
Permalink
silly question (not really if you know dns) but is your sip domain the same
as your email domain? if so you might just need to do a little dns record
work in your zone file.

On Tue, Oct 30, 2012 at 3:27 PM, Tony Graziano <***@myitdepartment.net
> wrote:

> The line wrapping looks weird, like it was touched in a cli editor that
> was set too narrow, the line wraps should not be there. I don't see the
> config lines automatically inserted by sipx in there either. I think if you
> were to open it in text editor that would show you wrapped lines and fix
> that, while making sure the sipx generated lines were in there (they are
> not), you would be able to fix it using the typical sendmail commands to
> rebuild m4 and then restart the sendmail server.
>
>
>
> On Tue, Oct 30, 2012 at 3:20 PM, Tommy Laino <***@gmail.com> wrote:
>
>>
>>
>> Tony I checked to see if postfix or someother MTA is running
>> or installed and so far it appears that only sendmail is
>> installed. It was installed out of the box when I installed
>> 4.4 through ISO. I have made no changes to the config file
>> for sendmail. Here it is
>>
>> dnl # The -t option will retry delivery if e.g. the user
>> runs over his quota.
>> dnl #
>> FEATURE(local_procmail, `', `procmail -t -Y -a $h -d
>> $u')dnl
>> Fs is the sendmail macro config file for m4. If you make
>> changes to
>> dnl # /etc/mail/sendmail.mc, you will need to regenerate
>> the
>> dnl # /etc/mail/sendmail.cf file by confirming that the
>> sendmail-cf package is
>> dnl # installed and then performing a
>> dnl #
>> dnl # make -C /etc/mail
>> dnl #
>> include(`/usr/share/sendmail-cf/m4/cf.m4')dnl
>> VERSIONID(`setup for linux')dnl
>> OSTYPE(`linux')dnl
>> dnl #
>> dnl # Do not advertize sendmail version.
>> dnl #
>> dnl define(`confSMTP_LOGIN_MSG', `$j Sendmail; $b')dnl
>> dnl #
>> dnl # default logging level is 9, you might want to set it
>> higher to
>> dnl # debug the configuration
>> dnl #
>> dnl define(`confLOG_LEVEL', `9')dnl
>> dnl #
>> dnl # Uncomment and edit the following line if your outgoing
>> mail needs to
>> dnl # be sent out through an external mail server:
>> dnl #
>> dnl define(`SMART_HOST', `smtp.your.provider')dnl
>> dnl #
>> define(`confDEF_USER_ID', ``8:12'')dnl
>> dnl define(`confAUTO_REBUILD')dnl
>> define(`confTRY_NULL_MX_LIST', `True')dnl
>> define(`confDONT_PROBE_INTERFACES', `True')dnl
>> define(`PROCMAIL_MAILER_PATH', `/usr/bin/procmail')dnl
>> define(`ALIAS_FILE', `/etc/aliases')dnl
>> define(`STATUS_FILE', `/var/log/mail/statistics')dnl
>> define(`UUCP_MAILER_MAX', `2000000')dnl
>> define(`confUSERDB_SPEC', `/etc/mail/userdb.db')dnl
>> define(`confPRIVACY_FLAGS',
>> `authwarnings,novrfy,noexpn,restrictqrun')dnl
>> define(`confAUTH_OPTIONS', `A')dnl
>> dnl #
>> dnl # The following allows relaying if the user
>> authenticates, and disallows
>> dnl # plaintext authentication (PLAIN/LOGIN) on non-TLS
>> links
>> dnl #
>> dnl define(`confAUTH_OPTIONS', `A p')dnl
>> dnl #
>> EATURE(`access_db', `hash -T<TMPF> -o /
>> FEATURE(`blacklist_recipients')dnl
>> EXPOSED_USER(`root')dnl
>> dnl #
>> dnl # For using Cyrus-IMAPd as POP3/IMAP server through LMTP
>> delivery uncomment
>> dnl # the following 2 definitions and activate below in the
>> MAILER section the
>> dnl # cyrusv2 mailer.
>> dnl #
>> dnl define(`confLOCAL_MAILER', `cyrusv2')dnl
>> dnl define(`CYRUSV2_MAILER_ARGS', `FILE
>> /var/lib/imap/socket/lmtp')dnl
>> dnl #
>> dnl # The following causes sendmail to only listen on the
>> IPv4 loopback address
>> dnl # 127.0.0.1 and not on any other network devices. Remove
>> the loopback
>> dnl # address restriction to accept email from the internet
>> or intranet.
>> dnl #
>> dnl DAEMON_OPTIONS(`Port=smtp,Addr=0.0.0.0, Name=MTA')dnl
>> dnl #
>> dnl # The following causes sendmail to additionally listen
>> to port 587 for
>> dnl # mail from MUAs that authenticate. Roaming users who
>> can't reach their
>> dnl # preferred sendmail daemon due to port 25 being blocked
>> or redirected find
>> dnl # this useful.
>> dnl #
>> dnl DAEMON_OPTIONS(`Port=submission, Name=MSA, M=Ea')dnl
>> dnl #
>> dnl # The following causes sendmail to additionally listen
>> to port 465, but
>> dnl # starting immediately in TLS mode upon connecting. Port
>> 25 or 587 followed
>> dnl # by STARTTLS is preferred, but roaming clients using
>> Outlook Express can't
>> dnl # do STARTTLS on ports other than 25. Mozilla Mail can
>> ONLY use STARTTLS
>> dnl # and doesn't support the deprecated smtps; Evolution
>> <1.1.1 uses smtps
>> dnl # when SSL is enabled-- STARTTLS support is available in
>> version 1.1.1.
>> dnl #
>> dnl # For this to work your OpenSSL certificates must be
>> configured.
>> dnl #
>> dnl DAEMON_OPTIONS(`Port=smtps, Name=TLSMTA, M=s')dnl
>> dnl #
>> dnl # The following causes sendmail to additionally listen
>> on the IPv6 loopback
>> dnl # device. Remove the loopback address restriction listen
>> to the network.
>> dnl #
>> dnl DAEMON_OPTIONS(`port=smtp,Addr=::1, Name=MTA-v6,
>> Family=inet6')dnl
>> dnl #
>> dnl # enable both ipv6 and ipv4 in sendmail:
>> dnl #
>> dnl DAEMON_OPTIONS(`Name=MTA-v4, Family=inet, Name=MTA-v6,
>> Family=inet6')
>> dnl #
>> dnl # We strongly recommend not accepting unresolvable
>> domains if you want to
>> dnl # protect yourself from spam. However, the laptop and
>> users on computers
>> dnl # that do not have 24x7 DNS do need this.
>> FEATURE(`accept_unresolvable_domains')dnl
>> dnl #
>> dnl FEATURE(`relay_based_on_MX')dnl
>> dnl #
>> dnl # Also accept email sent to "localhost.localdomain" as
>> local email.
>> dnl #
>> LOCAL_DOMAIN(`localhost.localdomain')dnl
>> dnl #
>> dnl # The following example makes mail from this host and
>> any additional
>> dnl # specified domains appear to be sent from mydomain.com
>> dnl #
>> dnl MASQUERADE_AS(`mydomain.com')dnl
>> dnl #
>> dnl # masquerade not just the headers, but the envelope as
>> well
>> dnl #
>> dnl FEATURE(masquerade_envelope)dnl
>> dnl #
>> dnl # masquerade not just @mydomainalias.com, but
>> @*.mydomainalias.com as well
>> dnl #
>> dnl FEATURE(masquerade_entire_domain)dnl
>> dnl #
>> dnl MASQUERADE_DOMAIN(localhost)dnl
>> dnl MASQUERADE_DOMAIN(localhost.localdomain)dnl
>> dnl MASQUERADE_DOMAIN(mydomainalias.com)dnl
>> dnl MASQUERADE_DOMAIN(mydomain.lan)dnl
>> MAILER(smtp)dnl
>> MAILER(procmail)dnl
>> dnl MAILER(cyrusv2)dnl
>> #
>> # Configured by sipX PBX: sipxpbx 4.4.0
>> define(`confMCI_CACHE_TIMEOUT', `1m')dnl
>> define(`confTO_INITIAL', `1m')dnl
>> define(`confTO_CONNECT', `1m')dnl
>> define(`confTO_ACONNECT', `1m')dnl
>> define(`confTO_HELO', `1m')dnl
>> define(`confTO_MAIL', `1m')dnl
>> define(`confTO_RCPT', `1m')dnl
>> define(`confTO_DATAINIT', `1m')dnl
>> define(`confTO_DATABLOCK', `1m')dnl
>> define(`confTO_DATAFINAL', `1m')dnl
>> define(`confTO_RSET', `1m')dnl
>> define(`confTO_QUIT', `1m')dnl
>> define(`confTO_MISC', `1m')dnl
>> define(`confTO_COMMAND', `1m')dnl
>> define(`confTO_IDENT', `1m')dnl
>> define(`confTO_FILEOPEN', `1m')dnl
>> define(`confTO_LHLO', `1m')dnl
>> define(`confTO_AUTH', `1m')dnl
>> define(`confTO_STARTTLS', `1m')dnl
>> define(`confTO_CONTROL', `1m')dnl
>> define(`confTO_QUEUERETURN', `1d')dnl
>> define(`confTO_QUEUERETURN_DSN', `1h')dnl
>> define(`confTO_QUEUEWARN', `2d')dnl
>>
>>
>> --
>> Tommy Laino
>> Dome Technologies
>> _______________________________________________
>> sipx-users mailing list
>> sipx-***@list.sipfoundry.org
>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>
>
>
>
> --
> ~~~~~~~~~~~~~~~~~~
> Tony Graziano, Manager
> Telephone: 434.984.8430
> sip: ***@voice.myitdepartment.net
> Fax: 434.465.6833
> ~~~~~~~~~~~~~~~~~~
> Linked-In Profile:
> http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
> Ask about our Internet Fax services!
> ~~~~~~~~~~~~~~~~~~
>
> Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
> 2013!
> <http://sipxcolab2013.eventbrite.com/?discount=tony2013>
>
>
> LAN/Telephony/Security and Control Systems Helpdesk:
> Telephone: 434.984.8426
> sip: ***@voice.myitdepartment.**net<***@voice.myitdepartment.net>
>
> Helpdesk Customers: http://myhelp.myitdepartment.**net<http://myhelp.myitdepartment.net>
> Blog: http://blog.myitdepartment.net
>
> _______________________________________________
> sipx-users mailing list
> sipx-***@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>



--
Michael Picher, Director of Technical Services
eZuce, Inc.

300 Brickstone Square****

Suite 201****

Andover, MA. 01810
O.978-296-1005 X2015
M.207-956-0262
@mpicher <http://twitter.com/mpicher>
linkedin <http://www.linkedin.com/profile/view?id=35504760&trk=tab_pro>
www.ezuce.com

------------------------------------------------------------------------------------------------------------
There are 10 kinds of people in the world, those who understand binary and
those who don't.
Tommy Laino
2012-11-25 03:45:11 UTC
Permalink
Just to update this thread. I took my new instance of
SipXecs to the customer prem to start my install. Setup
their firewall and SipXecs and when I was done I decided to
try to see if sendmail would work their. Sure enough first
try the test mail delivered to my email account and worked
just fine. Tested UM and that worked flawlessly as well

I am assuming that the Actiontec router provided by Verizon
is not working properly. I have all the same ports open on
both firewalls with differing results. I am going to swap
out the router on Monday and see if that fixes my issue.
Thank you for all your help guys
--
Tommy Laino
Dome Technologies
Todd Hodgen
2012-11-25 09:06:13 UTC
Permalink
I suspect your issue is with Verizon, and not the router. They are
blocking your ability to send email through them as an SMTP gateway.

-----Original Message-----
From: sipx-users-***@list.sipfoundry.org
[mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of Tommy Laino
Sent: Saturday, November 24, 2012 7:45 PM
To: sipx-***@list.sipfoundry.org
Subject: Re: [sipx-users] Sendmail Issue



Just to update this thread. I took my new instance of SipXecs to the
customer prem to start my install. Setup their firewall and SipXecs and when
I was done I decided to try to see if sendmail would work their. Sure enough
first try the test mail delivered to my email account and worked just fine.
Tested UM and that worked flawlessly as well

I am assuming that the Actiontec router provided by Verizon is not working
properly. I have all the same ports open on both firewalls with differing
results. I am going to swap out the router on Monday and see if that fixes
my issue.
Thank you for all your help guys
--
Tommy Laino
Dome Technologies
Tony Graziano
2012-11-25 12:46:34 UTC
Permalink
If they are not using any pots or catb services is the actiontec, replace
it since it would be acting simply as an Ethernet router. Good luck!
On Nov 25, 2012 4:06 AM, "Todd Hodgen" <***@frontier.com> wrote:

> I suspect your issue is with Verizon, and not the router. They are
> blocking your ability to send email through them as an SMTP gateway.
>
> -----Original Message-----
> From: sipx-users-***@list.sipfoundry.org
> [mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of Tommy Laino
> Sent: Saturday, November 24, 2012 7:45 PM
> To: sipx-***@list.sipfoundry.org
> Subject: Re: [sipx-users] Sendmail Issue
>
>
>
> Just to update this thread. I took my new instance of SipXecs to the
> customer prem to start my install. Setup their firewall and SipXecs and
> when
> I was done I decided to try to see if sendmail would work their. Sure
> enough
> first try the test mail delivered to my email account and worked just fine.
> Tested UM and that worked flawlessly as well
>
> I am assuming that the Actiontec router provided by Verizon is not working
> properly. I have all the same ports open on both firewalls with differing
> results. I am going to swap out the router on Monday and see if that fixes
> my issue.
> Thank you for all your help guys
> --
> Tommy Laino
> Dome Technologies
> _______________________________________________
> sipx-users mailing list
> sipx-***@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>
> _______________________________________________
> sipx-users mailing list
> sipx-***@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>

--
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: ***@voice.myitdepartment.net

Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net
Loading...