http://www.nnseek.com/e/mailing.postfix.users/ Posts for mailing.postfix.users Thu, 21 Aug 2008 10:24:43 PDT http://www.nnseek.com/ http://www.nnseek.com/img/64.png 64 64 NNSeek http://www.nnseek.com/e/mailing.postfix.users/postfix_not_sending_using_tls_161833903t.html http://www.nnseek.com/e/mailing.postfix.users/postfix_not_sending_using_tls_161833903t.html
I am running Postfix 2.5.1 with OpenSSL on an email gateway and I
configured the mailer to use STARTTLS whenever it is possible.
My config works fine *receiving* emails. I am using self-signed
certificate etc.

However, it doesn't work when sending email out. ie. when I send to a
mailer that I know accepts TLS encrypted e-mail, my mailer just sends
it out normally. Not even a mention of a failed handshake or whatever
on the maillog file. Just sends out like normal ESMTP.

Here's my TLS-specific config on main.cf:

smtpd_use_tls = yes
smtpd_tls_security_level = may
smtpd_tls_auth_only = no
smtpd_tls_CAfile = /etc/postfix/certs/cacert.pem
smtpd_tls_key_file = /etc/postfix/certs/foo-key.pem
smtpd_tls_cert_file = /etc/postfix/certs/foo-cert.pem
smtpd_tls_loglevel = 2
smtpd_tls_received_header = yes
smtpd_tls_session_cache_timeout = 3600s
smtpd_enforce_tls = no
smtpd_tls_ask_ccert = yes
smtpd_tls_req_ccert = no
tls_random_source = dev:/dev/urandom
smtp_use_tls = yes
smtp_tls_note_starttls_offer = yes
smtp_tls_CAfile = /etc/postfix/certs/cacert.pem
smtp_tls_key_file = /etc/postfix/certs/foo-key.pem
smtp_tls_cert_file = /etc/postfix/certs/foo-cert.pem
tls_random_exchange_name = /var/db/postfix/prng_exch


/etc/postfix/certs/cacert.pem is self-signed CA
/etc/postfix/certs/foo-key.pem is self-generated RSA private key
/etc/postfix/certs/foo-cert.pem is self-generated Cert

What am I doing wrong? There's obviously something that's sticking
somewhere and I've spent 2 weeks on-off on this, with no success.
Thanks for all help!

Kind regards,

--
Olivier MJ Crepin-Leblond
http://www.gih.com/ocl.html / ocl@gih.com

Posted In: mailing.postfix.users

no comments

Reply

]]> Thu, 21 Aug 2008 10:24:43 PDT http://www.nnseek.com/e/mailing.postfix.users/postfix_and_email_addresses_159903151t.html http://www.nnseek.com/e/mailing.postfix.users/postfix_and_email_addresses_159903151t.html squirrelmail with any email address I add to the database. and
example of this is:
root@localhost root 5000 5000 /var/spool/mail/virtual root/
1 1 Password1
(copied from phpmyadmin, from the mail database)

I try to log in as root@localhost with the password of Password1 and
it gives me an error about an incorrect email address and password
combination.

Why is this?

Posted In: mailing.postfix.users

no comments

Reply

]]> Mon, 11 Aug 2008 12:02:18 PDT http://www.nnseek.com/e/mailing.postfix.users/we_ll_advertise_your_business_78401_159748783t.html http://www.nnseek.com/e/mailing.postfix.users/we_ll_advertise_your_business_78401_159748783t.html HUGE Exposure. Let Us Handle
All The Work - VISITORS GUARANTEED
OR YOUR MONEY BACK!!!

http://submitmywebpage.com/offers/






cAn]T.P$6<=bejNZaxUnjVg<

Posted In: mailing.postfix.users

no comments

Reply

]]> Sun, 10 Aug 2008 13:14:29 PDT http://www.nnseek.com/e/mailing.postfix.users/trouble_with_squirrelmail_158976687t.html http://www.nnseek.com/e/mailing.postfix.users/trouble_with_squirrelmail_158976687t.html try to log in with valid information it denies me access. I used the
phpmyadmin site to create new users, all of which have a name,
address, and password.

I even tried copying and pasting the "clear text" password that
phpadmin grabs from the database... and no dice.


/var/log/mail.info:


root@elan-www:/usr/share/squirrelmail/functions# tail /var/log/
mail.info
Aug 7 16:01:05 elan-www postfix/virtual[6097]: warning: recipient
steve@elandata.com: not found in virtual_uid_maps
Aug 7 16:01:05 elan-www postfix/virtual[6097]: 97F5E66442:
to=elandata.com>, relay=virtual, delay=4803,
delays=4802/0.02/0/0.04, dsn=4.3.5, status=deferred (mail system
configuration error)
Aug 7 16:23:22 elan-www imapd-ssl: LOGIN FAILED,
user=steve@elandata.com, ip=[::ffff:127.0.0.1]
Aug 7 16:23:27 elan-www imapd-ssl: LOGOUT, ip=[::ffff:127.0.0.1],
rcvd=62, sent=334
Aug 7 16:23:50 elan-www imapd-ssl: LOGIN FAILED, user=root,
ip=[::ffff:127.0.0.1]
Aug 7 16:23:55 elan-www imapd-ssl: LOGOUT, ip=[::ffff:127.0.0.1],
rcvd=43, sent=334
Aug 7 16:24:57 elan-www imapd-ssl: LOGIN FAILED,
user=steve@elandata.com, ip=[::ffff:127.0.0.1]
Aug 7 16:25:02 elan-www imapd-ssl: LOGOUT, ip=[::ffff:127.0.0.1],
rcvd=56, sent=334
Aug 7 16:25:45 elan-www imapd-ssl: LOGIN FAILED,
user=steve@elandata.com, ip=[::ffff:127.0.0.1]
Aug 7 16:25:50 elan-www imapd-ssl: LOGOUT, ip=[::ffff:127.0.0.1],
rcvd=56, sent=334
root@elan-www:/usr/share/squirrelmail/functions#




/var/log/mail.err:


root@elan-www:/usr/share/squirrelmail/functions# tail /var/log/
mail.info
Aug 7 16:01:05 elan-www postfix/virtual[6097]: warning: recipient
steve@elandata.com: not found in virtual_uid_maps
Aug 7 16:01:05 elan-www postfix/virtual[6097]: 97F5E66442:
to=elandata.com>, relay=virtual, delay=4803,
delays=4802/0.02/0/0.04, dsn=4.3.5, status=deferred (mail system
configuration error)
Aug 7 16:23:22 elan-www imapd-ssl: LOGIN FAILED,
user=steve@elandata.com, ip=[::ffff:127.0.0.1]
Aug 7 16:23:27 elan-www imapd-ssl: LOGOUT, ip=[::ffff:127.0.0.1],
rcvd=62, sent=334
Aug 7 16:23:50 elan-www imapd-ssl: LOGIN FAILED, user=root,
ip=[::ffff:127.0.0.1]
Aug 7 16:23:55 elan-www imapd-ssl: LOGOUT, ip=[::ffff:127.0.0.1],
rcvd=43, sent=334
Aug 7 16:24:57 elan-www imapd-ssl: LOGIN FAILED,
user=steve@elandata.com, ip=[::ffff:127.0.0.1]
Aug 7 16:25:02 elan-www imapd-ssl: LOGOUT, ip=[::ffff:127.0.0.1],
rcvd=56, sent=334
Aug 7 16:25:45 elan-www imapd-ssl: LOGIN FAILED,
user=steve@elandata.com, ip=[::ffff:127.0.0.1]
Aug 7 16:25:50 elan-www imapd-ssl: LOGOUT, ip=[::ffff:127.0.0.1],
rcvd=56, sent=334
root@elan-www:/usr/share/squirrelmail/functions# tail /var/log/
mail.err
Aug 7 14:41:45 elan-www authdaemond: authmysql: MYSQL_CRYPT_PWFIELD
and MYSQL_CLEAR_PWFIELD not set in /etc/courier/authmysqlrc.
Aug 7 14:41:45 elan-www imapd-ssl: authentication error: Input/output
error
Aug 7 14:42:55 elan-www authdaemond: authmysql: MYSQL_CRYPT_PWFIELD
and MYSQL_CLEAR_PWFIELD not set in /etc/courier/authmysqlrc.
Aug 7 14:42:55 elan-www imapd: authentication error: Input/output
error
Aug 7 14:46:00 elan-www authdaemond: authmysql: MYSQL_CRYPT_PWFIELD
and MYSQL_CLEAR_PWFIELD not set in /etc/courier/authmysqlrc.
Aug 7 14:46:00 elan-www imapd-ssl: authentication error: Input/output
error
Aug 7 14:49:09 elan-www authdaemond: authmysql: MYSQL_CRYPT_PWFIELD
and MYSQL_CLEAR_PWFIELD not set in /etc/courier/authmysqlrc.
Aug 7 14:49:09 elan-www imapd-ssl: authentication error: Input/output
error
Aug 7 14:51:14 elan-www authdaemond: authmysql: MYSQL_CRYPT_PWFIELD
and MYSQL_CLEAR_PWFIELD not set in /etc/courier/authmysqlrc.
Aug 7 14:51:14 elan-www imapd-ssl: authentication error: Input/output
error
root@elan-www:/usr/share/squirrelmail/functions# tail /var/log/
mail.err
Aug 7 14:41:45 elan-www authdaemond: authmysql: MYSQL_CRYPT_PWFIELD
and MYSQL_CLEAR_PWFIELD not set in /etc/courier/authmysqlrc.
Aug 7 14:41:45 elan-www imapd-ssl: authentication error: Input/output
error
Aug 7 14:42:55 elan-www authdaemond: authmysql: MYSQL_CRYPT_PWFIELD
and MYSQL_CLEAR_PWFIELD not set in /etc/courier/authmysqlrc.
Aug 7 14:42:55 elan-www imapd: authentication error: Input/output
error
Aug 7 14:46:00 elan-www authdaemond: authmysql: MYSQL_CRYPT_PWFIELD
and MYSQL_CLEAR_PWFIELD not set in /etc/courier/authmysqlrc.
Aug 7 14:46:00 elan-www imapd-ssl: authentication error: Input/output
error
Aug 7 14:49:09 elan-www authdaemond: authmysql: MYSQL_CRYPT_PWFIELD
and MYSQL_CLEAR_PWFIELD not set in /etc/courier/authmysqlrc.
Aug 7 14:49:09 elan-www imapd-ssl: authentication error: Input/output
error
Aug 7 14:51:14 elan-www authdaemond: authmysql: MYSQL_CRYPT_PWFIELD
and MYSQL_CLEAR_PWFIELD not set in /etc/courier/authmysqlrc.
Aug 7 14:51:14 elan-www imapd-ssl: authentication error: Input/output
error
root@elan-www:/usr/share/squirrelmail/functions#



