Since this library seems to lack the implementation of UIDL command. So I wrote functions that send the UIDL command and that parse the response from server, based on rfc1939. Please check my code.

Sorry for my poor english. Thank you.

A failed logon to a "Microsoft Exchange POP3" server does not give a error, and sets the authenticated flag.

Wireshark summary: S: -ERR Logon failure: unknown user name or bad password.

Building and testing are now done using the regular cargo tool. Test coverage is only uploaded on linux stable. Use cargo tarpaulin for uploading test coverage to coveralls

Someone was asking about the &'static str argument type on irc. Seems better to copy the referenced str data if a persistent copy is needed. The (host, port) tuple change seems easier to read than the format!() macro.

I simply replaced a few bits of code swapping out the openssl bits to the native_tls alternative, addressing #16. I also moved the example to the example directory enabling the use of (addressing #13 ): cargo run --example gmail

Please confirm I did this right! I'll fix any issues with this as soon as possible.

Hi, I just tried to retrieve some mails in a loop, knowing that message #44 is not formatted correctly according to RFC (Spam message contains un-encoded binary data) and so, must run into error:

Example:

for i in 43..49 {
        let message = pop3.retr(i);
        let _eml = match message {
            POP3Message { raw: _ } => println!("{} ->  OK", i),
            _ => {  println!("{} -> ERR", i)
            }
        };

Result

43 ->  OK
44 -> ERR
45 -> ERR
46 -> ERR
47 -> ERR
48 -> ERR

Omitting message #44 in this loop by adding if i == 44 { continue } before pop3.retr results in correct output:

43 ->  OK
45 ->  OK
46 ->  OK
47 ->  OK
48 ->  OK

Any ideas what´s going wrong here? Did I miss something?

This issue was automatically generated. Feel free to close without ceremony if you do not agree with re-licensing or if it is not possible for other reasons. Respond to @cmr with any questions or concerns, or pop over to #rust-offtopic on IRC to discuss.

You're receiving this because someone (perhaps the project maintainer) published a crates.io package with the license as "MIT" xor "Apache-2.0" and the repository field pointing here.

TL;DR the Rust ecosystem is largely Apache-2.0. Being available under that license is good for interoperation. The MIT license as an add-on can be nice for GPLv2 projects to use your code.

Why?

The MIT license requires reproducing countless copies of the same copyright header with different names in the copyright field, for every MIT library in use. The Apache license does not have this drawback. However, this is not the primary motivation for me creating these issues. The Apache license also has protections from patent trolls and an explicit contribution licensing clause. However, the Apache license is incompatible with GPLv2. This is why Rust is dual-licensed as MIT/Apache (the "primary" license being Apache, MIT only for GPLv2 compat), and doing so would be wise for this project. This also makes this crate suitable for inclusion and unrestricted sharing in the Rust standard distribution and other projects using dual MIT/Apache, such as my personal ulterior motive, the Robigalia project.

Some ask, "Does this really apply to binary redistributions? Does MIT really require reproducing the whole thing?" I'm not a lawyer, and I can't give legal advice, but some Google Android apps include open source attributions using this interpretation. Others also agree with it. But, again, the copyright notice redistribution is not the primary motivation for the dual-licensing. It's stronger protections to licensees and better interoperation with the wider Rust ecosystem.

How?

To do this, get explicit approval from each contributor of copyrightable work (as not all contributions qualify for copyright, due to not being a "creative work", e.g. a typo fix) and then add the following to your README:

## License

Licensed under either of

 * Apache License, Version 2.0, ([LICENSE-APACHE](LICENSE-APACHE) or http://www.apache.org/licenses/LICENSE-2.0)
 * MIT license ([LICENSE-MIT](LICENSE-MIT) or http://opensource.org/licenses/MIT)

at your option.

### Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted
for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any
additional terms or conditions.

and in your license headers, if you have them, use the following boilerplate (based on that used in Rust):

// Copyright 2016 rust-pop3 Developers
//
// Licensed under the Apache License, Version 2.0, <LICENSE-APACHE or
// http://apache.org/licenses/LICENSE-2.0> or the MIT license <LICENSE-MIT or
// http://opensource.org/licenses/MIT>, at your option. This file may not be
// copied, modified, or distributed except according to those terms.

It's commonly asked whether license headers are required. I'm not comfortable making an official recommendation either way, but the Apache license recommends it in their appendix on how to use the license.

Be sure to add the relevant LICENSE-{MIT,APACHE} files. You can copy these from the Rust repo for a plain-text version.

And don't forget to update the license metadata in your Cargo.toml to:

license = "MIT OR Apache-2.0"

I'll be going through projects which agree to be relicensed and have approval by the necessary contributors and doing this changes, so feel free to leave the heavy lifting to me!

Contributor checkoff

To agree to relicensing, comment with :

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

Or, if you're a contributor, you can check the box in this repo next to your name. My scripts will pick this exact phrase up and check your checkbox, but I'll come through and manually review this issue later as well.

• [ ] @Wooowe
• [x] @hebiyan
• [x] @mattnenterprise