Discussion:
Internal Email
(too old to reply)
Michael Coulton
2014-10-28 21:26:36 UTC
Permalink
Hello
1st let me thank Burkhard Ott for all his help on a previous post of mine. What I'd now like to be able to do is send an email from postfix to an internal email server. Can someone guide me through how I would set this up? Thanks in advance for any help you can give me.

Here is the info:

Ubuntu Server Host File:
127.0.0.1 localhost
127.0.1.1 PBX1
192.168.2.3 mail.azlan.ca
192.168.2.3 ***@azlan.ca


Postfix = 192.168.2.2
Postfix hostname = PBX1
Internal Email Server = 192.168.2.3
FQDN = azlan.ca
sending email to ***@azlan.ca

I've set up a transport file and a transport.db because I read somewhere that I can have an entry of "azlan.ca smtp: 192.168.2.3" and this will force all outgoing mail to the email server. Current the file has a lone entry of "***@azlan.ca 192.268.2.3". I don't think this is correct based on the error log below.

I've tried lots of different configurations and this is my current main.cf

smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination
transport_maps = hash:/etc/potfix/transport
myhostname = mail.azlan.ca
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
myorigin = azlan.ca
mydestination = 192.168.2.3, PBX1, localhost.localdomain, localhost
relayhost =
mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 192.168.2.0/254
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = all
smtp_sasl_auth_enable = yes
smtp_sasl_security_options = noanonymous
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_use_tls = yes
smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt
smtp_destination_recipient_limit = 1024
inet_protocols = all

Error log message

Oct 28 17:24:11 PBX1 postfix/pickup[12121]: EC15D2C0E18: uid=1000 from=<pbx1>
Oct 28 17:24:11 PBX1 postfix/trivial-rewrite[12210]: error: open database /etc/potfix/transport.db: No such file or directory
Oct 28 17:24:11 PBX1 postfix/trivial-rewrite[12210]: warning: hash:/etc/potfix/transport is unavailable. open database /etc/potfix/transport.db: No such file or directory
Oct 28 17:24:11 PBX1 postfix/trivial-rewrite[12210]: warning: hash:/etc/potfix/transport lookup error for "*"
Oct 28 17:24:11 PBX1 postfix/trivial-rewrite[12210]: warning: hash:/etc/potfix/transport is unavailable. open database /etc/potfix/transport.db: No such file or directory
Oct 28 17:24:11 PBX1 postfix/trivial-rewrite[12210]: warning: hash:/etc/potfix/transport lookup error for "*"
Oct 28 17:24:11 PBX1 postfix/cleanup[12209]: EC15D2C0E18: message-id=<***@mail.azlan.ca>
Oct 28 17:24:12 PBX1 postfix/qmgr[12122]: EC15D2C0E18: from=<***@azlan.ca>, size=263, nrcpt=1 (queue active)
Oct 28 17:24:12 PBX1 postfix/trivial-rewrite[12210]: warning: hash:/etc/potfix/transport is unavailable. open database /etc/potfix/transport.db: No such file or directory
Oct 28 17:24:12 PBX1 postfix/trivial-rewrite[12210]: warning: hash:/etc/potfix/transport lookup error for "***@azlan.ca"
Oct 28 17:24:12 PBX1 postfix/trivial-rewrite[12210]: warning: transport_maps lookup failure
Oct 28 17:24:12 PBX1 postfix/error[12211]: EC15D2C0E18: to=<***@azlan.ca>, relay=none, delay=28, delays=28/0.01/0/0.05, dsn=4.3.0, status=deferred (address resolver failure)

re)
Burkhard Ott
2014-10-29 01:29:17 UTC
Permalink
Post by Michael Coulton
hash:/etc/potfix/transport is unavailable. open database
/etc/potfix/transport.db: No such file or directory Oct 28 17:24:12 PBX1
postfix/trivial-rewrite[12210]: warning: hash:/etc/potfix/transport
Have you done a postmap /etc/potfix/transport?
If not do that and exec a postfix reload, after that it shoudl work.

cheers
Michael Coulton
2014-10-29 02:01:17 UTC
Permalink
Post by Burkhard Ott
Post by Michael Coulton
hash:/etc/potfix/transport is unavailable. open database
/etc/potfix/transport.db: No such file or directory Oct 28 17:24:12 PBX1
postfix/trivial-rewrite[12210]: warning: hash:/etc/potfix/transport
Have you done a postmap /etc/potfix/transport?
If not do that and exec a postfix reload, after that it shoudl work.
cheers
Yes, I've created a transport file and the .db but I seem to get an error message. I've tried two addresses listed below. BTW I gave up on the relaying to rogers.com because it was becoming too difficult.

"I've set up a transport file and a transport.db because I read somewhere that I can have an entry of "azlan.ca smtp: 192.168.2.3" and this will force all outgoing mail to the email server. Current the file has a lone entry of "***@azlan.ca 192.268.2.3". I don't think this is correct based on the error log below."

Oct 28 17:24:11 PBX1 postfix/trivial-rewrite[12210]: error: open database /etc/potfix/transport.db: No such file or directory
Oct 28 17:24:11 PBX1 postfix/trivial-rewrite[12210]: warning: hash:/etc/potfix/transport is unavailable. open database /etc/potfix/transport.db: No such file or directory
Oct 28 17:24:11 PBX1 postfix/trivial-rewrite[12210]: warning: hash:/etc/potfix/transport lookup error for "*"
Oct 28 17:24:11 PBX1 postfix/trivial-rewrite[12210]: warning: hash:/etc/potfix/transport is unavailable. open database /etc/potfix/transport.db: No such file or directory
Oct 28 17:24:11 PBX1 postfix/trivial-rewrite[12210]: warning: hash:/etc/potfix/transport lookup error for "*"
Burkhard Ott
2014-10-30 02:10:16 UTC
Permalink
Post by Michael Coulton
Yes, I've created a transport file and the .db but I seem to get an
error message. I've tried two addresses listed below. BTW I gave up on
the relaying to rogers.com because it was becoming too difficult.
"I've set up a transport file and a transport.db because I read
somewhere that I can have an entry of "azlan.ca smtp: 192.168.2.3" and
this will force all outgoing mail to the email server. Current the file
is correct based on the error log below."
Oct 28 17:24:11 PBX1 postfix/trivial-rewrite[12210]: error: open
database /etc/potfix/transport.db: No such file or directory Oct 28
hash:/etc/potfix/transport is unavailable. open database
/etc/potfix/transport.db: No such file or directory Oct 28 17:24:11 PBX1
postfix/trivial-rewrite[12210]: warning: hash:/etc/potfix/transport
lookup error for "*"
hash:/etc/potfix/transport is unavailable. open database
/etc/potfix/transport.db: No such file or directory Oct 28 17:24:11 PBX1
postfix/trivial-rewrite[12210]: warning: hash:/etc/potfix/transport
lookup error for "*"
You could try /etc/postfix/transport instead of potfix :).

Why is it complicated with roger, sure crappy service, but it's not
complicated. If you need to authenticate there see: http://
www.clearfoundation.com/docs/howtos/smtp_authentication_to_isp
Was the first hit via google.

cheers
Michael Coulton
2014-10-30 04:08:13 UTC
Permalink
Post by Burkhard Ott
Post by Michael Coulton
Yes, I've created a transport file and the .db but I seem to get an
error message. I've tried two addresses listed below. BTW I gave up on
the relaying to rogers.com because it was becoming too difficult.
"I've set up a transport file and a transport.db because I read
somewhere that I can have an entry of "azlan.ca smtp: 192.168.2.3" and
this will force all outgoing mail to the email server. Current the file
is correct based on the error log below."
Oct 28 17:24:11 PBX1 postfix/trivial-rewrite[12210]: error: open
database /etc/potfix/transport.db: No such file or directory Oct 28
hash:/etc/potfix/transport is unavailable. open database
/etc/potfix/transport.db: No such file or directory Oct 28 17:24:11 PBX1
postfix/trivial-rewrite[12210]: warning: hash:/etc/potfix/transport
lookup error for "*"
hash:/etc/potfix/transport is unavailable. open database
/etc/potfix/transport.db: No such file or directory Oct 28 17:24:11 PBX1
postfix/trivial-rewrite[12210]: warning: hash:/etc/potfix/transport
lookup error for "*"
You could try /etc/postfix/transport instead of potfix :).
Why is it complicated with roger, sure crappy service, but it's not
complicated. If you need to authenticate there see: http://
www.clearfoundation.com/docs/howtos/smtp_authentication_to_isp
Was the first hit via google.
cheers
Hello
Yea.... I found "potfix" and changed it to "postfix", recreated the transport.db file, reloaded postfix and now get the following error:

status=deferred (mail transport unavailable)

Is this a permissions failure?
Thanks
Burkhard Ott
2014-10-31 01:18:56 UTC
Permalink
Post by Michael Coulton
status=deferred (mail transport unavailable)
Is this a permissions failure?
Can you post a few more lines from the log? Deffered is usually only a
temp. issue, there is still something not correct.

cheers
Michael Coulton
2014-10-31 02:56:38 UTC
Permalink
Post by Burkhard Ott
Post by Michael Coulton
status=deferred (mail transport unavailable)
Is this a permissions failure?
Can you post a few more lines from the log? Deffered is usually only a
temp. issue, there is still something not correct.
cheers
Hope this helps. Thanks

Oct 30 22:22:28 PBX1 postfix/qmgr[14511]: 560DE2C0ACC: from=<***@azlan.ca>, size=259, nrcpt=1 (queue active)
Oct 30 22:22:28 PBX1 postfix/qmgr[14511]: warning: connect to transport private/192.168.2.3: No such file or directory
Oct 30 22:22:28 PBX1 postfix/error[16374]: 560DE2C0ACC: to=<***@azlan.ca>, relay=none, delay=97092, delays=97092/0.01/0/0.05, dsn=4.3.0, status=deferred (mail transport unavailable)
Oct 30 22:28:11 PBX1 postfix/pickup[16380]: 0A4422C0DFB: uid=1000 from=<pbx1>
Oct 30 22:28:11 PBX1 postfix/cleanup[16502]: 0A4422C0DFB: message-id=<***@mail.azlan.ca>
Oct 30 22:28:11 PBX1 postfix/qmgr[14511]: 0A4422C0DFB: from=<***@azlan.ca>, size=280, nrcpt=1 (queue active)
Oct 30 22:28:11 PBX1 postfix/qmgr[14511]: warning: connect to transport private/192.168.2.3: No such file or directory
Oct 30 22:28:11 PBX1 postfix/error[16504]: 0A4422C0DFB: to=<***@azlan.ca>, relay=none, delay=33, delays=33/0/0/0.04, dsn=4.3.0, status=deferred (mail transport unavailable)
Burkhard Ott
2014-11-01 01:06:11 UTC
Permalink
Post by Michael Coulton
Oct 30 22:28:11 PBX1 postfix/qmgr[14511]: warning: connect to transport
private/192.168.2.3: No such file or directory
You still have an issue in main.cf or master (if configured vi master).
Did you setup transport_maps = /etc/postfix/transport ?
What do you have in transport, sould look like "azlan.ca
smtp:192.168.2.3".
Michael Coulton
2014-11-01 02:32:29 UTC
Permalink
Post by Burkhard Ott
Post by Michael Coulton
Oct 30 22:28:11 PBX1 postfix/qmgr[14511]: warning: connect to transport
private/192.168.2.3: No such file or directory
You still have an issue in main.cf or master (if configured vi master).
Did you setup transport_maps = /etc/postfix/transport ?
What do you have in transport, sould look like "azlan.ca
smtp:192.168.2.3".
Hello
Have adjusted the /etc/postfix/transport file to "azlan.ca smtp:192.168.2.3"

Error Log

Oct 31 22:26:18 PBX1 postfix/qmgr[18524]: BFD462C0B67: from=<***@azlan.ca>, size=268, nrcpt=1 (queue active)
Oct 31 22:26:48 PBX1 postfix/smtp[18526]: connect to 192.168.2.3[192.168.2.3]:25: Connection timed out
Oct 31 22:26:48 PBX1 postfix/smtp[18526]: BFD462C0B67: to=<***@azlan.ca>, relay=none, delay=61, delays=31/0/30/0, dsn=4.4.1, status=deferred (connect to 192.168.2.3[192.168.2.3]:25: Connection timed out)


/etc/postfix/master.cf