It likes to complain about those 2 password directives in /etc/courier/
authmysqlrc... but..:

# Either MYSQL_CRYPT_PWFIELD or MYSQL_CLEAR_PWFIELD must be defined.
Both
# are OK too. crypted passwords go into MYSQL_CRYPT_PWFIELD, cleartext
# passwords go into MYSQL_CLEAR_PWFIELD. Cleartext passwords allow
# CRAM-MD5 authentication to be implemented.

MYSQL_CRYPT_PWFIELD crypt

##NAME: MYSQL_CLEAR_PWFIELD:0
#
#
#MYSQL_CLEAR_PWFIELD clear

It's clearly set! Uncommenting both doesn't work either.

Ideas, anyone?

Posted In: mailing.postfix.users

no comments

Reply

]]> Thu, 07 Aug 2008 16:29:57 PDT http://www.nnseek.com/e/mailing.postfix.users/fuel_solution_earn_money_51636_158325423t.html http://www.nnseek.com/e/mailing.postfix.users/fuel_solution_earn_money_51636_158325423t.html Why PAY TOO MUCH for FUEL
Learn how to protect our
Environment and Reduce unnecessary
spending
=======================================

http://www.fuellegacy.com/dkokeefe

=======================================




@ldui

Posted In: mailing.postfix.users

no comments

Reply

]]> Mon, 04 Aug 2008 09:12:18 PDT http://www.nnseek.com/e/mailing.postfix.users/how_to_add_a_header_indicating_recipient_domain_155217327t.html http://www.nnseek.com/e/mailing.postfix.users/how_to_add_a_header_indicating_recipient_domain_155217327t.html spamassassin/mailscanner. It stands in front of a single MS Exchange
2003 R2 server serving four mail domains. Mail to username@whichever-
domain.com is delivered to the Exchange inbox for username, which is
what we want. However, we need to flag mail addressed to one domain in
particular for special handling (say special.com).

Surprisingly, neither Exchange nor Outlook can reliably identify the
recipient domain as a rule condition. (They can check for text in
headers, though.) Exchange does have the hooks for coding this, but
writing, testing and maintaining an SMTP sink would be a major
undertaking for such a seemingly minor result.

I feel sure that postfix or mailscanner could handle this easily,
i.e. if the recipient domain is special.com, add a header "X-
Special:true". Am I right, and if so, can anyone point me to the right
place to configure it?


