in reply to Re^2: SMTP Server - which module
in thread SMTP Server - which module

If it is only a small volume, I would especially stay with a proven and implemented solution for the MTA instead of rolling my own in a week or two. If your clients are well-behaved, they might queue the status mails themselves and retry after some time so you get a chance to fix your code.

Consider that you can set up the MTA to forward all mail to a Perl script anyway through a .forward file. I would avoid the risk of introducing an unproven component. The mailserver handles queueing and the complete protocol for you - why put that hassle on yourself if the usage is only 300 mails per day?

Replies are listed 'Best First'.
Re^4: SMTP Server - which module
by cavac (Prior) on Dec 29, 2011 at 22:39 UTC

    Your argumentation was flawless.

    But i have to bow my head in shame because i have a confession to make: After all this good advice about using a proven product, ... i uh still went ahead and wrote my own MTA. (Ok, what do you expect of some guy who wrote his own webserver just because he didn't like to configure Apache?)

    So far, i works quite nicely and it turns out we have more like 3000-5000 Mails per Day, except that the old mailserver i replaced just "lost" most of them.

    While i'm rather pleased with the result (so far, anyway), i still feel a little guilty about asking the question and then ignore all the advice i got.

    I'd like to hereby thank you for the advice, because i did take a look at various MTA's and saw what features i liked or didn't like. You could say i was inspired by the effort.

    BREW /very/strong/coffee HTTP/1.1
    Host: goodmorning.example.com
    
    418 I'm a teapot