# Postfix master process configuration file. For details on the format
# of the file, see the master(5) manual page (command: "man 5 master" or
# on-line: http://www.postfix.org/master.5.html).
#
# Do not forget to execute "postfix reload" after editing this file.
#
# ==========================================================================
# service type private unpriv chroot wakeup maxproc command + args
# (yes) (yes) (yes) (never) (100)
# ==========================================================================
smtp inet n - - - - smtpd
#smtp inet n - - - 1 postscreen
#smtpd pass - - - - - smtpd
#dnsblog unix - - - - 0 dnsblog
#tlsproxy unix - - - - 0 tlsproxy
#submission inet n - - - - smtpd
# -o syslog_name=postfix/submission
# -o smtpd_tls_security_level=encrypt
# -o smtpd_sasl_auth_enable=yes
# -o smtpd_reject_unlisted_recipient=no
# -o smtpd_client_restrictions=$mua_client_restrictions
# -o smtpd_helo_restrictions=$mua_helo_restrictions
# -o smtpd_sender_restrictions=$mua_sender_restrictions
# -o smtpd_recipient_restrictions=
# -o smtpd_relay_restrictions=permit_sasl_authenticated,reject
# -o milter_macro_daemon_name=ORIGINATING
#smtps inet n - - - - smtpd
# -o syslog_name=postfix/smtps
# -o smtpd_tls_wrappermode=yes
# -o smtpd_sasl_auth_enable=yes
# -o smtpd_reject_unlisted_recipient=no
# -o smtpd_client_restrictions=$mua_client_restrictions
# -o smtpd_helo_restrictions=$mua_helo_restrictions
# -o smtpd_sender_restrictions=$mua_sender_restrictions
# -o smtpd_recipient_restrictions=
# -o smtpd_relay_restrictions=permit_sasl_authenticated,reject
# -o milter_macro_daemon_name=ORIGINATING
#628 inet n - - - - qmqpd
pickup unix n - - 60 1 pickup
cleanup unix n - - - 0 cleanup
qmgr unix n - n 300 1 qmgr
#qmgr unix n - n 300 1 oqmgr
tlsmgr unix - - - 1000? 1 tlsmgr
rewrite unix - - - - - trivial-rewrite
bounce unix - - - - 0 bounce
defer unix - - - - 0 bounce
trace unix - - - - 0 bounce
verify unix - - - - 1 verify
flush unix n - - 1000? 0 flush
proxymap unix - - n - - proxymap
proxywrite unix - - n - 1 proxymap
smtp unix - - - - - smtp
relay unix - - - - - smtp
# -o smtp_helo_timeout=5 -o smtp_connect_timeout=5
showq unix n - - - - showq
error unix - - - - - error
retry unix - - - - - error
discard unix - - - - - discard
local unix - n n - - local
virtual unix - n n - - virtual
lmtp unix - - - - - lmtp
anvil unix - - - - 1 anvil
scache unix - - - - 1 scache
#
# ====================================================================
# Interfaces to non-Postfix software. Be sure to examine the manual
# pages of the non-Postfix software to find out what options it wants.
#
# Many of the following services use the Postfix pipe(8) delivery
# agent. See the pipe(8) man page for information about ${recipient}
# and other message envelope options.
# ====================================================================
#
# maildrop. See the Postfix MAILDROP_README file for details.
# Also specify in main.cf: maildrop_destination_recipient_limit=1
#
maildrop unix - n n - - pipe
flags=DRhu user=vmail argv=/usr/bin/maildrop -d ${recipient}
#
# ====================================================================
#
# Recent Cyrus versions can use the existing "lmtp" master.cf entry.
#
# Specify in cyrus.conf:
# lmtp cmd="lmtpd -a" listen="localhost:lmtp" proto=tcp4
#
# Specify in main.cf one or more of the following:
# mailbox_transport = lmtp:inet:localhost
# virtual_transport = lmtp:inet:localhost
#
# ====================================================================
#
# Cyrus 2.1.5 (Amos Gouaux)
# Also specify in main.cf: cyrus_destination_recipient_limit=1
#
#cyrus unix - n n - - pipe
# user=cyrus argv=/cyrus/bin/deliver -e -r ${sender} -m ${extension} ${user}
#
# ====================================================================
# Old example of delivery via Cyrus.
#
#old-cyrus unix - n n - - pipe
# flags=R user=cyrus argv=/cyrus/bin/deliver -e -m ${extension} ${user}
#
# ====================================================================
#
# See the Postfix UUCP_README file for configuration details.
#
uucp unix - n n - - pipe
flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient)
#
# Other external delivery methods.
#
ifmail unix - n n - - pipe
flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient)
bsmtp unix - n n - - pipe
flags=Fq. user=bsmtp argv=/usr/lib/bsmtp/bsmtp -t$nexthop -f$sender $recipient
scalemail-backend unix - n n - 2 pipe
flags=R user=scalemail argv=/usr/lib/scalemail/bin/scalemail-store ${nexthop} ${user} ${extension}
mailman unix - n n - - pipe
flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py
${nexthop} ${user}
Burkhard Ott
2014-11-01 02:57:15 UTC
Permalink
Post by Michael Coulton
Oct 31 22:26:48 PBX1 postfix/smtp[18526]: connect to
192.168.2.3[192.168.2.3]:25: Connection timed out
Is an smtp listening on that address and port?
( you can check via telnet 192.168.2.3 25)
Michael Coulton
2014-11-01 14:52:05 UTC
Permalink
Post by Burkhard Ott
Post by Michael Coulton
Oct 31 22:26:48 PBX1 postfix/smtp[18526]: connect to
192.168.2.3[192.168.2.3]:25: Connection timed out
Is an smtp listening on that address and port?
( you can check via telnet 192.168.2.3 25)
Hello
The smtp is listening on port 465 and I want to keep it that way so that I can send out going messages. So I've change my transport file to be:
azlan.ca smtp:[192.168.2.3]:465

Error Log


Nov 1 10:41:22 PBX1 postfix/smtp[20187]: 24F512C0E98: to=<***@azlan.ca>, relay=192.168.2.3[192.168.2.3]:465, delay=24, delays=24/0/0.04/0, dsn=4.3.0, status=deferred (local data error while talking to 192.168.2.3[192.168.2.3])
Nov 1 10:45:49 PBX1 postfix/qmgr[20185]: 8617F2C0CC4: from=<***@azlan.ca>, size=260, nrcpt=1 (queue active)
Nov 1 10:45:49 PBX1 postfix/qmgr[20185]: 929022C0D0F: from=<***@azlan.ca>, size=260, nrcpt=1 (queue active)
Nov 1 10:45:49 PBX1 postfix/qmgr[20185]: 0A4422C0DFB: from=<***@azlan.ca>, size=280, nrcpt=1 (queue active)
Nov 1 10:45:49 PBX1 postfix/smtp[20197]: error: open database /etc/postfix/sasl_passwd.db: No such file or directory
Nov 1 10:45:49 PBX1 postfix/smtp[20197]: CLIENT wrappermode (port smtps/465) is unimplemented
Nov 1 10:45:49 PBX1 postfix/smtp[20197]: instead, send to (port submission/587) with STARTTLS
Nov 1 10:45:49 PBX1 postfix/smtp[20198]: error: open database /etc/postfix/sasl_passwd.db: No such file or directory
Nov 1 10:45:49 PBX1 postfix/smtp[20198]: CLIENT wrappermode (port smtps/465) is unimplemented
Nov 1 10:45:49 PBX1 postfix/smtp[20198]: instead, send to (port submission/587) with STARTTLS
Nov 1 10:45:49 PBX1 postfix/smtp[20199]: error: open database /etc/postfix/sasl_passwd.db: No such file or directory
Nov 1 10:45:49 PBX1 postfix/smtp[20199]: CLIENT wrappermode (port smtps/465) is unimplemented
Nov 1 10:45:49 PBX1 postfix/smtp[20199]: instead, send to (port submission/587) with STARTTLS
Nov 1 10:45:49 PBX1 postfix/smtp[20197]: warning: hash:/etc/postfix/sasl_passwd is unavailable. open database /etc/postfix/sasl_passwd.db: No such file or directory
Nov 1 10:45:49 PBX1 postfix/smtp[20197]: warning: hash:/etc/postfix/sasl_passwd lookup error for "192.168.2.3"
Nov 1 10:45:49 PBX1 postfix/smtp[20197]: warning: 8617F2C0CC4: smtp_sasl_passwd lookup error
Nov 1 10:45:49 PBX1 postfix/smtp[20198]: warning: hash:/etc/postfix/sasl_passwd is unavailable. open database /etc/postfix/sasl_passwd.db: No such file or directory
Nov 1 10:45:49 PBX1 postfix/smtp[20198]: warning: hash:/etc/postfix/sasl_passwd lookup error for "192.168.2.3"
Nov 1 10:45:49 PBX1 postfix/smtp[20198]: warning: 929022C0D0F: smtp_sasl_passwd lookup error
Nov 1 10:45:49 PBX1 postfix/smtp[20199]: warning: hash:/etc/postfix/sasl_passwd is unavailable. open database /etc/postfix/sasl_passwd.db: No such file or directory
Nov 1 10:45:49 PBX1 postfix/smtp[20199]: warning: hash:/etc/postfix/sasl_passwd lookup error for "192.168.2.3"
Nov 1 10:45:49 PBX1 postfix/smtp[20199]: warning: 0A4422C0DFB: smtp_sasl_passwd lookup error
Nov 1 10:45:49 PBX1 postfix/smtp[20197]: 8617F2C0CC4: to=<***@azlan.ca>, relay=192.168.2.3[192.168.2.3]:465, delay=325276, delays=325276/0.04/0.06/0, dsn=4.3.0, status=deferred (local data error while talking to 192.168.2.3[192.168.2.3])
Nov 1 10:45:49 PBX1 postfix/smtp[20199]: 0A4422C0DFB: to=<***@azlan.ca>, relay=192.168.2.3[192.168.2.3]:465, delay=130691, delays=130691/0.08/0.05/0, dsn=4.3.0, status=deferred (local data error while talking to 192.168.2.3[192.168.2.3])
Nov 1 10:45:49 PBX1 postfix/smtp[20198]: 929022C0D0F: to=<***@azlan.ca>, relay=192.168.2.3[192.168.2.3]:465, delay=323669, delays=323669/0.06/0.04/0, dsn=4.3.0, status=deferred (local data error while talking to 192.168.2.3[192.168.2.3])
Nov 1 10:49:27 PBX1 postfix/pickup[20184]: 471722C0EE7: uid=1000 from=<pbx1>
Nov 1 10:49:27 PBX1 postfix/cleanup[20206]: 471722C0EE7: message-id=<***@mail.azlan.ca>
Nov 1 10:49:27 PBX1 postfix/qmgr[20185]: 471722C0EE7: from=<***@azlan.ca>, size=259, nrcpt=1 (queue active)
Nov 1 10:49:27 PBX1 postfix/error[20208]: 471722C0EE7: to=<***@azlan.ca>, relay=none, delay=21, delays=21/0/0/0.04, dsn=4.3.0, status=deferred (delivery temporarily suspended: local data error while talking to 192.168.2.3[192.168.2.3])
Burkhard Ott
2014-11-01 16:03:07 UTC
Permalink
Hello The smtp is listening on port 465 and I want to keep it that way
so that I can send out going messages. So I've change my transport file
azlan.ca smtp:[192.168.2.3]:465
Sure, then setup ssl on both sides.

