Multiple smtphost addresses using log4net

Question

5.00/5 (1 vote)

See more:

I want to be able to specify multiple smtp server host addresses and implement a logic whereby if email using one smtp server fails, it tries to send using the next smtp server address. Is it possible using log4net. Can we override some functions of log4net and implement our own logic in it to send emails?

XML

<appender name="SmtpAppender" type="log4net.Appender.SmtpAppender">
      <to value="group@ivp.in" />
      <from value="uname@ivp.in" />
      <subject>Error Notification</subject>
      <smtpHost value="smtp.gmail.com" />
      <authentication value="Basic" />
      <port value="587" />
      <username value="uname@company.com" />
      <password value="" />
      <bufferSize value="1" />
      <EnableSsl value="true"/>
      <lossy value="true" />
      <evaluator type="log4net.Core.LevelEvaluator">
        <threshold value="ERROR"/>
      </evaluator>
      <layout type="log4net.Layout.PatternLayout">
        <conversionPattern value="%newline%date [%thread] %level %logger - %message%newline%newline%exception" />
      </layout>
    </appender>

Thanks,
Pankaj

Posted 6-Jun-12 6:26am

Pankaj Chamria

Updated 6-Jun-12 21:18pm

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

SASS_Shooter · Answer 1 · 2012-06-06T09:24:00

One approach you can take -- though there are many solutions -- is to implement Common.Logging 2.0. This will give you pretty much the basic logging interface without any logging implementation. Then through Common.Logging configuration you can tell it what to use.

Via this mechanism you can
a) get all calls for logging written before addressing logging specifics
b) if you find you need to do custom logging, your code gets configured to be
called by Common.Logging and if you can use Log4Net for 90% of your tasks
then just pass through the calls to Log4Net.

In this fashion you can write you own code to do any custom logging you need to do. I did this with our environment because we were creating a unique log entry in the database providing a ton more info than what log4net was providing. Common.Logging provides you with either stubs into various popular logging tools, or the interfaces to do your own. It took about 1 hour of coding to have my logging facility called by everyone ... including NCommon's baked in log calls.