New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sendmail example: command not implemented #126

Closed
sigod opened this Issue Oct 31, 2012 · 1 comment

Comments

Projects
None yet
2 participants
@sigod
Contributor

sigod commented Oct 31, 2012

Just look at this console output.

d:\sigod\dev\vibe.d\examples\sendmail>vibe
Checking dependencies in 'd:\sigod\dev\vibe.d\examples\sendmail'
[017B0F80:00000000 INF] Sending mail...
object.Exception@d:\sigod\dev\vibe.d\source\vibe\mail\smtp.d(187): Expected status 220 got 502:  5.5.1 Error: command not implemented
----------------
0x004C7838 in char[][] core.sys.windows.stacktrace.StackTrace.trace()
0x004C76C3 in core.sys.windows.stacktrace.StackTrace core.sys.windows.stacktrace.StackTrace.__ctor()
0x00499782 in pure @safe void std.exception.bailOut(immutable(char)[], uint, const(char[]))
0x0040F859 in void vibe.mail.smtp.expectStatus(vibe.stream.stream.InputStream, int) at d:\sigod\dev\vibe.d\source\vibe\mail\smtp.d(188)
0x0040F197 in void vibe.mail.smtp.sendMail(vibe.mail.smtp.SmtpClientSettings, vibe.mail.smtp.Mail) at d:\sigod\dev\vibe.d\source\vibe\mail\smtp.d(133)
0x004037B7 in _Dmain at d:\sigod\dev\vibe.d\examples\sendmail\source\app.d(21)
0x00495844 in extern (C) int rt.dmain2.main(int, char**).void runMain()
0x0049587E in extern (C) int rt.dmain2.main(int, char**).void runAll()
0x004954A0 in main
0x004CE341 in mainCRTStartup
0x758E3C45 in BaseThreadInitThunk
0x76DF37F5 in RtlInitializeExceptionChain
0x76DF37C8 in RtlInitializeExceptionChain
----------------

s-ludwig added a commit that referenced this issue Nov 1, 2012

Revamped the SMTP client a bit and changed the server for the SMTP ex…
…ample.

The SMTP client now prints the command that was issued whenever the server sends an error so that problems can be better debugged. It now also obeys the settings.connectionType field and settings.useTLS was removed in turn.

The SMTP example uses smtp.example.com now so that it already fails looking up the host and does not try to send a mail using some actually existing server. See also issue #126.
@s-ludwig

This comment has been minimized.

Show comment
Hide comment
@s-ludwig

s-ludwig Nov 1, 2012

Member

The random example server that I used does not support TLS. I now mainly did two things: Change the server to smtp.example.com and proivde a better error message that also prints the command that was issued (STARTTLS in this case).

Unfortunately, the SMTP example will have to stay dysfunctional, unless there is some reliable and open SMTP server standing around (which in turn would probably be blocked as a spam source). Maybe I'll add a small log message saying that the source code needs to be adjusted with a real SMTP server/account.

Member

s-ludwig commented Nov 1, 2012

The random example server that I used does not support TLS. I now mainly did two things: Change the server to smtp.example.com and proivde a better error message that also prints the command that was issued (STARTTLS in this case).

Unfortunately, the SMTP example will have to stay dysfunctional, unless there is some reliable and open SMTP server standing around (which in turn would probably be blocked as a spam source). Maybe I'll add a small log message saying that the source code needs to be adjusted with a real SMTP server/account.

@s-ludwig s-ludwig closed this Nov 25, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment