Issue #43 resolved
Oleg Franchuk created an issue

I have set email settings in my ini config, but when i do send test email i have "Send email task created " and in email account don't have out email, dir is full. I watching by tcpdump on my server on my mail port 465 and it's full, in log file is all fine, no errors or warnings from email sending.

from production.ini smtp settings:

smtp_server =
smtp_username =
smtp_password = password
smtp_port = 465
smtp_use_tls = true
smtp_use_ssl = true
## Specify available auth parameters here (e.g. LOGIN PLAIN CRAM-MD5, etc.)
smtp_auth = PLAIN

Comments (8)

  1. Mads Kiilerich

    I don't know. I use a local old fashioned port 25 smtp server and it works fine.

    I don't understand what you mean with "full".

    Also, we use this issue tracker a bug tracker, not a discussion forum or support system. This kind of "requests" do not really fit in. I would suggest asking on the mailing list instead.

  2. Oleg Franchuk reporter

    full - i mean that in log file is nothing with errors or warnings for mail sending, but mail don't send

  3. Thomas De Schampheleire

    @franchukoleg82 is this still a problem? I have successfully used ssl and tls now.

    Initially, I also did not get e-mails, but got error messages on the terminal where I had started Kallithea. These messages were caused by not having configured a proper app_email_from value. The default value 'Kallithea' is not a valid e-mail address and was not accepted by my SMTP server. Setting 'app_email_from' to a valid e-mail address fixed the issue for me.

  4. Mads Kiilerich

    Minor clarifcation: It must be a configured policy on your SMTP server that declared 'Kallithea' an invalid sender address. It could also have rewritten it to something else.

    I think it could make sense if app_email_from had a default value of "Kallithea kallithea@%s"%socket.getfqdn() ... or perhaps also using the configured "site branding".

    (We have the opposite in kallithea/lib/auth_modules/ where socket.gethostname() is hardcoded without any way to override it.)

    Your description of the error messages on the terminal supports that there is a problem with error logging from mail.

  5. Thomas De Schampheleire

    In my (corporate) environment the SMTP server not only required a well-formed address but even an existing one, so would not be accepted, although it indeed makes sense to make that the default to help other users.

    To clarify: the error messages on the terminal were python exceptions, and in this case I started kallithea simply as 'paster serve production.ini'. On this same terminal I also see normal logs from e.g. 'INFO [kallithea.RequestWrapper]' or 'INFO [kallithea.lib.auth]'. So the location of the log was not that problematic, according to me?

  6. Mads Kiilerich

    These exceptions are usually sent by to the admin ... but that will of course give a catch 22 in this case ;-)

    Better documentation and better comments/defaults in the ini files would probably help.

  7. Log in to comment