TIA

Posted In: mailing.postfix.users

no comments

Reply

]]> Wed, 23 Jul 2008 12:55:37 PDT http://www.nnseek.com/e/mailing.postfix.users/anyone_using_else_using_an_rbl_server_or_proxy_with_154978991t.html http://www.nnseek.com/e/mailing.postfix.users/anyone_using_else_using_an_rbl_server_or_proxy_with_154978991t.html results from both programs using dig but i am unable to get the
correct reply using rblcheck. I started the server using

RBLDNSD="dsbl -r/var/lib/rbldns -b myiphere/53 \
myservername.mydomain.org:ip4set:clients"

and I can retrieve results using sothing like

dig 223.61.83.162.myservename.myserverdomain.org -t txt @myserverip

where 223.61.83.162 is the ip of the host being blocked but reversed
found in the file clients


The problem i am having is that if i use any rbl client like rblcheck
i dont get any results

if i do

rblcheck -s myservername.myserverip.org 162.83.61.223

the rblcheck program can find the ip 162.83.61.223


does anyone know if rblcheck queries upd port 53 in the same way that
dig does? any suggestions?

thanks.

Posted In: mailing.postfix.users

1 Comment

Reply

]]> Tue, 22 Jul 2008 13:31:24 PDT http://www.nnseek.com/e/mailing.postfix.users/order_of_restrictions_154604463t.html http://www.nnseek.com/e/mailing.postfix.users/order_of_restrictions_154604463t.html want to use greylisting and DNSBL. This ar my restrictions:

smtpd_data_restrictions =
reject_multi_bounce

smtpd_sender_restrictions =
reject_non_fqdn_sender
reject_unknown_sender_domain

smtpd_recipient_restrictions =
reject_non_fqdn_recipient
reject_unknown_recipient_domain
permit_mynetworks
permit_sasl_authenticated
check_recipient_access hash:/etc/postfix/swag-recipients
reject_unauth_destination
check_recipient_access hash:/etc/postfix/roleaccount_exceptions
reject_unlisted_recipient
check_helo_access pcre:/etc/postfix/helo_checks
reject_non_fqdn_hostname
reject_invalid_hostname
check_sender_mx_access cidr:/etc/postfix/bogus_mx
check_sender_access hash:/etc/postfix/senders
reject_unlisted_sender
check_policy_service inet:127.0.0.1:60001
check_policy_service inet:127.0.0.1:60000
reject_unverified_recipient
reject_unverified_sender
reject_unauth_pipelining
permit

swag-recipients consists of "user@domain.tld OK" pairs, and the
position in restrictions is my problem. For these ms exchange
recipients greylisting (localhost:60000) does not work, but changing
the position of check_recipient_access after postgrey conflicts with
reject_unlisted_recipient - I think. How to sort these policies the
cheapest way? What to use ms exchange domain.tld in relay_domains -
but how chekcing for valid recipients afterwards?

regards

Ronny Seffner

Posted In: mailing.postfix.users

no comments

Reply

]]> Mon, 21 Jul 2008 01:25:39 PDT http://www.nnseek.com/e/mailing.postfix.users/special_queue_lifetime_for_only_one_address_in_tra_154596271t.html http://www.nnseek.com/e/mailing.postfix.users/special_queue_lifetime_for_only_one_address_in_tra_154596271t.html postfix has got an transport "domain.tld smtp:[ip_of_msex]. Now I got
the request dor transport one special address to another host
"user@domain.tld smtp:[ip_of_special_host] - thats not the problem I
think. But: this special host is seldom online so I have to to
increase the queuel lifetime (or whatever - I dont know the right word
for) to one e.g. month. How to do that, please help.

regards

Ronny Seffner

Posted In: mailing.postfix.users

no comments

Reply

]]> Mon, 21 Jul 2008 00:28:19 PDT http://www.nnseek.com/e/mailing.postfix.users/postix_w_spamassassin_on_godaddy_vds_how_to_delete_153632943t.html http://www.nnseek.com/e/mailing.postfix.users/postix_w_spamassassin_on_godaddy_vds_how_to_delete_153632943t.html spamassassin. It marks the spam with [SPAM] in the subject line but I would
rather it deleted it before going to client.

Anyone know of a way? (I am a software developer and not a server guru but
can find my way around a little bit)

Many thanks.

Posted In: mailing.postfix.users

no comments

Reply

]]> Wed, 16 Jul 2008 11:57:25 PDT