TLS/SASL authentication

[BlueNoteWeb]

I just finished setting up jlasman's spamblocker exim.conf and it's working great, but it's now blocking mail from my backup/testing server in the closet. That server runs several cron scripts each day and sends the results to me via email which is now blocked since I'm on a DSL connection with a dynamic IP.

I found this information on the internet about how to set up PostFix to use authorization on outgoing mail:
http://postfix.state-of-mind.de/patrick.koetter/smtpauth/smtp_auth_mailservers.html
I have followed the directions in there explicitly.
When I try to send mail from my backup server, the entry in /var/log/exim/mainlog looks something like this:

2005-12-12 23:50:24 plain authenticator failed for pool-71-96-208-64.dfw.dsl-w.verizon.net (localhost.localdomain) [71.96.208.64]: 535 Incorrect authentication data ([email protected])

I know that I'm using the right password, I checked it by logging in via webmail to make sure it's not just the saved password in my mail client. Am I setting up my password file wrong? The file /etc/postfix/sasl_passwd looks like this:

mail.bluenoteweb.com       [email][email protected][/email]:mymailpassword

What should I be looking at next?

 

[nobaloney]

Is that server in your closet using postfix?

If so, then you can use the authenticated sender port along with Version 2 of SpamBlocker.

And of course then this post might belong in the Off-Topic forum .

But wait ...

Can you use a dynamic DNS service to set a hostname for that server in the closet? If so you can whitelist it's hostname in SpamBlocker (also using Version 2, as whitelisting doesn't work properly in earlier versions).

Jeff

 

[BlueNoteWeb]

I do have a dynamic DNS service for my IP. The information in the logs is still showing up with Verizon's name on it. Any way to stop that?

 

[nobaloney]

Thinking about it, you'll probably need to go ahead and figure out how to do authentication.

Jeff

 

[BlueNoteWeb]

Eventually I realized that I had never enabled SASL authentication on the server. I'm sure that earns me some sort of stupid-trophy.

Anywho, I just added the "from" address to the whitelist_senders and that's working fine.