ov 1 10:45:49 PBX1 postfix/smtp[20197]: CLIENT wrappermode (port
smtps/465) is unimplemented
Nov 1 10:45:49 PBX1 postfix/smtp[20197]: instead, send to (port
submission/587) with STARTTLS


You configured authentication, which is fine, however you need to setup
your authentication as well if you'd like to use it. Just defining a file
which doesn't exist won't help you.

Nov 1 10:45:49 PBX1 postfix/smtp[20197]: error: open database /etc/
postfix/sasl_passwd.db: No such file or directory

You didn't respond to my email I wrote you yesterday, let's try a
different way. Tell me what connection and what protocol(s) you'd like to
speak, I'll make you a config file you can use or not, up 2 you.

Don't want to offend you, but you really have to understand the basics if
you'd like to run a reliable service realitvly secure.

Sounds like a plan?

cheers
Michael Coulton
2014-11-01 20:00:58 UTC
Permalink
Post by Burkhard Ott
Hello The smtp is listening on port 465 and I want to keep it that way
so that I can send out going messages. So I've change my transport file
azlan.ca smtp:[192.168.2.3]:465
Sure, then setup ssl on both sides.
ov 1 10:45:49 PBX1 postfix/smtp[20197]: CLIENT wrappermode (port
smtps/465) is unimplemented
Nov 1 10:45:49 PBX1 postfix/smtp[20197]: instead, send to (port
submission/587) with STARTTLS
You configured authentication, which is fine, however you need to setup
your authentication as well if you'd like to use it. Just defining a file
which doesn't exist won't help you.
Nov 1 10:45:49 PBX1 postfix/smtp[20197]: error: open database /etc/
postfix/sasl_passwd.db: No such file or directory
You didn't respond to my email I wrote you yesterday, let's try a
different way. Tell me what connection and what protocol(s) you'd like to
speak, I'll make you a config file you can use or not, up 2 you.
Don't want to offend you, but you really have to understand the basics if
you'd like to run a reliable service realitvly secure.
Sounds like a plan?
cheers
Hello
Hopefully I can answer your questions.
***@PBX1:~$ telnet 192.168.2.3 465
Trying 192.168.2.3...
Connected to 192.168.2.3.
Escape character is '^]'.
220 mail.azlan.ca FirstClass ESMTP Mail Server v11.0 ready

FirstClass is the email server (a product by OpenText).


"Tell me what connection and what protocol(s)"
Don't understand the question. TCP, UDP, SMTP, ESMTP
POP3 = port 995
SMTP = port 465



If you could make me a config file that would be terrific. Thanks for the help.
Burkhard Ott
2014-11-01 20:15:49 UTC
Permalink
Post by Burkhard Ott
Hello The smtp is listening on port 465 and I want to keep it that
way so that I can send out going messages. So I've change my
azlan.ca smtp:[192.168.2.3]:465
Sure, then setup ssl on both sides.
ov 1 10:45:49 PBX1 postfix/smtp[20197]: CLIENT wrappermode (port
instead, send to (port submission/587) with STARTTLS
You configured authentication, which is fine, however you need to setup
your authentication as well if you'd like to use it. Just defining a
file which doesn't exist won't help you.
Nov 1 10:45:49 PBX1 postfix/smtp[20197]: error: open database /etc/
postfix/sasl_passwd.db: No such file or directory
You didn't respond to my email I wrote you yesterday, let's try a
different way. Tell me what connection and what protocol(s) you'd like
to speak, I'll make you a config file you can use or not, up 2 you.
Don't want to offend you, but you really have to understand the basics
if you'd like to run a reliable service realitvly secure.
Sounds like a plan?
cheers
Hello Hopefully I can answer your questions.
Connected to 192.168.2.3.
Escape character is '^]'.
220 mail.azlan.ca FirstClass ESMTP Mail Server v11.0 ready
FirstClass is the email server (a product by OpenText).
"Tell me what connection and what protocol(s)"
Don't understand the question. TCP, UDP, SMTP, ESMTP POP3 = port 995
SMTP = port 465
If you could make me a config file that would be terrific. Thanks for the help.
To be honest, throw away firstclass, install a linux (whatever flavor you
like), install an MTA, then I can help you.
if you'd like to stay with firstclass, they support their product so
please contat them (http://www.firstclass.com/Services/Support)

cheers
Michael Coulton
2014-11-01 21:08:57 UTC
Permalink
Post by Burkhard Ott
Post by Burkhard Ott
Hello The smtp is listening on port 465 and I want to keep it that
way so that I can send out going messages. So I've change my
azlan.ca smtp:[192.168.2.3]:465
Sure, then setup ssl on both sides.
ov 1 10:45:49 PBX1 postfix/smtp[20197]: CLIENT wrappermode (port
instead, send to (port submission/587) with STARTTLS
You configured authentication, which is fine, however you need to setup
your authentication as well if you'd like to use it. Just defining a
file which doesn't exist won't help you.
Nov 1 10:45:49 PBX1 postfix/smtp[20197]: error: open database /etc/
postfix/sasl_passwd.db: No such file or directory
You didn't respond to my email I wrote you yesterday, let's try a
different way. Tell me what connection and what protocol(s) you'd like
to speak, I'll make you a config file you can use or not, up 2 you.
Don't want to offend you, but you really have to understand the basics
if you'd like to run a reliable service realitvly secure.
Sounds like a plan?
cheers
Hello Hopefully I can answer your questions.
Connected to 192.168.2.3.
Escape character is '^]'.
220 mail.azlan.ca FirstClass ESMTP Mail Server v11.0 ready
FirstClass is the email server (a product by OpenText).
"Tell me what connection and what protocol(s)"
Don't understand the question. TCP, UDP, SMTP, ESMTP POP3 = port 995
SMTP = port 465
If you could make me a config file that would be terrific. Thanks for the help.
To be honest, throw away firstclass, install a linux (whatever flavor you
like), install an MTA, then I can help you.
if you'd like to stay with firstclass, they support their product so
please contat them (http://www.firstclass.com/Services/Support)
cheers
Hello
FirstClass does offer support to trial license versions. I know because I use to work there on the Voice Services side; not the messaging or collabrative side. Their product conforms to all open standards and I'm using it as a hobbist to send and receive mail through my ISP; the problamatic rogers.com.

I shouldn't be having issue's sending an email from the postfix MTA at 192.168.2.2 to my FirstClass server at 192.168.2.3. My understanding is that this should be a simple process, however I keep running into road blocks.
I've successfully send and received mail using FirstClass in the past through the rogers SMTP server. I'd like to stay with postfix as I've spent so much time working with it. A friend of mine uses "sendmail" through rogers.com and doesn't seem to have an issue. I'd like to stay loyal to "postfix" if I could. All I simply want to do is send email notification from 192.168.2.2 to ***@azlan.ca using "postfix". I don't care if the email stay's internal on my network or goes externally via rogers.com or google.com. All I know is that in 5 weeks none of these options has worked. All the reading I've done; all the help you've kindly provided; none it has managed to get one single piece of email from point A (192.168.2.2) to point B (192.168.2.3)!

So..... what settings do I need in my main.cf and master.cf in order for this to work?
Should I remove postfix and re-install it so that I can start from scratch?
You kindly offered to create a config file for me. What information do you need?
If my FC Server is using port 465, then I guess I need to create a sasl_passwrd and sasl_passwrd.db file?

If you don't wish to support this issue any more, then I can understand that. As always I really appreciate your very kind efforts.
Michael
Burkhard Ott
2014-11-01 21:37:57 UTC
Permalink
Hello FirstClass does offer support to trial license versions. I know
because I use to work there on the Voice Services side; not the
messaging or collabrative side. Their product conforms to all open
standards and I'm using it as a hobbist to send and receive mail through
my ISP; the problamatic rogers.com.
I shouldn't be having issue's sending an email from the postfix MTA at
192.168.2.2 to my FirstClass server at 192.168.2.3. My understanding is
that this should be a simple process, however I keep running into road
blocks.
I've successfully send and received mail using FirstClass in the past
through the rogers SMTP server. I'd like to stay with postfix as I've
spent so much time working with it. A friend of mine uses "sendmail"
through rogers.com and doesn't seem to have an issue. I'd like to stay
loyal to "postfix" if I could. All I simply want to do is send email
don't care if the email stay's internal on my network or goes externally
via rogers.com or google.com. All I know is that in 5 weeks none of
these options has worked. All the reading I've done; all the help you've
kindly provided; none it has managed to get one single piece of email
from point A (192.168.2.2) to point B (192.168.2.3)!
So..... what settings do I need in my main.cf and master.cf in order for this to work?
Should I remove postfix and re-install it so that I can start from scratch?
You kindly offered to create a config file for me. What information do you need?
If my FC Server is using port 465, then I guess I need to create a
sasl_passwrd and sasl_passwrd.db file?
If you don't wish to support this issue any more, then I can understand
that. As always I really appreciate your very kind efforts.
Michael
No problem, then you should license the product, or use entirely open
source. I support open source on my spare time, which is quite limited. I
do not support any commercial software. Who knows if they setup iptable
rules and block the traffic, route it elsewehere.
Sorry, I can't help in that case.

Continue reading on narkive:
Loading...